[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUXdS3EuXyGZiS1--rMu6H0ospzCiK_CXgPv8mOk0sMt+Q@mail.gmail.com>
Date: Tue, 13 Aug 2013 18:23:29 +0200
From: Sedat Dilek <sedat.dilek@...il.com>
To: Chris Wilson <chris@...is-wilson.co.uk>,
Sedat Dilek <sedat.dilek@...il.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, linux-kernel@...r.kernel.org,
Daniel Vetter <daniel.vetter@...ll.ch>,
Dave Airlie <airlied@...il.com>,
DRI <dri-devel@...ts.freedesktop.org>,
intel-gfx <intel-gfx@...ts.freedesktop.org>,
"s.dilek" <s.dilek@...erlin.de>
Subject: Re: linux-next: Tree for Aug 13 [ screen corruption in graphical mode ]
On Tue, Aug 13, 2013 at 5:59 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
> On Tue, Aug 13, 2013 at 4:45 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> On Tue, Aug 13, 2013 at 4:07 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>> On Tue, Aug 13, 2013 at 11:57 AM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>>>> On Tue, Aug 13, 2013 at 11:52 AM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>>>>> On Tue, Aug 13, 2013 at 11:47:19AM +0200, Sedat Dilek wrote:
>>>>>> On Tue, Aug 13, 2013 at 11:39 AM, Chris Wilson <chris@...is-wilson.co.uk> wrote:
>>>>>> > On Tue, Aug 13, 2013 at 11:35:53AM +0200, Sedat Dilek wrote:
>>>>>> >> After a logout from my "BROKEN" Unity-2D session - the login-screen
>>>>>> >> for LightDM seems to be OK.
>>>>>> >> Then entering my Unity-2D desktop is OK - no screen corruptions.
>>>>>> >
>>>>>> > What hardware and display do you have?
>>>>>>
>>>>>> It's a Samsung ultrabook with SandyBridge CPU.
>>>>>>
>>>>>> [ 333.291] (--) intel(0): Integrated Graphics Chipset: Intel(R) HD
>>>>>> Graphics 3000
>>>>>
>>>>> using LVDS.
>>>>>
>>>>>> - Sedat -
>>>>>>
>>>>>> P.S.: I switched to intel-ddx v2-21-14-35-g5840bf in the meantime.
>>>>>
>>>>> Did that make a difference? It shouldn't if the error is occuring before
>>>>> X even starts...
>>>>
>>>> NO, was just confused not seeing "GT2" (HD-3000 was new to me) in my
>>>> Xorg.log :-).
>>>>
>>>> As said logging out of Unity-2D and entering LightDM greeter - screen is fine.
>>>> Starting again a Unity-2D session - no screen corruption, too.
>>>>
>>>> - Sedat -
>>>
>>> Some more testing:
>>>
>>> [1] With my X stack:
>>>
>>> FIRST BAD: next-20130812
>>> LAST GOOD: next-20130809
>>>
>>> [2] With Ubuntu's X stack:
>>>
>>> next-20130813 is OK (Xorg.log attached)
>>>
>>
>> drm-intel-nightly is also BAD with my X stack (with Ubuntu's X stack
>> no problems).
>>
>
> I have bisected the issue on Linux v3.11-rc5 + drm-intel-nightly:
>
> 5456fe3882812aba251886e36fe55bfefb8e8829 is the first bad commit
> commit 5456fe3882812aba251886e36fe55bfefb8e8829
> Author: Chris Wilson <chris@...is-wilson.co.uk>
> Date: Thu Aug 8 14:41:07 2013 +0100
>
> drm/i915: Allocate LLC ringbuffers from stolen
>
> As stolen objects now behave identically (wrt to default LLC cacheing)
> as their normal system counterparts, we no longer have to differentiate
> our usage for ringbuffers. So allocate them from stolen on SNB+ as well.
>
> Signed-off-by: Chris Wilson <chris@...is-wilson.co.uk>
> Reviewed-by: Ville Syrjälä <ville.syrjala@...ux.intel.com>
> Signed-off-by: Daniel Vetter <daniel.vetter@...ll.ch>
>
> :040000 040000 de063a052f39095f4d2f51b49caef9f827df41e8
> 1c819aa5501a9fcc9912a5c7c037c71b9b9e9a6b M drivers
>
> See also attached files!
>
With the attached revert-patch my system is OK (with my customized X stack).
- Sedat -
Download attachment "0001-Revert-drm-i915-Allocate-LLC-ringbuffers-from-stolen.patch" of type "application/octet-stream" (1030 bytes)
Powered by blists - more mailing lists