Commen=
t # 32
on bug 89034<=
/a>
from Tom Stellard
(In reply to smoki from comment #31)
> (In reply to Michel D=C3=A4nzer 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 rep=
ort:
>=20
> Those regressions are only reproducable here with sub reg liveness en=
abled.
>=20
> >On my Kaveri, I've been seeing random failures of some (of the sam=
e 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 Mes=
a?) causes the hardware to go into a >weird, semi-persistent state.
>=20
> >I'm afraid it might be tricky to bisect that, but it would be very=
helpful.
>=20
> That sounds like a separate one, but i don't have that and can't repr=
oduce
> it on Kabini. I only have some known of those sometimes fails at rando=
m, but
> those are under "warn" and just few of them (i am talking ab=
out just 1-3
> tests), but no "fail" tests happens here at random.
Would you be able to set the environment variable R600_DEBUG=3Dps,vs and ru=
n the
glsl-fs-min test with the good and bad commit and post the output.
R600_DEBUG=3Dps,vs ./bin/shader_runner tests/shaders/glsl-fs-min-shader_test
-auto