<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] [SKL] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [4561], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=100753#c5">Comment # 5</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [i915] [SKL] GPU HANG: ecode 9:0:0x86dffffd, in Xorg [4561], reason: Hang on render ring, action: reset" href="https://bugs.freedesktop.org/show_bug.cgi?id=100753">bug 100753</a> from <a class="email" href="mailto:milamber@linux.com" title="Milamber <milamber@linux.com>"> Milamber</a> <pre> A new hang but this time with XWayland (on the same laptop) [77401.948200] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xwayland [17361], reason: Hang on render ring, action: reset [77401.948203] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace. [77401.948204] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel [77401.948205] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue. [77401.948206] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it. [77401.948208] [drm] GPU crash dump saved to /sys/class/drm/card0/error [77401.948281] drm/i915: Resetting chip after gpu hang [77401.948346] [drm] RC6 on [77401.964901] [drm] GuC firmware load skipped [77413.947343] drm/i915: Resetting chip after gpu hang [77413.947410] [drm] RC6 on [77413.963504] [drm] GuC firmware load skipped</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> </ul> </body> </html>