From: Dan Williams <dan.j.williams@intel.com>
To: Andrew Morton <akpm@linux-foundation.org>
Cc: smf.linux@ntlworld.com, bugzilla-daemon@bugzilla.kernel.org,
Linux MM <linux-mm@kvack.org>
Subject: Re: [Bug 112211] New: ATI Radeon Graphics not rendering correctly
Date: Wed, 10 Feb 2016 18:21:54 -0800 [thread overview]
Message-ID: <CAPcyv4heg5VwqgjkpHAC3gfHANv4tu=n2hpeCoSpaeyhRQBUqg@mail.gmail.com> (raw)
In-Reply-To: <CAPcyv4hCRxUWLdsreG+LJZwP0VmVPOGLK-uh46++juj2KOH8QQ@mail.gmail.com>
On Tue, Feb 9, 2016 at 12:36 PM, Dan Williams <dan.j.williams@intel.com> wrote:
> On Tue, Feb 9, 2016 at 12:20 PM, Andrew Morton
> <akpm@linux-foundation.org> wrote:
>>
>> (switched to email. Please respond via emailed reply-to-all, not via the
>> bugzilla web interface).
>>
>> On Tue, 09 Feb 2016 08:41:39 +0000 bugzilla-daemon@bugzilla.kernel.org wrote:
>>
>>> https://bugzilla.kernel.org/show_bug.cgi?id=112211
>>>
>>> Bug ID: 112211
>>> Summary: ATI Radeon Graphics not rendering correctly
>>> Product: Memory Management
>>> Version: 2.5
>>> Kernel Version: Linux 4.5-rc3
>>> Hardware: IA-32
>>> OS: Linux
>>> Tree: Mainline
>>> Status: NEW
>>> Severity: normal
>>> Priority: P1
>>> Component: Page Allocator
>>> Assignee: akpm@linux-foundation.org
>>> Reporter: smf.linux@ntlworld.com
>>> Regression: No
>>>
>>> On testing linux 4.5-rc( 1,2 and 3) I have found that my display is not
>>> rendered correctly on starting the X server. My screen is mainly black with
>>> portions of the desktop appearing from time to time. I initially raised this
>>> with the DRM/Radeon team:
>>>
>>> https://bugs.freedesktop.org/show_bug.cgi?id=93998
>>>
>>> On investigation a bisect identified the following commit as the source of my
>>> problem:
>>>
>>> 01c8f1c44b83a0825b573e7c723b033cece37b86 is the first bad commit
>>> commit 01c8f1c44b83a0825b573e7c723b033cece37b86
>>> Author: Dan Williams <dan.j.williams@intel.com>
>>> Date: Fri Jan 15 16:56:40 2016 -0800
>>>
>>> mm, dax, gpu: convert vm_insert_mixed to pfn_t
>>>
>>> Convert the raw unsigned long 'pfn' argument to pfn_t for the purpose of
>>> evaluating the PFN_MAP and PFN_DEV flags. When both are set it triggers
>>> _PAGE_DEVMAP to be set in the resulting pte.
>>>
>>> There are no functional changes to the gpu drivers as a result of this
>>> conversion.
>>>
>>> Signed-off-by: Dan Williams <dan.j.williams@intel.com>
>>> Cc: Dave Hansen <dave@sr71.net>
>>> Cc: David Airlie <airlied@linux.ie>
>>> Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
>>> Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
>>>
>>> The problem is present on two AMD/ATI systems I have tried but is absent from
>>> my Intel based laptop. All my systems are 32 bit LFS builds.
>>>
>>> I did try to contact Dan Williams but I am not sure that my e-mail got through,
>>> can anyone suggest a way forward please ?
>>>
>>
>> Does your kernel include
>>
>> commit 03fc2da63b9a33dce784a2075c7e068bb97cbf69
>> Author: Dan Williams <dan.j.williams@intel.com>
>> Date: Tue Jan 26 09:48:05 2016 -0800
>>
>> mm: fix pfn_t to page conversion in vm_insert_mixed
>>
>
> Hi Stuart, from the bugzilla activity it looks like you are already
> running with this fix. Can you append you kernel config file to the
> bugzilla. There's something particular about 32-bit builds I'm
> missing...
Thanks for the config file. I was able to reproduce this in a VM that
uses the DRM layer. The fix that works for me is available here in
patchwork [1]. Let me know if it works in your environment.
[1]: https://patchwork.kernel.org/patch/8276171/
--
To unsubscribe, send a message with 'unsubscribe linux-mm' in
the body to majordomo@kvack.org. For more info on Linux MM,
see: http://www.linux-mm.org/ .
Don't email: <a href=mailto:"dont@kvack.org"> email@kvack.org </a>
prev parent reply other threads:[~2016-02-11 2:21 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-112211-27@https.bugzilla.kernel.org/>
2016-02-09 20:20 ` Andrew Morton
2016-02-09 20:36 ` Dan Williams
2016-02-11 2:21 ` Dan Williams [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAPcyv4heg5VwqgjkpHAC3gfHANv4tu=n2hpeCoSpaeyhRQBUqg@mail.gmail.com' \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=bugzilla-daemon@bugzilla.kernel.org \
--cc=linux-mm@kvack.org \
--cc=smf.linux@ntlworld.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox