[Bug 111396] GPU HANG: ecode 9:0:0xedddfeff, reason: Hang on render ring, action: reset

[bugzilla-daemon at freedesktop.org]

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

--- Comment #4 from yugang <yugang.fan at intel.com> ---
for some init analysis from our side, current project is hard to switch to
latest upstream kernel or mesa due to production requirement, and we also met
another HANG and tracked in
https://bugs.freedesktop.org/show_bug.cgi?id=111395.

'''
GPU HANG: ecode 9:0:0xedddfeff, reason: Hang on render ring, action: reset

_ERROR: 0x00000000
FAULT_TLB_DATA: 0x00000002 0x072a312a_

ACTHD: 0x00000000 ff4b1770      <-- Instruction at this address is being parsed
by CS
IPEHR: 0x12020101                      <-  (head of the instruction which was
parsed previously)    <- MI_STORE_REGISTER_MEM

Also, there no bit set in error reg. This means there is no pagefault problem
(memory issue) at least.

ACTHD is what we need to take a look at here because it helps to point to the
actual 3D instructions being parsed by command streamer when GPU hang is
detected.
ACTHD value of “ACTHD: 0x00000000 ff4b1770” points to the GPU instruction at
the GTT space address, “0xff4b1770”

“0xff4b1770" points to "0x12020101", which is same value with IPEHR.

The MI_STORE_REGISTER_MEM command requests a register read from a specified
memory mapped register location in the device and store of that DWord to
memory. 
The register address is specified along with the command to perform the read.

_0xff4b1764: 0x12020101: MI_STORE_REGISTER_MEM
0xff4b1768: 0x00000000: dword 1
0xff4b176c: 0x00000000: dword 2
0xff4b1770: 0xd1160d0e: UNKNOWN_

-- 
You are receiving this mail because:
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-3d-bugs/attachments/20190816/32433766/attachment.html>