Bug 99986 - [i915] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2122], reason: Hang on render ring, action: reset
Summary: [i915] [drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2122], reason: Hang on ...
Status: RESOLVED DUPLICATE of bug 103555
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Daniel J Blueman
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-02-27 12:52 UTC by Trygve Laugstøl
Modified: 2017-11-10 23:36 UTC (History)
5 users (show)

See Also:
i915 platform:
i915 features:


Attachments
/sys/class/drm/card0/error (793.13 KB, text/plain)
2017-02-27 12:52 UTC, Trygve Laugstøl
Details
/sys/class/drm/card0/error (755.49 KB, text/plain)
2017-03-07 09:35 UTC, Daniel J Blueman
Details
kernel log from 4.9.13 stock (83.90 KB, text/plain)
2017-03-07 09:35 UTC, Daniel J Blueman
Details
/sys/class/drm/card0/error (947.94 KB, text/plain)
2017-07-18 19:00 UTC, Klinisbu
Details

Description Trygve Laugstøl 2017-02-27 12:52:03 UTC
Created attachment 129951 [details]
/sys/class/drm/card0/error

[drm] GPU HANG: ecode 9:0:0x85dffffb, in Xorg [2122], reason: Hang on render ring, action: reset
[drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[drm] GPU crash dump saved to /sys/class/drm/card0/error
drm/i915: Resetting chip after gpu hang
[drm] RC6 on
[drm] GuC firmware load skipped
drm/i915: Resetting chip after gpu hang
[drm] RC6 on
[drm] GuC firmware load skipped
kicad[10372]: segfault at 55e302ac1350 ip 000055e302ac1350 sp 00007ffed51f7298 error 15
gnome-session-f[29773]: segfault at 0 ip 00007fa805afde09 sp 00007ffdfebe00d0 error 4 in libgtk-3.so.0.2200.8[7fa80581b000+6ff000]

This happened after about a day of uptime.

$ uname -m
x86_64

$ uname -r
4.9.0-2-amd64

Screen connection: display port
CPU: Intel(R) Core(TM) i7-6700K CPU @ 4.00GHz
Motherboard: Z170A GAMING M7 (MS-7976)
Comment 1 Trygve Laugstøl 2017-02-28 10:15:07 UTC
Forgot to mention that this is a Debian unstable system, exact kernel: 4.9.0-2-amd64 #1 SMP Debian 4.9.10-1 (2017-02-17) x86_64 GNU/Linux
Comment 2 Daniel J Blueman 2017-03-07 09:35:20 UTC
Created attachment 130107 [details]
/sys/class/drm/card0/error

I experience this on Ubuntu 16.04 (ElementaryOS) running Ubuntu mainline 4.9.13 after some hours of uptime.

Hardware is Dell XPS 9550 with current BIOS (1.2.19) and Skylake graphics (i7-6700HQ).
Comment 3 Daniel J Blueman 2017-03-07 09:35:47 UTC
Created attachment 130108 [details]
kernel log from 4.9.13 stock
Comment 4 Daniel J Blueman 2017-03-07 09:41:10 UTC
Packages:
xserver-xorg-video-intel-hwe-16.04 ver 2:2.99.917+git20160706-1ubuntu1~16.04.1
xorg-server-hwe-16.04 ver 2:1.18.4-1ubuntu6.1~16.04.1
xserver-xorg-hwe-16.04 ver 1:7.7+13ubuntu4~16.04.2
mesa-common-dev ver 11.2.0-1ubuntu2
libdrm-dev ver 2.4.67-1

Using internal panel only:
$ xrandr
Screen 0: minimum 320 x 200, current 3840 x 2160, maximum 8192 x 8192
eDP-1 connected primary 3840x2160+0+0 (normal left inverted right x axis y axis) 346mm x 194mm
   3840x2160     60.00*+
..

I believe this didn't occur before I installed the HWE updates above.
Comment 5 Klinisbu 2017-07-18 19:00:25 UTC
Created attachment 132746 [details]
/sys/class/drm/card0/error
Comment 6 Matt Turner 2017-11-10 23:36:08 UTC

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


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.