[Bug 91593] GPU HANG: ecode 8:0:0x85dffffb, in valley_x64 [8637], reason: Ring hung, action: reset

bugzilla-daemon at freedesktop.org bugzilla-daemon at freedesktop.org
Tue Sep 27 15:05:52 UTC 2016


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

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

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

--- Comment #3 from yann <yann.argotti at intel.com> ---
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: 4.1.3-200.fc22.x86_64
Platform: Broadwell-U (pci id: 0x1616)
Mesa: [Please confirm your mesa version]

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

We can also note:
ERROR: 0x00000001
    TLB page fault error (GTT entry not valid)
FAULT_TLB_DATA: 0x0000001c 0xe1b59da4
    Address 0x0000ce1b59da4000 GGTT

and in FAULT_REG of render ring: Invalid PTE Fault

Batch extract (around 0x18a04a94):

0x18a04a74:      0x78140000: 3D UNKNOWN: 3d_965 opcode = 0x7814
0x18a04a78:      0x80002044: UNKNOWN
Bad count in PIPE_CONTROL
0x18a04a7c:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0x18a04a80:      0x00101c11:    destination address
0x18a04a84:      0x00000000:    immediate dword low
0x18a04a88:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0x18a04a94:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0x18a04a98:      0x00002000:    destination address
0x18a04a9c:      0x00000000:    immediate dword low
0x18a04aa0:      0x00000000:    immediate dword high
Bad count in PIPE_CONTROL
0x18a04aac:      0x7a000004: PIPE_CONTROL: no write, no depth stall, no RC
write flush, no inst flush
0x18a04ab0:      0x00000001:    destination address
0x18a04ab4:      0x00000000:    immediate dword low
0x18a04ab8:      0x00000000:    immediate dword high

-- 
You are receiving this mail because:
You are on the CC list for the bug.
You are the QA Contact 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/20160927/85aa68cf/attachment-0001.html>


More information about the intel-gfx-bugs mailing list