Comment # 32
on bug 89034
from Tom Stellard
(In reply to smoki from comment #31) > (In reply to Michel Dänzer from comment #30) > > I think at least the piglit regressions aren't directly related to > > sub-register liveness and should be tracked in a separate bug report: > > Those regressions are only reproducable here with sub reg liveness enabled. > > >On my Kaveri, I've been seeing random failures of some (of the same as yours) >piglit tests recently (with sub-register liveness disabled). The only way I've >found to avoid those failures is to keep rebooting until I get lucky. It seems >like some recent change (most likely in Mesa?) causes the hardware to go into a >weird, semi-persistent state. > > >I'm afraid it might be tricky to bisect that, but it would be very helpful. > > That sounds like a separate one, but i don't have that and can't reproduce > it on Kabini. I only have some known of those sometimes fails at random, but > those are under "warn" and just few of them (i am talking about just 1-3 > tests), but no "fail" tests happens here at random. Would you be able to set the environment variable R600_DEBUG=ps,vs and run the glsl-fs-min test with the good and bad commit and post the output. R600_DEBUG=ps,vs ./bin/shader_runner tests/shaders/glsl-fs-min-shader_test -auto
You are receiving this mail because:
- You are the assignee for the bug.
_______________________________________________ dri-devel mailing list dri-devel@xxxxxxxxxxxxxxxxxxxxx http://lists.freedesktop.org/mailman/listinfo/dri-devel
