Bug 98488

Summary: GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell [1460], reason: Hang on render ring, action: reset
Product: DRI Reporter: Chris Murphy <bugzilla>
Component: DRM/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: CLOSED DUPLICATE QA Contact: Intel GFX Bugs mailing list <intel-gfx-bugs>
Severity: normal    
Priority: medium CC: intel-gfx-bugs
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: All   
Whiteboard:
i915 platform: SKL i915 features: GPU hang
Attachments:
Description Flags
cpuinfo
none
dmesg
none
dmidecode
none
gpu crash dump
none
journalctl -b -o short-monotonic
none
lspci none

Description Chris Murphy 2016-10-28 23:34:03 UTC 
Summary: Laptop recently cold booted, logged in, did some basic Terminal and Texedit stuff, walked away for ~10 minutes. Upon return, screen is black and doesn't respond to keyboard entry, and at monotonic time 5988-5990 I'm pressing the brightness up and down keys. Screen comes back on and I check kernel messages and find this:



[ 5290.337813] [drm] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell [1460], reason: Hang on render ring, action: reset
[ 5290.337818] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 5290.337820] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 5290.337822] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 5290.337825] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 5290.337828] [drm] GPU crash dump saved to /sys/class/drm/card0/error


So I'm filing a bug.

Hardware is an HP Spectre 13-v021nr
Comment 1 Chris Murphy 2016-10-28 23:34:52 UTC 
Created attachment 127595 [details]
cpuinfo
Comment 2 Chris Murphy 2016-10-28 23:35:05 UTC 
Created attachment 127596 [details]
dmesg
Comment 3 Chris Murphy 2016-10-28 23:35:18 UTC 
Created attachment 127597 [details]
dmidecode
Comment 4 Chris Murphy 2016-10-28 23:35:55 UTC 
Created attachment 127598 [details]
gpu crash dump
Comment 5 Chris Murphy 2016-10-28 23:36:34 UTC 
Created attachment 127599 [details]
journalctl -b -o short-monotonic
Comment 6 Chris Murphy 2016-10-28 23:36:57 UTC 
Created attachment 127600 [details]
lspci
Comment 7 Chris Murphy 2016-10-28 23:41:19 UTC 
Note, this is a GNOME on Wayland session.

kernel-4.8.4-301.fc25.x86_64
gnome-shell-3.22.1-2.fc25.x86_64
ibus-wayland-1.5.14-3.fc25.x86_64
libwayland-client-1.12.0-1.fc25.x86_64
libwayland-cursor-1.12.0-1.fc25.x86_64
gnome-session-wayland-session-3.22.1-2.fc25.x86_64
libwayland-server-1.12.0-1.fc25.x86_64
xorg-x11-server-Xwayland-1.19.0-0.3.20161026.fc25.x86_64
mesa-libwayland-egl-12.0.3-3.fc25.x86_64
Comment 8 Chris Wilson 2016-10-29 08:47:12 UTC 
Render ring missed a context-switch. Could do with more information from a drm-intel-nightly error state if possible.
Comment 9 Chris Murphy 2016-10-30 04:03:36 UTC 
If there's a how-to for comment 8, I'll do it. I've had this laptop for 4 weeks and this is the first time I've gotten this GPU hang, and the journal has only this one event. Also currently running kernel-4.9.0-0.rc2.git2.1.fc26.x86_64, does this contain what's needed to get more error info, or is it specific to the nightlies?
Comment 10 yann 2016-12-14 08:53:39 UTC 
seeing also bug 99057, and your log, it looks like to be a dup of bug 95063

*** This bug has been marked as a duplicate of bug 95063 ***

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.