Bug 100459 - GPU HANG: ecode 9:0:0x85dffffb, in X [2869], reason: Hang on render ring, action: reset
Summary: GPU HANG: ecode 9:0:0x85dffffb, in X [2869], reason: Hang on render ring, act...
Status: NEEDINFO
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-03-29 22:18 UTC by Jan Kundrát
Modified: 2018-03-21 20:23 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (757.36 KB, text/plain)
2017-03-29 22:18 UTC, Jan Kundrát
Details
dmesg (173.79 KB, text/plain)
2017-03-29 22:25 UTC, Jan Kundrát
Details
Xorg.0.log (54.51 KB, text/x-log)
2017-03-29 22:26 UTC, Jan Kundrát
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jan Kundrát 2017-03-29 22:18:40 UTC
Created attachment 130556 [details]
/sys/class/drm/card0/error

Kernel 4.9.18, Gentoo, Skylake i5-6300U, Thinkpad T460s, xorg-drivers-1.19, xorg-server-1.19.0, xorg-x11-7.4-r2, mesa oldish git 5f0e4c7c798827950e835d40912024480ec6d665 (built on 2016-12-05), KDE Plasma, kwin df306a4062ca946de34507a3e2be1d7178dfdf38 (built on 2017-03-06).

Here's what dmesg said:

[50141.741666] [drm] GPU HANG: ecode 9:0:0x85dffffb, in X [2869], reason: Hang on render ring, action: reset
[50141.741670] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[50141.741671] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[50141.741673] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[50141.741674] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[50141.741676] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[50141.741796] drm/i915: Resetting chip after gpu hang
[50141.742030] [drm] RC6 on
[50141.758485] [drm] GuC firmware load skipped
[50151.789804] drm/i915: Resetting chip after gpu hang
[50151.790021] [drm] RC6 on
[50151.805713] [drm] GuC firmware load skipped
[50151.828349] kscreen_backend[3160]: segfault at 10 ip 00007fd5e834944c sp 00007ffc6cf8b680 error 4 in KSC_XRandR.so[7fd5e8330000+22000]
[50153.951117] wlp4s0: deauthenticating from f4:f2:6d:18:f3:bd by local choice (Reason: 3=DEAUTH_LEAVING)

I'll be attaching the crash dump, what I have in the dmesg, and the Xorg log.
Comment 1 Jan Kundrát 2017-03-29 22:25:40 UTC
Created attachment 130557 [details]
dmesg
Comment 2 Jan Kundrát 2017-03-29 22:26:07 UTC
Created attachment 130558 [details]
Xorg.0.log
Comment 3 Christian Kreuzberger 2017-04-10 10:00:11 UTC
I am having the same issue with Ubuntu 16.04 on a Dell Optiplex 5040.
CPU: Intel(R) Core(TM) i5-6500 CPU @ 3.20GHz

At all times, my system used to freeze. This is the first time I was able to recover and got the following error in dmesg:

[10475.769692] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [1244], reason: Hang on render ring, action: reset
[10475.769694] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[10475.769696] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[10475.769696] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[10475.769697] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[10475.769699] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[10475.769784] drm/i915: Resetting chip after gpu hang
[10475.770004] [drm] GuC firmware load skipped
[10477.781755] [drm] RC6 on

I am trying the rc6 thing for kernel parameters now!
Comment 4 Elizabeth 2018-03-21 20:23:46 UTC
Hello, is this still reproducible with newer releases? How can this hang be triggered? 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.