<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - Screen freezes after updating to 1.18.3 [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [319], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=96452#c1">Comment # 1</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - Screen freezes after updating to 1.18.3 [drm] GPU HANG: ecode 8:0:0xfffffffe, in Xorg [319], reason: Ring hung, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=96452">bug 96452</a> from <a class="email" href="mailto:jaglover@gmail.com" title="Saul <jaglover@gmail.com>"> Saul</a> <pre>Same issue here: [ 1108.779048] [drm] stuck on render ring [ 1108.786056] [drm] GPU HANG: ecode 8:0:0xfffffffe, in X [1897], reason: Ring hung, action: reset [ 1108.786063] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [ 1108.786067] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [ 1108.786071] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [ 1108.786074] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [ 1108.786078] [drm] GPU crash dump saved to /sys/class/drm/card0/error [ 1108.787820] drm/i915: Resetting chip after gpu hang [ 1116.779124] [drm] stuck on render ring [ 1116.786003] [drm] GPU HANG: ecode 8:0:0xfffffffe, in X [1897], reason: Ring hung, action: reset [ 1116.786435] [drm:i915_set_reset_status] *ERROR* gpu hanging too fast, banning! [ 1116.788816] drm/i915: Resetting chip after gpu hang</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>