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 , 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
Created attachment 127595 [details]
Created attachment 127596 [details]
Created attachment 127597 [details]
Created attachment 127598 [details]
gpu crash dump
Created attachment 127599 [details]
journalctl -b -o short-monotonic
Created attachment 127600 [details]
Note, this is a GNOME on Wayland session.
Render ring missed a context-switch. Could do with more information from a drm-intel-nightly error state if possible.
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?
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 ***