Bug 98794 - [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [562], reason: Hang on render ring, action: reset
Summary: [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [562], reason: Hang on render r...
Status: RESOLVED DUPLICATE of bug 93166
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
: 98816 (view as bug list)
Depends on:
Reported: 2016-11-20 10:37 UTC by János Illés
Modified: 2016-12-20 15:34 UTC (History)
3 users (show)

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

gpu crash log (128.29 KB, text/plain)
2016-11-20 10:37 UTC, János Illés
GPU crash log (1.01 MB, text/plain)
2016-12-20 01:32 UTC, hvbakel

Description János Illés 2016-11-20 10:37:57 UTC
Created attachment 128081 [details]
gpu crash log

I had GPU hang and restart with the following text in the journal. 

 [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [562], 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] GuC firmware load skipped

The CPU is an Intel Core m7-6Y75 with HD Graphics 515

Running Linux kernel 4.8.7
Comment 1 yann 2016-11-21 08:05:51 UTC
There are constant improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa (12 or 13) to see if this issue is still occurring. mark as REOPENED	if you can reproduce and RESOLVED/* if you cannot reproduce.

In parallel, assigning to Mesa product.

Kernel: 4.8.7-pf
Platform: SKL (pci id: 0x191e, pci revision: 0x07, pci subsystem: 1043:1cfd)
Mesa: [Please confirm your mesa version]

From this error dump, hung is happening in render ring batch with active head at 0xea3377e8, with 0x7b000005 (3DPRIMITIVE) as IPEHR.

Batch extract (around 0xea3377e8):

0xea3377c8:      0x78090005: 3DSTATE_VERTEX_ELEMENTS
0xea3377cc:      0x02000000:    buffer 0: invalid, type 0x0000, src offset 0x0000 bytes
0xea3377d0:      0x22220000:    (0.0, 0.0, 0.0, 0.0), dst offset 0x00 bytes
0xea3377d4:      0x02f60000:    buffer 0: invalid, type 0x00f6, src offset 0x0000 bytes
0xea3377d8:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0xea3377dc:      0x02f60004:    buffer 0: invalid, type 0x00f6, src offset 0x0004 bytes
0xea3377e0:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
Bad length 7 in (null), expected 6-6
0xea3377e4:      0x7b000005: 3DPRIMITIVE: fail sequential
0xea3377e8:      0x00000000:    vertex count
0xea3377ec:      0x00000003:    start vertex
0xea3377f0:      0x0000006a:    instance count
0xea3377f4:      0x00000001:    start instance
0xea3377f8:      0x00000000:    index bias
0xea3377fc:      0x00000000: MI_NOOP
Comment 2 yann 2016-11-22 15:27:57 UTC
*** Bug 98816 has been marked as a duplicate of this bug. ***
Comment 3 hvbakel 2016-12-20 01:30:45 UTC
I'm experiencing the same issue on kernel 4.9.0 with mesa 13.0.2. CPU: i7-6560U, Iris Graphics 540 (Skylake GT3e). Crash log attached.
Comment 4 hvbakel 2016-12-20 01:32:16 UTC
Created attachment 128572 [details]
GPU crash log
Comment 5 Mark Janes 2016-12-20 15:34:24 UTC
Any crash in Xorg should be considered a duplicate of 93166 unless it can be reproduces with modesetting/glamor or using the tip of xf86-video-intel

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

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.