[Bug 105236] New: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [3413], reason: Hang on rcs0, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Sun Feb 25 07:59:22 UTC 2018
https://bugs.freedesktop.org/show_bug.cgi?id=105236
Bug ID: 105236
Summary: [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [3413],
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: peter.van.hooft at gmail.com
QA Contact: intel-gfx-bugs at lists.freedesktop.org
CC: intel-gfx-bugs at lists.freedesktop.org
Created attachment 137585
--> https://bugs.freedesktop.org/attachment.cgi?id=137585&action=edit
/sys/class/drm/card0/error
Platform: HP Elitebook 840 G3, Fedora 27, kernel 4.15.4-300.fc27.x86_64.
mesa-dri-drivers-17.3.5-1.fc27.x86_64
xorg-x11-drv-intel-2.99.917-31.20171025.fc27.x86_64
After starting a graphical Java program the X server becomes unresponsive and
eventually I'm logged out:
[Sun Feb 25 08:40:41 2018] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
[3413], reason: Hang on rcs0, action: reset
[Sun Feb 25 08:40:41 2018] [drm] GPU hangs can indicate a bug anywhere in the
entire gfx stack, including userspace.
[Sun Feb 25 08:40:41 2018] [drm] Please file a _new_ bug report on
bugs.freedesktop.org against DRI -> DRM/Intel
[Sun Feb 25 08:40:41 2018] [drm] drm/i915 developers can then reassign to the
right component if it's not a kernel issue.
[Sun Feb 25 08:40:41 2018] [drm] The gpu crash dump is required to analyze gpu
hangs, so please always attach it.
[Sun Feb 25 08:40:41 2018] [drm] GPU crash dump saved to
/sys/class/drm/card0/error
--
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/20180225/579afc72/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list