Bug 98539 - [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [503], reason: Hang on render ring, action: reset
Summary: [SKL] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [503], reason: Hang on render r...
Status: RESOLVED INVALID
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
URL:
Whiteboard:
Keywords:
: 98587 (view as bug list)
Depends on:
Blocks:
 
Reported: 2016-11-02 05:42 UTC by Jethro Beekman
Modified: 2017-02-10 22:38 UTC (History)
2 users (show)

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


Attachments
Contents of /sys/class/drm/card0/error (133.49 KB, text/plain)
2016-11-02 05:42 UTC, Jethro Beekman
Details

Description Jethro Beekman 2016-11-02 05:42:58 UTC
Created attachment 127681 [details]
Contents of /sys/class/drm/card0/error

[85104.218062] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [503], reason: Hang on render ring, action: reset
[85104.218066] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[85104.218068] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[85104.218070] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[85104.218072] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[85104.218075] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[85104.218189] drm/i915: Resetting chip after gpu hang
[85104.218528] [drm] GuC firmware load skipped
[85106.137288] [drm] RC6 on

Filing bug report as request. Happy to provide more information if needed.
Comment 1 yann 2016-11-03 15:18:05 UTC
Please confirm current version of Mesa on your system and ensure that you are using latest one.

In parallel, assigning to Mesa product.

Kernel: 4.8.4-1-ARCH
Platform: Skylake (pci id: 0x1926, pci revision: 0x0a, pci subsystem: 1028:06dc)
Mesa: [Please confirm your mesa version]

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

Batch extract (around 0xff02c920):

0xff02c900:      0x78090005: 3DSTATE_VERTEX_ELEMENTS
0xff02c904:      0x02000000:    buffer 0: invalid, type 0x0000, src offset 0x0000 bytes
0xff02c908:      0x22220000:    (0.0, 0.0, 0.0, 0.0), dst offset 0x00 bytes
0xff02c90c:      0x02f60000:    buffer 0: invalid, type 0x00f6, src offset 0x0000 bytes
0xff02c910:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0xff02c914:      0x02f60004:    buffer 0: invalid, type 0x00f6, src offset 0x0004 bytes
0xff02c918:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
Bad length 7 in (null), expected 6-6
0xff02c91c:      0x7b000005: 3DPRIMITIVE: fail sequential
0xff02c920:      0x00000000:    vertex count
0xff02c924:      0x00000003:    start vertex
0xff02c928:      0x00000032:    instance count
0xff02c92c:      0x00000001:    start instance
0xff02c930:      0x00000000:    index bias
0xff02c934:      0x00000000: MI_NOOP
Comment 2 yann 2016-11-04 14:44:44 UTC
*** Bug 98587 has been marked as a duplicate of this bug. ***
Comment 3 yann 2016-11-04 14:47:22 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 4 Jethro Beekman 2016-11-05 18:00:04 UTC
I was using mesa 13.0.0rc2-2. I don't know how to reproduce but I'll let you know if it happens again.
Comment 5 Sven Schwedas 2016-12-05 09:09:06 UTC
I've seen the same error happening with mesa 13.0.2, but I have no idea how to reproduce it either:

[30198.776454] [drm] GPU HANG: ecode 9:0:0x84dffff8, in Xorg [10675], reason: Hang on render ring, action: reset
[30198.776457] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[30198.776458] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[30198.776460] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[30198.776461] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[30198.776462] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[30198.776624] drm/i915: Resetting chip after gpu hang
[30198.776825] [drm] GuC firmware load skipped
[30200.696893] [drm] RC6 on
Comment 6 Annie 2017-02-10 22:38:27 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.