Bug 94268 - [ILK] GPU HANG: ecode 5:0:0x790af1fb, in chromium [23747], reason: Ring hung, action: reset
Summary: [ILK] GPU HANG: ecode 5:0:0x790af1fb, in chromium [23747], 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-02-23 19:59 UTC by Yury
Modified: 2017-02-10 22:38 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (1.52 MB, text/plain)
2016-02-23 19:59 UTC, Yury
Details

Description Yury 2016-02-23 19:59:20 UTC
Created attachment 121927 [details]
/sys/class/drm/card0/error

Hello, kernel ask me to file a bug,

[drm] stuck on render ring
[drm] GPU HANG: ecode 5:0:0x790af1fb, in chromium [23747], reason: Ring hung, action: reset

X.Org X Server 1.16.4, debian 8.
chromium 48.0.2564.82.
Comment 1 yann 2016-09-05 11:15:00 UTC
Assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head
at 0x07d4372c, with 0x79050004 (3DSTATE_DEPTH_BUFFER) as IPEHR.

Batch extract (around 0x07d4372c):


0x07d43700:      0x7a001002: PIPE_CONTROL: no write, no depth stall, RC write flush, no inst flush
0x07d43704:      0x00000000:    destination address
0x07d43708:      0x00000000:    immediate dword low
0x07d4370c:      0x00000000:    immediate dword high
0x07d43710:      0x78010004: 3DSTATE_BINDING_TABLE_POINTERS
0x07d43714:      0x00000000:    VS binding table
0x07d43718:      0x00000000:    GS binding table
0x07d4371c:      0x00000000:    Clip binding table
0x07d43720:      0x00000000:    SF binding table
0x07d43724:      0x00007040:    WM binding table
0x07d43728:      0x79050004: 3DSTATE_DEPTH_BUFFER
0x07d4372c:      0x2c081f7f:    2D, z24s8, pitch = 8064 bytes, tiled, HiZ 0, Separate Stencil 0
0x07d43730:      0x12ef1000:    depth offset
0x07d43734:      0x5db9f3c0:    2000x3000
0x07d43738:      0x00000000:    volume depth
0x07d4373c:      0x00000000:
0x07d43740:      0x02000000: MI_FLUSH
0x07d43744:      0x78000005: 3DSTATE_PIPELINED_POINTERS
0x07d43748:      0x07d49fa0:    VS state
0x07d4374c:      0x00000000:    GS state
0x07d43750:      0x07d49f41:    Clip state
0x07d43754:      0x07d49fc0:    SF state
0x07d43758:      0x07d4a000:    WM state
Comment 2 yann 2016-11-04 15:25:25 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:36 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.