[Bug 97334] New: GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [3284], reason: Ring hung, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Aug 13 17:51:14 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=97334
Bug ID: 97334
Summary: GPU HANG: ecode 6:0:0x87e8fffd, in Xorg [3284],
reason: Ring hung, action: reset
Product: DRI
Version: unspecified
Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: jonschoning at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
[ 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]
--
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160813/56a28fa7/attachment.html>
More information about the intel-gfx-bugs
mailing list