<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED DUPLICATE - GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue" href="https://bugs.freedesktop.org/show_bug.cgi?id=100245#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_CLOSED bz_closed" title="CLOSED DUPLICATE - GPU HANG: ecode 6:-1:0x00000000, reason: Kicking stuck semaphore on render ring, action: continue" href="https://bugs.freedesktop.org/show_bug.cgi?id=100245">bug 100245</a> from <a class="email" href="mailto:aaron.lu@intel.com" title="Aaron Lu <aaron.lu@intel.com>"> Aaron Lu</a> <pre>This problem reappeared on 4.13.5-200.fc26.x86_64 [774249.632109] [drm] GPU HANG: ecode 6:0:0x85fffff8, in Xorg [696], reason: Hang on rcs0, action: reset [774249.632110] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [774249.632111] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [774249.632111] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [774249.632111] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [774249.632112] [drm] GPU crash dump saved to /sys/class/drm/card0/error [774249.632172] drm/i915: Resetting chip after gpu hang It recovered without killing my desktop session, please let me know if you need the error file.</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>