<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Firefox crashing xserver and some major rendering bugs" href="https://bugs.freedesktop.org/show_bug.cgi?id=89034#c30">Comment # 30</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Firefox crashing xserver and some major rendering bugs" href="https://bugs.freedesktop.org/show_bug.cgi?id=89034">bug 89034</a> from <a class="email" href="mailto:michel@daenzer.net" title="Michel Dänzer <michel@daenzer.net>"> Michel Dänzer</a> <pre>(In reply to smoki from <a href="show_bug.cgi?id=89034#c29">comment #29</a>) > I did fresh piglit run now and it shows there are 159 regressed now... I think at least the piglit regressions aren't directly related to sub-register liveness and should be tracked in a separate bug report: 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.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>