drm/i915: Capture the initial error-state when kicking stuck rings
We lost the ability to capture the first error for a stuck ring in the recent hangcheck robustification. Whilst both error states are interesting (why does the GPU not recover is also essential to debug), our primary goal is to fix the initial hang and so we need to capture the first error state upon taking hangcheck action. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Reviewed-by: Mika Kuoppala <mika.kuoppala@intel.com> Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>
This commit is contained in:
parent
4c445e0ebc
commit
09e14bf3ba
|
@ -1988,6 +1988,7 @@ ring_stuck(struct intel_ring_buffer *ring, u32 acthd)
|
|||
if (tmp & RING_WAIT) {
|
||||
DRM_ERROR("Kicking stuck wait on %s\n",
|
||||
ring->name);
|
||||
i915_handle_error(dev, false);
|
||||
I915_WRITE_CTL(ring, tmp);
|
||||
return HANGCHECK_KICK;
|
||||
}
|
||||
|
@ -1999,6 +2000,7 @@ ring_stuck(struct intel_ring_buffer *ring, u32 acthd)
|
|||
case 1:
|
||||
DRM_ERROR("Kicking stuck semaphore on %s\n",
|
||||
ring->name);
|
||||
i915_handle_error(dev, false);
|
||||
I915_WRITE_CTL(ring, tmp);
|
||||
return HANGCHECK_KICK;
|
||||
case 0:
|
||||
|
|
Loading…
Reference in New Issue