Created an attachment (id=34479)
dmesg of early failure with 1000 retries, 128 whack pages
(In reply to comment #39)
> > --- Comment #38 from legolas558 <email address hidden> 2010-03-26 07:08:31 PST ---
> btw, I've tried your two-glxgears-with-clipping test. No ill effects, here
> ...
>
I have tested with 32, 64, 128 whack pages and I have found the following:
- with 32/64 whack pages, moving around one glxgears window was enough to trigger the flush failure
- with 128 whack pages, moving around didn't seem to work but a resize of the glxgears window triggered the bug
- bug becomes progressively harder to trigger when increasing whack pages (qualitative sensation)
In all cases (even 16 whack pages and/or 1000/2000 retries), no more than 2 failures are found in dmesg (because as you said it gives up after that).
I am worried about this fact that our hardware, apparently the same, is not showing same behaviour...my .config is here:
Created an attachment (id=34479)
dmesg of early failure with 1000 retries, 128 whack pages
(In reply to comment #39) with-clipping test. No ill effects, here
> > --- Comment #38 from legolas558 <email address hidden> 2010-03-26 07:08:31 PST ---
> btw, I've tried your two-glxgears-
> ...
>
I have tested with 32, 64, 128 whack pages and I have found the following:
- with 32/64 whack pages, moving around one glxgears window was enough to trigger the flush failure
- with 128 whack pages, moving around didn't seem to work but a resize of the glxgears window triggered the bug
- bug becomes progressively harder to trigger when increasing whack pages (qualitative sensation)
In all cases (even 16 whack pages and/or 1000/2000 retries), no more than 2 failures are found in dmesg (because as you said it gives up after that).
I am worried about this fact that our hardware, apparently the same, is not showing same behaviour...my .config is here:
http:// www.iragan. com/linux/ i855GM/ legolas558. config