(In reply to comment #153)
> (In reply to comment #145)
> > Created attachment 91383 [details]
> > gedit in openbox with 2.99.907 GM45 SNA
> >
> > I am finding that GM45 SNA seems unusable with 2.99.907 - git bisect pointed
> > to the bad commit as:
> > 9289e2c56b7f0cc78c5123691ad96611f0e04bed is the first bad commit
> > commit 9289e2c56b7f0cc78c5123691ad96611f0e04bed
> > Author: Chris Wilson <email address hidden>
> > Date: Mon Dec 16 11:39:20 2013 +0000
> >
> > sna/gen4: Sacrifice performance to workaround render corruption
Interestingly this commit has increased the number of buggy character occurrence - although I admit I'm overriding MAX_FLUSH_VERTICES to 9 (since I don't like the slowness with 1) so I've been rather living with faster desktop and occasional wrong characters on the screen - but with this commit it seems to appearance of visual problem increased to the level which makes noticeable reading difficulties that probably enforce me to switch to very slow '1' for MAX :(...
(I'm not sure if it's the direct cause - since I've been using before about 3 week old version of git tree)
(In reply to comment #153) 78c5123691ad966 11f0e04bed is the first bad commit 78c5123691ad966 11f0e04bed
> (In reply to comment #145)
> > Created attachment 91383 [details]
> > gedit in openbox with 2.99.907 GM45 SNA
> >
> > I am finding that GM45 SNA seems unusable with 2.99.907 - git bisect pointed
> > to the bad commit as:
> > 9289e2c56b7f0cc
> > commit 9289e2c56b7f0cc
> > Author: Chris Wilson <email address hidden>
> > Date: Mon Dec 16 11:39:20 2013 +0000
> >
> > sna/gen4: Sacrifice performance to workaround render corruption
Interestingly this commit has increased the number of buggy character occurrence - although I admit I'm overriding MAX_FLUSH_VERTICES to 9 (since I don't like the slowness with 1) so I've been rather living with faster desktop and occasional wrong characters on the screen - but with this commit it seems to appearance of visual problem increased to the level which makes noticeable reading difficulties that probably enforce me to switch to very slow '1' for MAX :(...
(I'm not sure if it's the direct cause - since I've been using before about 3 week old version of git tree)