[Bug 93817] Skylake Intel HD Graphics 520 GPU HANG: ecode 9:0:0x87cafff2, in chrome [3189], reason: Ring hung, action: reset

[bugzilla-daemon at freedesktop.org]

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

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

           What    |Removed                     |Added
----------------------------------------------------------------------------
          Component|DRM/Intel                   |Drivers/DRI/i915
            Version|XOrg git                    |unspecified
         QA Contact|intel-gfx-bugs at lists.freede |
                   |sktop.org                   |
            Product|DRI                         |Mesa
           Assignee|intel-gfx-bugs at lists.freede |idr at freedesktop.org
                   |sktop.org                   |

--- Comment #1 from yann <yann.argotti at intel.com> ---
Sam, there were workaround for SKL and 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 the meantime, assigning to Mesa product.

>From this error dump, hung is happening in render ring batch with active head
at 0x2b85163c, with 0x78150009 (3D UNKNOWN: 3d_965 opcode = 0x7815) as IPEHR.

Batch extract (around 0x2b85163c):

0x2b851618:      0x00000000: MI_NOOP
Bad length 7 in (null), expected 6-6
0x2b85161c:      0x7b000005: 3DPRIMITIVE: fail sequential
0x2b851620:      0x00000104:    vertex count
0x2b851624:      0x00000006:    start vertex
0x2b851628:      0x00000000:    instance count
0x2b85162c:      0x00000001:    start instance
0x2b851630:      0x00000000:    index bias
0x2b851634:      0x00000000: MI_NOOP
0x2b851638:      0x78150009: 3D UNKNOWN: 3d_965 opcode = 0x7815
0x2b85163c:      0x00000003: MI_NOOP

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
You are the assignee for the bug.
You are on the CC list for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/intel-gfx-bugs/attachments/20160914/8baf42bb/attachment.html>