Bug 99251 - [KBL] [i915] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell, reason: Hang on render ring
Summary: [KBL] [i915] GPU HANG: ecode 9:0:0xfffffffe, in gnome-shell, reason: Hang on ...
Status: CLOSED FIXED
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-01-02 22:53 UTC by antcc
Modified: 2017-06-27 16:07 UTC (History)
1 user (show)

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


Attachments
GPU crash dump (45 bytes, application/gzip)
2017-01-02 22:53 UTC, antcc
no flags Details
Error dump (42.97 KB, application/gzip)
2017-01-30 14:27 UTC, Lionel Landwerlin
no flags Details

Description antcc 2017-01-02 22:53:31 UTC
Created attachment 128713 [details]
GPU crash dump

I left my laptop unattended for about 15 to 20 minutes. When I came back to it, it had a black screen, and it wouldn't respond to anything (trackpad, keyboard, short press of power button, etc). However, the light indicating that is was on was present, as well as the charging light (it was plugged in). I opted for long-pressing the power button and rebooting. Then it was back to normal.

I have auto-suspend turned off when charging, so it didn't try to sleep. Nevertheless, I had enabled the option to turn off the screen after being idle for 10 minutes, so it most likely tried to do that.

The situation described above did take place several times in the past month, but this is the first time that it resulted in a GPU hang.

System architecture: x86_64
Kernel Version: 4.9.0-nvme (Patched with NVME-patch from https://aur.archlinux.org/packages/linux-nvme/)
Linux Distribution: Arch Linux + GNOME 3.22
Machine: Dell XPS 13 9360 Developer Edition
Display connector: eDP

I have attached the GPU crash dump. It was recovered AFTER I had rebooted the machine.

Thanks in advance.
Comment 1 yann 2017-01-03 15:50:09 UTC
antcc, you may try to reproduce with latest nvme patched kernel (or from our latest tip branch: https://cgit.freedesktop.org/drm/drm-tip/). Moreover, did you try to switch to a VT? or connect via ssh?

As expected, attached gpu error dump does not contain any data since reboot reset gpu as well. Getting proper error dump and kernel log will help to locate / investigate the issue.
Comment 2 antcc 2017-01-03 15:55:31 UTC
(In reply to yann from comment #1)
> antcc, you may try to reproduce with latest nvme patched kernel (or from our
> latest tip branch: https://cgit.freedesktop.org/drm/drm-tip/). Moreover, did
> you try to switch to a VT? or connect via ssh?
> 
> As expected, attached gpu error dump does not contain any data since reboot
> reset gpu as well. Getting proper error dump and kernel log will help to
> locate / investigate the issue.

Hi yann,

I'm afraid I didn't try to switch to a VT or connect via ssh for that matter. I will try to reproduce and get a useful error dump.

Thanks
Comment 3 Lionel Landwerlin 2017-01-30 14:27:41 UTC
Created attachment 129232 [details]
Error dump

I had a similar crash several times already.
This time I was able to extract the dump \o/
Comment 4 Chris Wilson 2017-01-30 14:36:01 UTC
(In reply to Lionel Landwerlin from comment #3)
> Created attachment 129232 [details]
> Error dump
> 
> I had a similar crash several times already.
> This time I was able to extract the dump \o/

That is a missed context-switch interrupt. For starters, update to drm-tip to obtain better debug info, and probably a fix already.
Comment 5 Ricardo 2017-03-03 17:04:17 UTC
Lionel or antcc have you try Chris's suggestion to update to https://cgit.freedesktop.org/drm-tip and retest...
Comment 6 Jari Tahvanainen 2017-04-10 09:17:06 UTC
Timeout - assuming to be fixed in drm-tip. If problem still persist on latest kernel (preferable taken from drm-tip git://anongit.freedesktop.org/git/drm-tip), then reopen this with proper data attached (see https://01.org/linuxgraphics/documentation/how-report-bugs).


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.