[Bug 104037] New: [drm] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason: Hang on rcs0, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sat Dec 2 13:55:18 UTC 2017
https://bugs.freedesktop.org/show_bug.cgi?id=104037
Bug ID: 104037
Summary: [drm] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688],
reason: Hang on rcs0, 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: philip.kiehnle at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 135878
--> https://bugs.freedesktop.org/attachment.cgi?id=135878&action=edit
Content of /sys/class/drm/card0/error
When using KiCad's Pcbnew program, after a while the screen freezes for a few
seconds, then the window manager restarts.
Ubuntu 16.04 with kernel 4.14.
$ dmesg
[ 2245.773240] [drm] GPU HANG: ecode 9:0:0x87f9bffb, in Xorg [1688], reason:
Hang on rcs0, action: reset
[ 2245.773241] [drm] GPU hangs can indicate a bug anywhere in the entire gfx
stack, including userspace.
[ 2245.773241] [drm] Please file a _new_ bug report on bugs.freedesktop.org
against DRI -> DRM/Intel
[ 2245.773242] [drm] drm/i915 developers can then reassign to the right
component if it's not a kernel issue.
[ 2245.773242] [drm] The gpu crash dump is required to analyze gpu hangs, so
please always attach it.
[ 2245.773242] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 2245.773247] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2246.883491] asynchronous wait on fence i915:gnome-shell[1994]/1:a0fd timed
out
[ 2253.763721] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2261.763886] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2269.924050] i915 0000:00:02.0: Resetting rcs0 after gpu hang
[ 2277.828202] i915 0000:00:02.0: Resetting rcs0 after gpu hang
$ glxinfo | grep "OpenGL version"
OpenGL version string: 3.0 Mesa 17.2.4
The same problem occurs with Mesa 17.0.7 and kernel 4.13.
Please let me know what other information I can provide to help with this.
--
You are receiving this mail because:
You are the assignee for the bug.
You are on the CC list for the bug.
You are the QA Contact for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20171202/4ccf922b/attachment.html>
More information about the intel-gfx-bugs
mailing list