[Bug 111424] Random recoverable GPU hangs in trivial GpuTest Triangle test
bugzilla-daemon at freedesktop.org
bugzilla-daemon at freedesktop.org
Mon Aug 19 10:33:22 UTC 2019
https://bugs.freedesktop.org/show_bug.cgi?id=111424
--- Comment #2 from Chris Wilson <chris at chris-wilson.co.uk> ---
The current sampling is ACTHD (batch/ring head address, updates with batch
buffer) + RING_START (to spot context switches) + RING_HEAD (includes wrap
counter so effectively ~24b). Only if they all match plus some fuzzing of
INSTDONE do we worry about the GPU being hung.
We could now throw in an engine->serial [submission serial] and only declare a
hang if we stop submitting (which would be CS freeze on execlists, and ring
full on ringbuffer). Or we can go with the heartbeat scheme.
If the drm-tip result is typical, the engine reset should be harmless.
--
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/20190819/3a06a782/attachment-0001.html>
More information about the intel-gfx-bugs
mailing list