<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - GPU HANG: ecode 9:0:0x85dffffb, in X [2869], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=100459#c3">Comment # 3</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - GPU HANG: ecode 9:0:0x85dffffb, in X [2869], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=100459">bug 100459</a> from <a class="email" href="mailto:ckreuzberger@anexia-it.com" title="Christian Kreuzberger <ckreuzberger@anexia-it.com>"> Christian Kreuzberger</a> <pre>I am having the same issue with Ubuntu 16.04 on a Dell Optiplex 5040. CPU: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz At all times, my system used to freeze. This is the first time I was able to recover and got the following error in dmesg: [10475.769692] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1244], reason: Hang on render ring, action: reset [10475.769694] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [10475.769696] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [10475.769696] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [10475.769697] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [10475.769699] [drm] GPU crash dump saved to /sys/class/drm/card0/error [10475.769784] drm/i915: Resetting chip after gpu hang [10475.770004] [drm] GuC firmware load skipped [10477.781755] [drm] RC6 on I am trying the rc6 thing for kernel parameters now!</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>