drm/i915: Add reason for capture in error state

Browse source

We capture error state not only when the GPU hangs but also on
other situations as in interrupt errors and in situations where
we can kick things forward without GPU reset. There will be log
entry on most of these cases. But as error state capture might be
only thing we have, if dmesg was not captured. Or as in GEN4 case,
interrupt error can trigger error state capture without log entry,
the exact reason why capture was made is hard to decipher.

v2: Split out the the error code stuff to separate patch (Ben)

References: https://bugs.freedesktop.org/show_bug.cgi?id=74193
Signed-off-by: Mika Kuoppala <mika.kuoppala@intel.com>
Reviewed-by: Chris Wilson <chris@chris-wilson.co.uk>
Signed-off-by: Daniel Vetter <daniel.vetter@ffwll.ch>

...

This commit is contained in:

Mika Kuoppala 2014-02-25 17:11:26 +02:00 • committed by Daniel Vetter

parent cb38300215

commit 581744626d

4 changed files with 58 additions and 27 deletions

Show all changes Ignore whitespace when comparing lines Ignore changes in amount of whitespace Ignore changes in whitespace at EOL

Download patch file Download diff file Expand all files Collapse all files

5

drivers/gpu/drm/i915/i915_debugfs.c

View file

7

drivers/gpu/drm/i915/i915_drv.h

View file

27

drivers/gpu/drm/i915/i915_gpu_error.c

View file

46

drivers/gpu/drm/i915/i915_irq.c

View file