Summary: | [HSW] stuck on render ring, GPU HANG: ecode 0:0x85dffffd, in X [1773], reason: Ring hung, action: reset | ||
---|---|---|---|
Product: | Mesa | Reporter: | naduss <kolsjdldddd> |
Component: | Drivers/DRI/i965 | Assignee: | Ian Romanick <idr> |
Status: | RESOLVED INVALID | QA Contact: | |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | |||
i915 platform: | HSW | i915 features: | GPU hang |
Attachments: |
/sys/class/drm/card0/error
dmesg /sys/class/drm/card0/error gzipped Xorg log uname -a cpuinfo |
Description
naduss
2015-01-20 14:20:22 UTC
Created attachment 112549 [details]
dmesg
Created attachment 112550 [details]
/sys/class/drm/card0/error gzipped
Created attachment 112551 [details]
Xorg log
Created attachment 112552 [details]
uname -a
Created attachment 112553 [details]
cpuinfo
Happened to me when doing some WebGL-intensive work. The entire system hanged and required a reboot, though. 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 Please test a new version of Mesa (12 or 13) and mark as REOPENED if you can reproduce and RESOLVED/* if you cannot reproduce. 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.