Bug 95201 - [HSW] GPU HANG: ecode 7:0:0x85dffffc, in gnome-shell [892], reason: Ring hung, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x85dffffc, in gnome-shell [892], reason: Ring hung...
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 normal
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-04-29 08:25 UTC by mrks
Modified: 2017-02-10 22:38 UTC (History)
1 user (show)

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


Attachments
Crash Dump (3.12 MB, text/plain)
2016-04-29 08:25 UTC, mrks
Details

Description mrks 2016-04-29 08:25:55 UTC
Created attachment 123341 [details]
Crash Dump

[142152.060178] [drm] GPU HANG: ecode 7:0:0x85dffffc, in gnome-shell [892], reason: Ring hung, action: reset
[142152.060179] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[142152.060179] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[142152.060180] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[142152.060180] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[142152.060181] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[142152.062301] drm/i915: Resetting chip after gpu hang
Comment 1 yann 2016-09-02 16:14:29 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 0x05693e28, with 0x7a000003 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0x05693e28):

0x05693df8:      0x7b000005: 3DPRIMITIVE:
0x05693dfc:      0x00000104:    tri list random
0x05693e00:      0x00000018:    vertex count
0x05693e04:      0x00000006:    start vertex
0x05693e08:      0x00000001:    instance count
0x05693e0c:      0x00000000:    start instance
0x05693e10:      0x00000000:    index bias
0x05693e14:      0x7a000003: PIPE_CONTROL
0x05693e18:      0x00101c11:    no write, cs stall, render target cache flush, instruction cache invalidate, texture cache invalidate, vf fetch invalidate, depth cache flush,
0x05693e1c:      0x00000000:    destination address
0x05693e20:      0x00000000:    immediate dword low
0x05693e24:      0x00000000:    immediate dword high
0x05693e28:      0x780e0000: 3DSTATE_CC_STATE_POINTERS
0x05693e2c:      0x000062c1:    pointer to COLOR_CALC_STATE at 0x000062c0 (changed)
Comment 2 yann 2016-11-04 15:18:53 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:38:43 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.