[Bug 95396] GPU HANG: ecode 6:0:0x85fffffc, in Xorg [504], reason: Ring hung, action: reset
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Fri Sep 2 15:38:07 UTC 2016
https://bugs.freedesktop.org/show_bug.cgi?id=95396
yann <yann.argotti at intel.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Component|DRM/Intel |Drivers/DRI/i915
Product|DRI |Mesa
Assignee|intel-gfx-bugs at lists.freede |idr at freedesktop.org
|sktop.org |
Version|unspecified |git
QA Contact|intel-gfx-bugs at lists.freede |
|sktop.org |
--- Comment #1 from yann <yann.argotti at intel.com> ---
Assigning to Mesa product (please let me know if I am mistaken with this GPU
Hang).
>From this error dump, hung is happening in render ring batch with active head
at 0x76a68390, with 0x7a000003 (PIPE_CONTROL) as IPEHR.
Batch extract (around 0x76a68390):
0x76a68364: 0x7b001404: 3DPRIMITIVE: tri strip sequential
0x76a68368: 0x00000004: vertex count
0x76a6836c: 0x00000000: start vertex
0x76a68370: 0x00000001: instance count
0x76a68374: 0x00000000: start instance
0x76a68378: 0x00000000: index bias
0x76a6837c: 0x7a000003: PIPE_CONTROL
0x76a68380: 0x00100002: no write, cs stall, stall at scoreboard,
0x76a68384: 0x00000000: destination address
0x76a68388: 0x00000000: immediate dword low
0x76a6838c: 0x00000000: immediate dword high
0x76a68390: 0x7a000003: PIPE_CONTROL
0x76a68394: 0x00004000: qword write,
0x76a68398: 0x7fffe004: destination address
0x76a6839c: 0x00000000: immediate dword low
0x76a683a0: 0x00000000: immediate dword high
0x76a683a4: 0x780e0002: 3DSTATE_CC_STATE_POINTERS
0x76a683a8: 0x00006401: blend change 1
0x76a683ac: 0x00000000: depth stencil change 0
0x76a683b0: 0x00000000: cc change 0
--
You are receiving this mail because:
You are the QA Contact for the bug.
You are on the CC list for the bug.
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160902/27f1e154/attachment.html>
More information about the intel-gfx-bugs
mailing list