Bug 93818 - [HSW] GPU HANG: ecode 7:0:0x86d2fffd, in chrome [5415], reason: Ring hung, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x86d2fffd, in chrome [5415], reason: Ring hung, ac...
Status: CLOSED FIXED
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-01-22 01:29 UTC by Greg White
Modified: 2016-11-04 15:50 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (3.14 MB, text/plain)
2016-01-22 01:29 UTC, Greg White
Details

Description Greg White 2016-01-22 01:29:55 UTC
Created attachment 121199 [details]
/sys/class/drm/card0/error

I see this hang fairly frequently.  This is a mobile Haswell system.
Comment 1 yann 2016-09-14 16:09:23 UTC
Assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head at 0x0c569cc8, with 0x790d0002 (3DSTATE_MULTISAMPLE) as IPEHR.

Batch extract (around 0x0c569cc8):

0x0c569cac:      0x78240000: 3DSTATE_BLEND_STATE_POINTERS
0x0c569cb0:      0x00005941:    pointer to BLEND_STATE at 0x00005940 (changed)
0x0c569cb4:      0x780e0000: 3DSTATE_CC_STATE_POINTERS
0x0c569cb8:      0x00005901:    pointer to COLOR_CALC_STATE at 0x00005900 (changed)
0x0c569cbc:      0x78250000: 3DSTATE_DEPTH_STENCIL_STATE_POINTERS
0x0c569cc0:      0x000058c1:    pointer to DEPTH_STENCIL_STATE at 0x000058c0 (changed)
0x0c569cc4:      0x790d0002: 3DSTATE_MULTISAMPLE
0x0c569cc8:      0x00000006:    dword 1
0x0c569ccc:      0xdbb39d79:    dword 2
0x0c569cd0:      0x3ff55117:    dword 3
0x0c569cd4:      0x78180000: 3DSTATE_SAMPLE_MASK
0x0c569cd8:      0x000000ff:    dword 1
Comment 2 yann 2016-11-04 15:35:07 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.


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.