Bug 96280 - gpu hang ecode 9:0:0x85df7eff, in gnome-shell, reason: Engine(s) hung, action reset
Summary: gpu hang ecode 9:0:0x85df7eff, in gnome-shell, reason: Engine(s) hung, action...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: medium normal
Assignee: yann
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-30 20:00 UTC by Saul St John
Modified: 2017-07-27 16:51 UTC (History)
1 user (show)

See Also:
i915 platform: SKL
i915 features: GPU hang

Attachments
gpu crash dump (44.49 KB, application/x-bzip)
2016-05-30 20:00 UTC, Saul St John 		no flags Details
full dmesg listing (61.42 KB, text/plain)
2016-05-30 20:02 UTC, Saul St John 		no flags Details
xorg log (67.65 KB, text/x-log)
2016-05-30 20:03 UTC, Saul St John 		no flags Details
xrandr --verbose (9.64 KB, text/plain)
2016-05-30 20:03 UTC, Saul St John 		no flags Details
lspci -vv -xxx (2.53 KB, text/plain)
2016-05-30 20:04 UTC, Saul St John 		no flags Details
View All

Description Saul St John 2016-05-30 20:00:01 UTC 
Created attachment 124182 [details]
gpu crash dump

X froze up and I was worried because I had an unsaved document in VSCode, but it started working again when I switched VTs to a text console and back. dmesg says this:

[171847.897508] [drm] stuck on render ring
[171847.898299] [drm] GPU HANG: ecode 9:0:0x85df7eff, in gnome-shell [1340], reason: Engine(s) hung, action: reset
[171847.898300] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[171847.898301] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[171847.898302] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[171847.898302] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[171847.898303] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[171847.900998] drm/i915: Resetting chip after gpu hang
[171848.905509] [drm] RC6 on
[171857.873462] [drm] stuck on render ring
[171857.874186] [drm] GPU HANG: ecode 9:0:0x87f93ff9, in code [7592], reason: Engine(s) hung, action: reset
[171857.876842] drm/i915: Resetting chip after gpu hang
[171859.873489] [drm] RC6 on
[171867.885616] [drm] stuck on render ring
[171867.886320] [drm] GPU HANG: ecode 9:0:0x85dffeff, in gnome-shell [1340], reason: Engine(s) hung, action: reset
[171867.887615] drm/i915: Resetting chip after gpu hang
[171869.885604] [drm] RC6 on
[171877.909446] [drm] stuck on render ring
[171877.910100] [drm] GPU HANG: ecode 9:0:0x87f93ff9, in code [7592], reason: Engine(s) hung, action: reset
[171877.911445] drm/i915: Resetting chip after gpu hang
[171879.909671] [drm] RC6 on

...so I did.
Comment 1 Saul St John 2016-05-30 20:02:36 UTC 
Created attachment 124183 [details]
full dmesg listing
Comment 2 Saul St John 2016-05-30 20:03:00 UTC 
Created attachment 124184 [details]
xorg log
Comment 3 Saul St John 2016-05-30 20:03:19 UTC 
Created attachment 124185 [details]
xrandr --verbose
Comment 4 Saul St John 2016-05-30 20:04:01 UTC 
Created attachment 124186 [details]
lspci -vv -xxx
Comment 5 Jari Tahvanainen 2017-03-08 10:50:26 UTC 
Yann - can you please help here and check out the crash dump data for more details? 
saul.stjohn@gmail.com - have you seen this problem lately? Maybe on newer kernel from drm-tip.
Comment 6 Jari Tahvanainen 2017-05-23 11:27:11 UTC 
Timeout - assuming resolved+worksforme. Please reopen the bug with the new data from the latest kernel (preferable from drm-tip) if problem still persist.

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.