Bug 96216 - [SKL] GPU HANG: ecode 9:0:0x85dfffff, in totem [1222], reason: Ring hung, action: reset
Summary: [SKL] GPU HANG: ecode 9:0:0x85dfffff, in totem [1222], reason: Ring hung, act...
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Intel 3D Bugs Mailing List
QA Contact: Intel 3D Bugs Mailing List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-25 18:06 UTC by ciri
Modified: 2017-02-10 22:39 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (614.50 KB, text/x-log)
2016-05-25 18:06 UTC, ciri
Details

Description ciri 2016-05-25 18:06:53 UTC
Created attachment 124087 [details]
/sys/class/drm/card0/error

This happens both in Chromium, Totem, and at other random moments in gnome.

[   96.353814] [drm] stuck on render ring
[   96.354034] [drm] GPU HANG: ecode 9:0:0x85dfffff, in totem [1222], reason: Ring hung, action: reset
[   96.354036] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[   96.354036] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[   96.354037] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[   96.354038] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[   96.354038] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[   96.356243] drm/i915: Resetting chip after gpu hang
[   98.334011] [drm] RC6 on
Comment 1 yann 2016-09-01 13:21:58 UTC
Assigning to Mesa product (please let me know if I am mistaken with this GPU Hang).

From this error dump, hung is happening in render ring batch with active head at 0xfc849a3c, with 0x7a000004 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0xfc849a3c):

Bad count in PIPE_CONTROL
0xfc849a0c:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC write flush, no inst flush
0xfc849a10:      0x00000000:    destination address
0xfc849a14:      0x00000000:    immediate dword low
0xfc849a18:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0xfc849a24:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC write flush, no inst flush
0xfc849a28:      0x00101c11:    destination address
0xfc849a2c:      0x00000000:    immediate dword low
0xfc849a30:      0x00000000:    immediate dword high
Bad length 8 in 3DSTATE_URB, expected 3-3
0xfc849a3c:      0x78050006: 3DSTATE_URB
0xfc849a40:      0x304c18ff:    VS entries 6399, alloc size 77 (1024bit row)
0xfc849a44:      0xf033a000:    GS entries 928, alloc size 1 (1024bit row)
0xfc849a5c:      0x78070003: 3D UNKNOWN: 3d_965 opcode = 0x7807
0xfc849a60:      0x0800067f: MI UNKNOWN
Comment 2 Matt Turner 2016-11-04 00:44:29 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 3 Annie 2017-02-10 22:39:14 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.