Created attachment 43153 [details]
A photo of screen mess
Bug detailed description:
Screen mess when running vdrift. It's kernel regression.Pls see attached photo.
Jesse, does this look familiar?
That does look a bit like the failure Michael was seeing; if it's a kernel regression what's the offending commit?
Screen mess when running vdrift only exists on Huronriver (VGA compatible
controlle:0126(rev 08)).In particular, it works fine in our new Huronriver(VGA
compatible controller: Intel Corporation Device 0116 (rev 09)) and Sugarbay.
The main aspect of screen mess is car mess in this bug.
1.Huron River(0126 rev08)could reproduce this bug easily.Usually,it appears within 30 seconds after the game start and exists until the game is over. The game lasts about two minutes.
2.Sugarbay and HuronRiver(0116 rev 09)：The situations of this two SNB is different from above Huron River(0126 rev08). Car mess may appear after the game begins and continue one to two seconds.Besides, in a game ,the time and the probability for its occurence is small(the probability may 1/10 or much more lower ). It is hard to reproduce.
For Huron River(0126 rev08),this bug is easy to be reproduce.However, the situation of the good commit which was figured out ago is similar to “Sugarbay and HuronRiver(0116 rev 09)”after being test again(car mess may appear,but the time and the probability of a game is a little larger than the other two machines ).After the mistake was found,I tried to find out the good commit of Huron River(0126 rev08),but before unstalbe_Kernel_37 I still didn't find it.
I think this one is fixed now?
Test on Huronriver, the problem still exists.
Kernel: (drm-intel-next) da3cc9202697a44057c1bd3ad685689375f1fe0c
The phenomenon: flashing spots on car come out when running vdrift. When spots come out, maybe disappear soon, then come out again.It exists not only on HuronRiver(rev 08) but also on HuronRiver(rev 09).
There is the same problem on padman.
The problem is still existed in IVB and SNB platform.
Ian, can you reproduce this?
I have concern for getting performance data with this bug existing.
Proposed fix that may apply (there's alpha testing on some of that screenshot, but I'm not sure how the car is rendered):
Gordon, does this still happens with latest 3.2 RC, or drm-intel-next branch?
The bug only exists when run vdrift on the SNB, and both exists when run padman and vdrift on IVB.
(In reply to comment #13)
> Gordon, does this still happens with latest 3.2 RC, or drm-intel-next branch?
The attached vdrift screenshot looks an awful lot like the Sandybridge clock gating bug Eric fixed in kernel 3.2.
I just tried World of Padman on Ivybridge and it looks fine. Vdrift doesn't run due to #44957 (an application bug), so I didn't test that.
Closing this as WORKSFORME. If you still see problems, please open separate bugs for each application.
Li Bo, please verify.
padman has been fixed in both IVB and SNB. but vdrift still has this problem, not only on IVB and SNB, but also on other platforms.