[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CA+icZUUKH6Fa8WksqA69FXKUUJmKsNdXv0ZJH50HA2mFavfPCg@mail.gmail.com>
Date: Tue, 13 Aug 2013 16:45:25 +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 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).
- Sedat -
> - Sedat -
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists