summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorChris Wilson <chris@chris-wilson.co.uk>2019-11-11 14:43:22 +0300
committerChris Wilson <chris@chris-wilson.co.uk>2019-11-11 14:46:40 +0300
commitdfd9c1b4eab124c16c3b59362c3640983bf79949 (patch)
treebdd9e746fbd74a6e3a5315f4995662435485123a
parent267c012635c2a5cdeedf6ccf85b57add3f7826b3 (diff)
downloadlinux-dfd9c1b4eab124c16c3b59362c3640983bf79949.tar.xz
drm/i915: Show guilty context name on GPU reset
We mention that we are resetting the GPU, and dump the device state for post mortem debugging. However, while that dump contains the active processes and the one flagged as causing the error, we do not always include that information in dmesg. Include the name of the guilty process in dmesg for reference. Signed-off-by: Chris Wilson <chris@chris-wilson.co.uk> Cc: Mika Kuoppala <mika.kuoppala@linux.intel.com> Cc: Tvrtko Ursulin <tvrtko.ursulin@intel.com> Reviewed-by: Mika Kuoppala <mika.kuoppala@linux.intel.com> Link: https://patchwork.freedesktop.org/patch/msgid/20191111114323.5833-4-chris@chris-wilson.co.uk
-rw-r--r--drivers/gpu/drm/i915/gt/intel_reset.c4
1 files changed, 4 insertions, 0 deletions
diff --git a/drivers/gpu/drm/i915/gt/intel_reset.c b/drivers/gpu/drm/i915/gt/intel_reset.c
index f03e000051c1..86d52383bf9d 100644
--- a/drivers/gpu/drm/i915/gt/intel_reset.c
+++ b/drivers/gpu/drm/i915/gt/intel_reset.c
@@ -87,6 +87,10 @@ static bool context_mark_guilty(struct i915_gem_context *ctx)
if (!i915_gem_context_is_bannable(ctx))
return false;
+ dev_notice(ctx->i915->drm.dev,
+ "%s context reset due to GPU hang\n",
+ ctx->name);
+
/* Record the timestamp for the last N hangs */
prev_hang = ctx->hang_timestamp[0];
for (i = 0; i < ARRAY_SIZE(ctx->hang_timestamp) - 1; i++)