linux-kernel - Re: linux-next: Tree for Aug 21 [ screen corruption in graphical mode ]

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Date:	Thu, 22 Aug 2013 13:32:16 +0200
From:	Daniel Vetter <daniel.vetter@...ll.ch>
To:	Sedat Dilek <sedat.dilek@...il.com>
Cc:	Chris Wilson <chris@...is-wilson.co.uk>,
	linux-next <linux-next@...r.kernel.org>,
	LKML <linux-kernel@...r.kernel.org>,
	intel-gfx <intel-gfx@...ts.freedesktop.org>,
	Stephen Rothwell <sfr@...b.auug.org.au>,
	"s.dilek" <s.dilek@...erlin.de>
Subject: Re: linux-next: Tree for Aug 21 [ screen corruption in graphical mode ]

On Thu, Aug 22, 2013 at 1:30 PM, Daniel Vetter <daniel.vetter@...ll.ch> wrote:
> On Thu, Aug 22, 2013 at 1:13 PM, Sedat Dilek <sedat.dilek@...il.com> wrote:
>> dmesg (a lot of traces) and kernel-config attached.
>>
>> UXA causes still screen corruption.
>
> Hm, was only a slim chance that this patch would fix anything - I
> think you'd always see an oops when you'd hit this bug instead of just
> a bit of corruption.

Ok, I think it's time to throw in the towel a bit. I've dropped


commit d46f1c3f1372e3a72fab97c60480aa4a1084387f
Author: Chris Wilson <chris@...is-wilson.co.uk>
Date:   Thu Aug 8 14:41:06 2013 +0100

    drm/i915: Allow the GPU to cache stolen memory

from my queue. I guess we can retry for 3.13 again.
-Daniel
-- 
Daniel Vetter
Software Engineer, Intel Corporation
+41 (0) 79 365 57 48 - http://blog.ffwll.ch
--
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/