Bug 98256 - [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1517], reason: Ring hung, action: reset
Summary: [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1517], reason: Ring hung, acti...
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium minor
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-10-14 12:41 UTC by Ed
Modified: 2017-02-10 22:38 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (61.80 KB, application/x-bzip)
2016-10-14 12:49 UTC, Ed
Details

Description Ed 2016-10-14 12:41:16 UTC
Stock Slackware 14.2 kernel 4.4.14 #2 SMP Fri Jun 24 13:38:27 CDT 2016 x86_64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz GenuineIntel GNU/Linux

X periodically hands for several seconds. dmesg output:

[drm] stuck on render ring
[ 1618.710208] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [1517], reason: Ring hung, action: reset
[ 1618.710212] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[ 1618.710214] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[ 1618.710216] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[ 1618.710218] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[ 1618.710220] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[ 1618.712532] drm/i915: Resetting chip after gpu hang
[ 1620.709900] [drm] RC6 on


attached: /sys/class/drm/card0/error
Comment 1 Ed 2016-10-14 12:49:52 UTC
Created attachment 127298 [details]
/sys/class/drm/card0/error
Comment 2 yann 2016-10-14 13:45:30 UTC
There were workaround for SKL and improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.

In parallel, assigning to Mesa product.

Kernel: 4.4.14
Platform: Skylake GT2 (pci id:0x191b)
Mesa: [Please confirm your mesa version]

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

Batch extract (around 0xddf64974):

0xddf64954:      0x78090005: 3DSTATE_VERTEX_ELEMENTS
0xddf64958:      0x02000000:    buffer 0: invalid, type 0x0000, src offset 0x0000 bytes
0xddf6495c:      0x22220000:    (0.0, 0.0, 0.0, 0.0), dst offset 0x00 bytes
0xddf64960:      0x02f60000:    buffer 0: invalid, type 0x00f6, src offset 0x0000 bytes
0xddf64964:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0xddf64968:      0x02f60004:    buffer 0: invalid, type 0x00f6, src offset 0x0004 bytes
0xddf6496c:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
Bad length 7 in (null), expected 6-6
0xddf64970:      0x7b000005: 3DPRIMITIVE: fail sequential
0xddf64974:      0x00000000:    vertex count
0xddf64978:      0x00000003:    start vertex
0xddf6497c:      0x00000c7a:    instance count
0xddf64980:      0x00000001:    start instance
0xddf64984:      0x00000000:    index bias
0xddf64988:      0x00000000: MI_NOOP
0xddf6498c:      0x784d0000: 3D UNKNOWN: 3d_965 opcode = 0x784d
Comment 3 Ed 2016-10-15 01:21:17 UTC
Mesa version 11.2.2
Comment 4 yann 2016-11-04 14:39:12 UTC
Please test a new version of Mesa (12 or 13) and mark as REOPENED
if you can reproduce and RESOLVED/* if you cannot reproduce.
Comment 5 Annie 2017-02-10 22:38:51 UTC
Dear Reporter,

This Mesa bug has been in the "NEEDINFO" status for over 60 days. I am closing this bug based on lack of response but feel free to reopen if resolution is still needed. Please ensure you're supplying the correct information as requested.

Thank you.


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.