[Bug 99598] [IVB] GPU HANG: ecode 7:0:0x85fffefa, in glmark2 [8458], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=99598

yann <yann.argotti at intel.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
      i915 features|                            |GPU hang
             Status|NEW                         |NEEDINFO
            Summary|[drm] stuck on render ring  |[IVB] GPU HANG: ecode
                   |GPU HANG: ecode             |7:0:0x85fffefa, in glmark2
                   |7:0:0x85fffefa              |[8458], reason: Ring hung,
                   |                            |action: reset
      i915 platform|                            |IVB

--- Comment #3 from yann <yann.argotti at intel.com> ---
According to mesa engineers, mesa only emits 3DSTATE_VERTEX_ELEMENTS on-demand
right before 3DPRIMITIVE.

So I recommend to update to latest version of xf86-video-intel since fix should
be already in and mark as REOPENED if you can reproduce (and attach fresh gpu
error dump) and RESOLVED/* if you cannot reproduce.

In addition, there are constant improvements pushed in kernel and Mesa that
will benefit to your system, so please re-test with latest kernel & Mesa (12 or
13).

In either case (still or not occurring), please confirm you config.

*Details:
- Kernel: 4.4.0-59-generic
- Platform: IvyBridge (PCI ID: 0x0152, PCI Revision: 0x09, PCI Subsystem:
1043:844d)
- Mesa: [Please confirm your version]
- xf86-video-intel: [Please confirm your version]

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

Batch extract (around 0x7cc98930):

0x7cc988ec:      0x78090003: 3DSTATE_VERTEX_ELEMENTS
0x7cc988f0:      0x02400000:    buffer 0: valid, type 0x0040, src offset 0x0000
bytes
0x7cc988f4:      0x11130000:    (X, Y, Z, 1.0), dst offset 0x00 bytes
0x7cc988f8:      0x06400000:    buffer 1: valid, type 0x0040, src offset 0x0000
bytes
0x7cc988fc:      0x11130000:    (X, Y, Z, 1.0), dst offset 0x00 bytes
0x7cc98900:      0x7b000005: 3DPRIMITIVE:
0x7cc98904:      0x00000004:    tri list sequential
0x7cc98908:      0x0000540c:    vertex count
0x7cc9890c:      0x00000000:    start vertex
0x7cc98910:      0x00000001:    instance count
0x7cc98914:      0x00000000:    start instance
0x7cc98918:      0x00000000:    index bias
0x7cc9891c:      0x7a000003: PIPE_CONTROL
0x7cc98920:      0x00101001:    no write, cs stall, render target cache flush,
depth cache flush,
0x7cc98924:      0x00000000:    destination address
0x7cc98928:      0x00000000:    immediate dword low
0x7cc9892c:      0x00000000:    immediate dword high
0x7cc98930:      0x7a000003: PIPE_CONTROL
0x7cc98934:      0x00000408:    no write, texture cache invalidate, constant
cache invalidate,
0x7cc98938:      0x00000000:    destination address
0x7cc9893c:      0x00000000:    immediate dword low
0x7cc98940:      0x00000000:    immediate dword high

-- 
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/20170130/1ebf93ee/attachment-0001.html>