Chris Wilson <[email protected]> writes: > 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 <[email protected]> > Cc: Mika Kuoppala <[email protected]> > Cc: Tvrtko Ursulin <[email protected]>
Reviewed-by: Mika Kuoppala <[email protected]> > --- > drivers/gpu/drm/i915/gt/intel_reset.c | 4 ++++ > 1 file changed, 4 insertions(+) > > 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++) > -- > 2.24.0 _______________________________________________ Intel-gfx mailing list [email protected] https://lists.freedesktop.org/mailman/listinfo/intel-gfx
