Bug 97334

Summary: GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [3284], reason: Ring hung, action: reset
Product: DRI Reporter: jonschoning
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED WONTFIX QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: SNB i915 features: GPU hang

Description jonschoning 2016-08-13 17:51:14 UTC 
[ 1273.859190] [drm] stuck on render ring
[ 1273.859668] [drm] GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [3284], reason: Ring hung, action: reset
[ 1273.859669] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1273.859670] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1273.859670] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1273.859671] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1273.859672] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1273.861826] drm/i915: Resetting chip after gpu hang
[ 1279.859432] [drm] stuck on render ring
[ 1279.859971] [drm] GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [3284], reason: Ring hung, action: reset
[ 1279.862110] drm/i915: Resetting chip after gpu hang
[ 1279.924540] show_signal_msg: 6 callbacks suppressed
[ 1279.924543] chrome[6470]: segfault at 968 ip 00007fbcffdf3643 sp 00007fff1da6e900 error 4 in libX11.so.6.3.0[7fbcffdcb000+135000]
Comment 1 Chris Wilson 2016-08-15 08:42:16 UTC 
/sys/class/drm/card0/error is required after the hang (before rebooting) for triaging.
Comment 2 yann 2016-08-23 14:21:28 UTC 
Jonschoning, please attach GPU crash dump saved to /sys/class/drm/card0/error and kernel log (ie dmesg).
Comment 3 jonschoning 2016-08-23 16:17:03 UTC 
/sys/class/drm/card0/error had 0 bytes at the time of the error.  There is no more information.
Comment 4 Chris Wilson 2016-08-23 16:20:17 UTC 
It is a virtual file. It has no size until you open it, ls misreports it size as 0 when it is never empty.
Comment 5 Jari Tahvanainen 2017-07-03 11:06:35 UTC 
Closing ~1 year old resolved+wontfix.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.