<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226#c263">Comment # 263</a> on <a class="bz_bug_link bz_status_REOPENED " title="REOPENED - [snb 3.5] stale semaphore sync seqno (typically as seen on bcs->rcs)" href="https://bugs.freedesktop.org/show_bug.cgi?id=54226">bug 54226</a> from <a class="email" href="mailto:aaron.lu@intel.com" title="Aaron Lu <aaron.lu@intel.com>"> Aaron Lu</a> <pre>Created <a href="attachment.cgi?id=135173" name="attach_135173" title="gpu error file on 4.13.5-200.fc26.x86_64">attachment 135173</a> <a href="attachment.cgi?id=135173&action=edit" title="gpu error file on 4.13.5-200.fc26.x86_64">[details]</a> gpu error file on 4.13.5-200.fc26.x86_64 This problem reappeared on 4.13.5-200.fc26.x86_64 last Friday. [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</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> </ul> </body> </html>