[Bug 99671] [v4.10] GPU HANG: ecode 6:0:0xbd69ffff, in compiz [2609], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99671

--- Comment #22 from Chris Wilson <chris at chris-wilson.co.uk> ---
(In reply to Josh Holland from comment #20)
> 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!).

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170211/a349bff9/attachment.html>