Bug 88630 - [HSW] stuck on render ring, GPU HANG: ecode 0:0x85dffffd, in X [1773], reason: Ring hung, action: reset
Summary: [HSW] stuck on render ring, GPU HANG: ecode 0:0x85dffffd, in X [1773], reason...
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: 2015-01-20 14:20 UTC by naduss
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 (439.69 KB, text/plain)
2015-01-20 14:20 UTC, naduss
Details
dmesg (42.28 KB, text/plain)
2015-01-20 14:20 UTC, naduss
Details
/sys/class/drm/card0/error gzipped (439.69 KB, application/octet-stream)
2015-01-20 14:22 UTC, naduss
Details
Xorg log (34.62 KB, text/plain)
2015-01-20 14:23 UTC, naduss
Details
uname -a (141 bytes, text/plain)
2015-01-20 14:24 UTC, naduss
Details
cpuinfo (1.91 KB, text/plain)
2015-01-20 14:25 UTC, naduss
Details

Description naduss 2015-01-20 14:20:22 UTC
Created attachment 112548 [details]
/sys/class/drm/card0/error

Similar/same? as https://bugs.freedesktop.org/show_bug.cgi?id=87560 and
https://bugs.freedesktop.org/show_bug.cgi?id=88411 but dmesg told me to create a new one.

Symptoms: X freezes for a few seconds, resumes afterwards fine.
Reproduce: consistently happens after several minutes of full screen video, e.g. through the youtube html5 player or mplayer.
Comment 1 naduss 2015-01-20 14:20:43 UTC
Created attachment 112549 [details]
dmesg
Comment 2 naduss 2015-01-20 14:22:27 UTC
Created attachment 112550 [details]
/sys/class/drm/card0/error gzipped
Comment 3 naduss 2015-01-20 14:23:18 UTC
Created attachment 112551 [details]
Xorg log
Comment 4 naduss 2015-01-20 14:24:12 UTC
Created attachment 112552 [details]
uname -a
Comment 5 naduss 2015-01-20 14:25:32 UTC
Created attachment 112553 [details]
cpuinfo
Comment 6 Yuval Adam 2016-02-03 15:13:03 UTC
Happened to me when doing some WebGL-intensive work. The entire system hanged and required a reboot, though.
Comment 7 yann 2016-09-29 13:21:45 UTC
We seem to have neglected the bug a bit, apologies.

There were improvements pushed in kernel and Mesa that will benefit to your system, so please re-test with latest kernel & Mesa to see if this issue is still occurring.

In parallel, assigning to Mesa product (please let me know if I am mistaken with this GPU Hang).

Kernel: 3.18.2-hardened-r1
Platform: Haswell (pci id: 0x0402)
Mesa: [Please confirm your mesa version]

From this error dump, hung is happening in render ring batch with active head at 0x01208298, with 0x7a000002 (PIPE_CONTROL) as IPEHR.

Batch extract (around 0x01208298):

0x01208264:      0x78090005: 3DSTATE_VERTEX_ELEMENTS
0x01208268:      0x0a000000:    buffer 2: valid, type 0x0000, src offset 0x0000 bytes
0x0120826c:      0x22220000:    (0.0, 0.0, 0.0, 0.0), dst offset 0x00 bytes
0x01208270:      0x0af60000:    buffer 2: valid, type 0x00f6, src offset 0x0000 bytes
0x01208274:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0x01208278:      0x0a850004:    buffer 2: valid, type 0x0085, src offset 0x0004 bytes
0x0120827c:      0x11230000:    (X, Y, 0.0, 1.0), dst offset 0x00 bytes
0x01208280:      0x782a0000: 3DSTATE_BINDING_TABLE_POINTERS_PS
0x01208284:      0x0000ff40:    dword 1
0x01208288:      0x7a000002: PIPE_CONTROL
0x0120828c:      0x00100002:    no write, cs stall, stall at scoreboard,
0x01208290:      0x00000000:
0x01208294:      0x00000000:
0x01208298:      0x78080003: 3DSTATE_VERTEX_BUFFERS
0x0120829c:      0x0800400c:    buffer 1: sequential, pitch 12b
0x012082a0:      0x01208390:    buffer address
0x012082a4:      0xffffffff:    max index
0x012082a8:      0x00000000:    mbz
Comment 8 yann 2016-11-04 15:49:45 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 9 Annie 2017-02-10 22:39:15 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.