[Bug 97968] [i915] GPU HANG: ecode 9:0:0xfffffffe (Team Fortress 2)

[bugzilla-daemon at freedesktop.org]

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

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

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

--- Comment #6 from yann <yann.argotti at intel.com> ---
(In reply to snrub from comment #5)
> Created attachment 126873 [details]
> Second crash dump

thanks for your quick feedback. So it looks like we have a different issue from
the original one. For the 1st one either disabling rc6 or ensuring that you are
updating to a kernel that has the commit

You may also try to update your mesa version if this is not already the case,
collect and attach logs collected thanks to apitrace:
http://apitrace.github.io/.

Regarding the last one, reassigning to Mesa (please let me know if I am
mistaken with this GPU Hang).


Kernel: 4.7.5-040705-generic
Platform: Skylake NUC Skull Canyon, Model nuc6i7kyk (pci id: 0x193b)
Mesa: [Please confirm your mesa version]

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

Batch extract (around 0xd4bb4594):

0xd4bb4548:      0x7b000005: 3DPRIMITIVE: fail sequential
0xd4bb454c:      0x00000104:    vertex count
0xd4bb4550:      0x0000000c:    start vertex
0xd4bb4554:      0x00001d3a:    instance count
0xd4bb4558:      0x00000001:    start instance
0xd4bb455c:      0x00000000:    index bias
0xd4bb4560:      0x00000000: MI_NOOP
Bad count in PIPE_CONTROL
0xd4bb4564:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0xd4bb4568:      0x0000a000:    destination address
0xd4bb456c:      0xddc6a008:    immediate dword low
0xd4bb4570:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0xd4bb457c:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0xd4bb4580:      0x00101001:    destination address
0xd4bb4584:      0x00000000:    immediate dword low
0xd4bb4588:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0xd4bb4594:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0xd4bb4598:      0x00000408:    destination address
0xd4bb459c:      0x00000000:    immediate dword low
0xd4bb45a0:      0x00000000:    immediate dword high
0xd4bb45ac:      0x78210000: 3D UNKNOWN: 3d_965 opcode = 0x7821
0xd4bb45b0:      0x00006680: MI_NOOP
0xd4bb45b4:      0x78240000: 3D UNKNOWN: 3d_965 opcode = 0x7824

-- 
You are receiving this mail because:
You are the assignee for the bug.
You are the QA Contact 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/20160929/131099fa/attachment-0001.html>