Bug 95396 - [SNB] GPU HANG: ecode 6:0:0x85fffffc, in Xorg [504], reason: Ring hung, action: reset
Summary: [SNB] GPU HANG: ecode 6:0:0x85fffffc, in Xorg [504], reason: Ring hung, actio...
Status: RESOLVED INVALID
Alias: None
Product: Mesa
Classification: Unclassified
Component: Drivers/DRI/i965 (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Ian Romanick
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-05-14 10:09 UTC by zetxx
Modified: 2017-02-10 22:38 UTC (History)
1 user (show)

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


Attachments
GPU crash dump (2.20 MB, text/plain)
2016-05-14 10:09 UTC, zetxx
Details

Description zetxx 2016-05-14 10:09:26 UTC
Created attachment 123743 [details]
GPU crash dump

WM: Xfce 4.12, did nothing gpu just hang 

DMESG:

[11353.135460] [drm] stuck on render ring
[11353.136080] [drm] GPU HANG: ecode 6:0:0x85fffffc, in Xorg [504], reason: Ring hung, action: reset
[11353.136082] [drm] GPU hangs can indicate a bug anywhere in the entire gfx stack, including userspace.
[11353.136083] [drm] Please file a _new_ bug report on bugs.freedesktop.org against DRI -> DRM/Intel
[11353.136084] [drm] drm/i915 developers can then reassign to the right component if it's not a kernel issue.
[11353.136085] [drm] The gpu crash dump is required to analyze gpu hangs, so please always attach it.
[11353.136086] [drm] GPU crash dump saved to /sys/class/drm/card0/error
[11353.138166] drm/i915: Resetting chip after gpu hang
Comment 1 yann 2016-09-02 15:38:07 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 0x76a68390, with 0x7a000003 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0x76a68390):

0x76a68364:      0x7b001404: 3DPRIMITIVE: tri strip sequential
0x76a68368:      0x00000004:    vertex count
0x76a6836c:      0x00000000:    start vertex
0x76a68370:      0x00000001:    instance count
0x76a68374:      0x00000000:    start instance
0x76a68378:      0x00000000:    index bias
0x76a6837c:      0x7a000003: PIPE_CONTROL
0x76a68380:      0x00100002:    no write, cs stall, stall at scoreboard,
0x76a68384:      0x00000000:    destination address
0x76a68388:      0x00000000:    immediate dword low
0x76a6838c:      0x00000000:    immediate dword high
0x76a68390:      0x7a000003: PIPE_CONTROL
0x76a68394:      0x00004000:    qword write,
0x76a68398:      0x7fffe004:    destination address
0x76a6839c:      0x00000000:    immediate dword low
0x76a683a0:      0x00000000:    immediate dword high
0x76a683a4:      0x780e0002: 3DSTATE_CC_STATE_POINTERS
0x76a683a8:      0x00006401:    blend change 1
0x76a683ac:      0x00000000:    depth stencil change 0
0x76a683b0:      0x00000000:    cc change 0
Comment 2 yann 2016-11-04 15:17:23 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:42 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.