On Wed, Sep 08, 2010 at 05:48:17PM +0100, Chris Wilson wrote: > On Wed, 8 Sep 2010 18:38:09 +0200, Julien Cristau <jcris...@debian.org> wrote: > > On Wed, Sep 8, 2010 at 17:10:36 +0100, Chris Wilson wrote: > > > As it looks like uninitialised data, it could be the xserver bug where we > > > sent damage events prior to flushing the 2D batchbuffer, so that there was > > > an opportunity for compositing WM to grab garbage. > > > > > That one's plausible, thanks. Florian, are you running a compositing > > manager? If yes, does the corruption happen without that? > > > > Looks like the fix for that one is > > 8d7b7a0d71e0b89321b3341b781bc8845386def6 and > > c65f610e12f9df168d5639534ed3c2bd40afffc8? > > And 69d65f9184006eac790efcff78a0e425160e95aa for -intel. > -Chris
I guess these are git commit id's? Which repository? I failed to find it in the kernel and the obvious intel drivers git. I'd like to test possible fixes. Flo -- Florian Lohoff f...@zz.de
signature.asc
Description: Digital signature
