<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [v4.10] GPU HANG: ecode 6:0:0xbd69ffff, in compiz [2609], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=99671#c22">Comment # 22</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [v4.10] GPU HANG: ecode 6:0:0xbd69ffff, in compiz [2609], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=99671">bug 99671</a> from <a class="email" href="mailto:chris@chris-wilson.co.uk" title="Chris Wilson <chris@chris-wilson.co.uk>"> Chris Wilson</a> <pre>(In reply to Josh Holland from <a href="show_bug.cgi?id=99671#c20">comment #20</a>) > I got a crash, although I couldn't get the GPU crash dump unfortunately -- I > couldn't even switch to a TTY. dmesg looks like it might be more useful now > though. Hmm, after the hang though and the crash is consistent with the corruption. But it does make the matter much more serious as we go from a gpu hang to a driver lockup. I was expecting the debug code to detect something much, much earlier. Hmm. Or maybe it is more significant than I first thought. Feb 11 17:47:37 yes kernel: [ 2.358719] [drm] DRM_I915_DEBUG_GEM enabled confirms that the debug code was indeed enabled. > Should I be staying on revision fb21519ea for this, or should I be upgrading > to the latest drm-tip? Nothing pertinent to this bug yet, but refreshing everytime we have an idea to test will be helpful (random bug fixes hopefully improving and not adding regressions elsewhere!).</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>