[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#596085: xserver-xorg-video-intel: partial display corruption / mostly text / Mobile 945GM



tag 596085 moreinfo
kthxbye

Hi Florian,

On Wed, Sep 22, 2010 at 11:50:59 +0200, Florian Lohoff wrote:

> 
> Hi,
> 
> On Mon, Sep 20, 2010 at 07:24:57PM +0200, Julien Cristau wrote:
> > On Mon, Sep 20, 2010 at 18:02:31 +0200, Florian Lohoff wrote:
> > 
> > > On Wed, Sep 08, 2010 at 05:48:17PM +0100, Chris Wilson wrote:
> > > > On Wed, 8 Sep 2010 18:38:09 +0200, Julien Cristau <jcristau@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.
> > > 
> > The first two are git://anongit.freedesktop.org/git/xorg/xserver and the
> > third is git://anongit.freedesktop.org/git/xorg/driver/xf86-video-intel.
> 
> Okay - i rebuilt xserver-xorg-core and video-intel with the above patches and
> i still have those corruptions.
> 
Could you re-test with an updated stack (kernel 3.0 or 3.1, X 1.11,
intel 2.16) and let us know if it's gone?  If not please file a bug
upstream according to
http://intellinuxgraphics.org/how_to_report_bug.html and let us know the
bug number for tracking.

Thanks,
Julien



Reply to: