[Bug 100448] New: [drm] GPU HANG: ecode 6:0:0x00fff8df, in Xwayland [1636], reason: Hang on render ring, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Wed Mar 29 13:53:19 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=100448
Bug ID: 100448
Summary: [drm] GPU HANG: ecode 6:0:0x00fff8df, in Xwayland
[1636], reason: Hang on render ring, action: reset
Product: DRI
Version: DRI git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: mikhail.v.gavrilov at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 130532
--> https://bugs.freedesktop.org/attachment.cgi?id=130532&action=edit
dmesg
Kernel 4.11.0-0.rc2
[ 101.841803] [drm] GPU HANG: ecode 6:0:0x00fff8df, in Xwayland [1636],
reason: Hang on render ring, action: reset
[ 101.841805] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 101.841805] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 101.841806] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 101.841806] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 101.841807] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 101.856990] drm/i915: Resetting chip after gpu hang
[ 109.838383] drm/i915: Resetting chip after gpu hang
[ 117.838499] drm/i915: Resetting chip after gpu hang
[ 198.863210] drm/i915: Resetting chip after gpu hang
[ 206.863314] drm/i915: Resetting chip after gpu hang
[ 206.863359] [drm:i915_reset [i915]] *ERROR* GPU recovery failed
--
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20170329/a87ae34d/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list