[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 #5 from Kenneth Graunke <kenneth at whitecape.org> ---
Now that I've looked more closely, this one looks especially strange.

1. The batchbuffer is supposedly 0xff4b0000, but the "Active (render ring)"
list includes this:

    00000000_ff4b0000    32768 3e 00 [ 7a0a 00 00 00 00 ] 00 Y dirty uncached

The batch buffer is...Y-tiled?  That's not right.  Plus, there seems to be very
little batch in the batch - it's *entirely* image garbage.  If anything, it
looks like we actually execbuf2'd an image which may have at one point
contained some batch commands due to BO cache reuse or something.

2. The hardware context is entirely garbage as well.  Even the headers and
basic structure are missing.  It's almost all zeroes.

I'm not sure that Mesa is likely to cause this much damage with a simple buffer
underallocation.  It may be possible, but a *lot* of data is clobbered, and in
multiple places which are not necessarily contiguous.

Chris, any more bright ideas?

-- 
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/20190821/66484f1d/attachment.html>