Bug 94160 - [HSW] GPU HANG: ecode 7:0:0x87d73c1a, in kodi.bin [26241], reason: Ring hung, action: reset
Summary: [HSW] GPU HANG: ecode 7:0:0x87d73c1a, in kodi.bin [26241], 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-15 14:19 UTC by Mathias
Modified: 2017-02-10 22:39 UTC (History)
1 user (show)

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


Attachments
/sys/class/drm/card0/error (425.81 KB, text/plain)
2016-02-15 14:19 UTC, Mathias
Details

Description Mathias 2016-02-15 14:19:11 UTC
Created attachment 121765 [details]
/sys/class/drm/card0/error

dmesg: http://nopaste.linux-dev.org/?942990
/sys/class/drm/card0/error ~500kB http://s000.tinyupload.com/index.php?file_id=08391695366219291034

00:02.0 VGA compatible controller: Intel Corporation Xeon E3-1200 v3/4th Gen Core Processor Integrated Graphics Controller (rev 06)

X.Org X Server 1.18.1, Release Date: 2016-02-08
xf86-video-intel 1:2.99.917+519+g8229390-1
kodi 15.2


I didn't experience any kodi playback issues just noticed this in dmesg.
Comment 1 yann 2016-09-05 11:28:27 UTC
Assigning to Mesa product.

From this error dump, hung is happening in render ring batch with active head
at 0x7e846ff0, with 0x78080003 (3DPRIMITIVE) as IPEHR.

Batch extract (around 0x7e846ff0):

0x7e846fbc:      0x7b000005: 3DPRIMITIVE:
0x7e846fc0:      0x00000007:    quad list sequential
0x7e846fc4:      0x000000cc:    vertex count
0x7e846fc8:      0x00000000:    start vertex
0x7e846fcc:      0x00000001:    instance count
0x7e846fd0:      0x00000000:    start instance
0x7e846fd4:      0x00000000:    index bias
0x7e846fd8:      0x782a0000: 3DSTATE_BINDING_TABLE_POINTERS_PS
0x7e846fdc:      0x00007360:    dword 1
0x7e846fe0:      0x782f0000: 3DSTATE_SAMPLER_STATE_POINTERS_PS
0x7e846fe4:      0x00007340:    dword 1
0x7e846fe8:      0x78080003: 3DSTATE_VERTEX_BUFFERS
0x7e846fec:      0x00014018:    buffer 0: sequential, pitch 24b
0x7e846ff0:      0x020bf1a0:    buffer address
0x7e846ff4:      0x020cafff:    max index
0x7e846ff8:      0x00000000:    mbz
0x7e846ffc:      0x78090005: 3DSTATE_VERTEX_ELEMENTS
0x7e847000:      0x02400000:    buffer 0: valid, type 0x0040, src offset 0x0000 bytes
0x7e847004:      0x11130000:    (X, Y, Z, 1.0), dst offset 0x00 bytes
0x7e847008:      0x02c7000c:    buffer 0: valid, type 0x00c7, src offset 0x000c bytes
0x7e84700c:      0x11110000:    (X, Y, Z, W), dst offset 0x00 bytes
0x7e847010:      0x02850010:    buffer 0: valid, type 0x0085, src offset 0x0010 bytes
0x7e847014:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
Comment 2 yann 2016-11-04 15:29:13 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.

If you can reproduce, please capture and upload an apitrace (https://github.com/apitrace/apitrace) so that we can easily 
reproduce as well.
Comment 3 Annie 2017-02-10 22:39:11 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.