[Bug 111981] New: i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000, hang on rcs0
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Oct 11 18:38:05 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111981
Bug ID: 111981
Summary: i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000,
hang on rcs0
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: not set
Priority: not set
Component: DRM/Intel
Assignee: intel-gfx-bugs at lists.freedesktop.org
Reporter: dgilbert at redhat.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 145713
--> https://bugs.freedesktop.org/attachment.cgi?id=145713&action=edit
contents of /sys/class/drm/card0/error
My dmesg told me to report this, who am I to argue!
(I didn't notice a hang, just noticed it in the dmesg).
Lenovo t580 running fedora 31, xfce desktop.
Linux dgilbert-t580.localhost 5.3.5-300.fc31.x86_64 #1 SMP Tue Oct 8 13:07:42
UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
[Fri Oct 11 17:53:37 2019] i915 0000:00:02.0: GPU HANG: ecode 9:0:0x00000000,
hang on rcs0
[Fri Oct 11 17:53:37 2019] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Fri Oct 11 17:53:37 2019] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Fri Oct 11 17:53:37 2019] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Fri Oct 11 17:53:37 2019] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Fri Oct 11 17:53:37 2019] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
[Fri Oct 11 17:53:37 2019] i915 0000:00:02.0: Resetting rcs0 for hang on rcs0
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list 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/20191011/c1f4dfa6/attachment.html>
More information about the intel-gfx-bugs
mailing list