I tried to compile mesa-git from aur but it failed. I really won't be able to compile it multiple times on this machine to search which commit broke it. Is this a big problem? Will be this not be resolved if I am not able to do all thing?

(In reply to cosiekvfj from comment #11)
> "skl shows correct rendering" What does that mean?
>
> I also tested app with LIBGL_ALWAYS_SOFTWARE=1 and then rendering is correct.
This means that the trace renders correctly on Intel Skylake (i965) driver.

I have compiled couple of times. Here are my results.
b7da8fa11d5c6ec71113350eed1959191a7d5990 working
84b961dd53a0509a6865d8417301838b34a40096 working
e54b2e902aba22f697c0ba8622cd0a905f1edfff working
172bfdaa9e80342ade3f023f72d455d76713b866 not working
f75a1084349f2332aa080d77acc175ddbe0ab886 not working

Created attachment 129912[details]
Piglit dri2 w/o patch
I have done piglit test you guys was talking about on the mailinglist. I can do it again with patch if you want. Also I have rendering issue with dri3 and steam login screen. I think I will make another bug report. Also I want to test hyperz in piglit so it can be flipped on by default.

Created attachment 129963[details]
piglit mesa at e54b2e902aba22f697c0ba8622cd0a905f1edfff
I also tested mesa before the commit which broke my usercase. After earlier tests I had small image artefact on terminal window. Not with this one. :)
If you want more tests or you want me to redo previous tests or if you are unsure about results, I'm happy to help.

I think it's not the end. I think this workaround proposed in this patch is not an actual workaround. I've opened another ticket for this issue, but I think it would be better of to revert back this patch. https://bugs.freedesktop.org/show_bug.cgi?id=101382