Bug 105236 - [skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
Summary: [skl] GPU HANG: ecode 9:0:0x85dffffb, in Xorg
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-02-25 07:59 UTC by Peter van Hooft
Modified: 2018-03-06 18:14 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (40.24 KB, text/plain)
2018-02-25 07:59 UTC, Peter van Hooft
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter van Hooft 2018-02-25 07:59:22 UTC
Created attachment 137585 [details]
/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
Comment 1 Elizabeth 2018-03-06 18:14:46 UTC
Could you try to replicate with 17.3.6 and post results? Thank you.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.