<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - GPU lockups with kernel 3.11.0 / 3.12-rc1 when dpm=1 on r600g (Cayman)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69723#c51">Comment # 51</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - GPU lockups with kernel 3.11.0 / 3.12-rc1 when dpm=1 on r600g (Cayman)" href="https://bugs.freedesktop.org/show_bug.cgi?id=69723">bug 69723</a> from <a class="email" href="mailto:alexandre.f.demers@gmail.com" title="Alexandre Demers <alexandre.f.demers@gmail.com>"> Alexandre Demers</a> <pre>(In reply to <a href="show_bug.cgi?id=69723#c50">comment #50</a>) > (In reply to <a href="show_bug.cgi?id=69723#c49">comment #49</a>) > > (In reply to <a href="show_bug.cgi?id=69723#c48">comment #48</a>) > > > The display went black a couple of time and according to dmesg/journal, it was > > > related to texelFetch segfaulting in llvm [...] > > > > 'The display went black a couple of time' sounds like GPU resets after > > lockups, which are unlikely to be directly related to segfaulting piglit > > tests FWIW. > > Maybe, but I have no other indication. Also, I'm pretty that, when in auto > power level, when I run my piglit tests, it locks at there. > > Another thing I noticed: if I run the quick piglit tests at a low power > level, the total number of passed tests is higher than when I run it at an > higher speed. The failing tests explaining this difference are mostly > texelFetch related. I'll send the piglit results from both runs once I'll > have set back mclk to its default value. Oops, "... I'm pretty that..." -> "... I'm pretty sure that..."</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>