<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [865G] [SNA] GPU Hang: freeze: stuck on render ring" href="https://bugs.freedesktop.org/show_bug.cgi?id=72089#c23">Comment # 23</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - [865G] [SNA] GPU Hang: freeze: stuck on render ring" href="https://bugs.freedesktop.org/show_bug.cgi?id=72089">bug 72089</a> from <a class="email" href="mailto:goetzchrist@gmail.com" title="Götz <goetzchrist@gmail.com>"> Götz</a> <pre>Created <a href="attachment.cgi?id=121145" name="attach_121145" title="/sys/class/drm/card0/error kernel 4.4.0">attachment 121145</a> <a href="attachment.cgi?id=121145&action=edit" title="/sys/class/drm/card0/error kernel 4.4.0">[details]</a> /sys/class/drm/card0/error kernel 4.4.0 With Kernel 4.4.0 and xf86-video-intel 2.99.917+519+g8229390 (both from Arch Linux) [ 469.990009] [drm] stuck on render ring [ 469.995039] [drm] GPU HANG: ecode 2:0:0x476f7fc1, in Xorg [339], reason: Ring hung, action: reset [ 469.995044] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 469.995046] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 469.995048] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 469.995050] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 469.995052] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 469.996128] drm/i915: Resetting chip after gpu hang [ 469.996180] [drm:i915_reset [i915]] *ERROR* Failed to reset chip: -19</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>