Bug 101075 - [drm] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell [1578], reason: Hang on render ring, action: reset
Summary: [drm] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell [1578], reason: Hang on ...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Chris Beelby
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-17 14:43 UTC by Chris Beelby
Modified: 2017-06-27 14:19 UTC (History)
1 user (show)

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


Attachments
kernel and system log showing various crash traces (2.08 MB, application/x-tar)
2017-05-17 14:43 UTC, Chris Beelby
no flags Details

Description Chris Beelby 2017-05-17 14:43:29 UTC
Created attachment 131388 [details]
kernel and system log showing various crash traces

These hangs occurr almost always after closing the laptop lid and waiting a bit and then re-opening the lid. There seems to be some connection between the GPU hang and also the WiFi having issues.
Comment 1 Chris Wilson 2017-05-18 22:07:57 UTC
Please attach /sys/class/drm/card0/error following a hang -- this is a dump of the gpu state at the time of the error, and our starting point for triage.
Comment 2 Chris Beelby 2017-05-30 18:50:01 UTC
Sorry I forgot to include that file originally and now it is not present on my system. I thought the same information it contained was also in the logs I did include but maybe it is not all the same (parts of it were definitely the same as I saw this). Also, while this error was happening regularly a couple weeks ago it nows seems to have stopped. I'm not sure if I installed a new version of some file (I am running on debian unstable) or something else has changed. Either way it seems at this point that I am not able to get that file you requested and since the issue seems to have stopped maybe we should just close this ticket and I can create a new one if it happens again. I'll be sure to grab that file next time. Thanks.
Comment 3 Chris Wilson 2017-05-30 19:23:09 UTC
A good chance that it did go away with an update, but if it does happen again please do reopen and attach the error state.


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.