Re: [PATCH v1] drm/xe: Update xe_device_declare_wedged() error log

[Rodrigo Vivi <rodrigo.vivi@intel.com>]

On Thu, Feb 05, 2026 at 05:04:24PM +0530, Raag Jadav wrote:
> Since the introduction of DRM wedged event, there are now a few different
> procedures to recover the device depending on selected recovery method.
> Update the error log to reflect this and point the user to correct
> documentation for it.
> 
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>

Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>

and pushing this right now to drm-xe-next...

> ---
>  drivers/gpu/drm/xe/xe_device.c | 3 ++-
>  1 file changed, 2 insertions(+), 1 deletion(-)
> 
> diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
> index 815f0b0c9dfd..e59555896471 100644
> --- a/drivers/gpu/drm/xe/xe_device.c
> +++ b/drivers/gpu/drm/xe/xe_device.c
> @@ -1317,7 +1317,8 @@ void xe_device_declare_wedged(struct xe_device *xe)
>  		xe->needs_flr_on_fini = true;
>  		drm_err(&xe->drm,
>  			"CRITICAL: Xe has declared device %s as wedged.\n"
> -			"IOCTLs and executions are blocked. Only a rebind may clear the failure\n"
> +			"IOCTLs and executions are blocked.\n"
> +			"For recovery procedure, refer to https://docs.kernel.org/gpu/drm-uapi.html#device-wedging\n"
>  			"Please file a _new_ bug report at https://gitlab.freedesktop.org/drm/xe/kernel/issues/new\n",
>  			dev_name(xe->drm.dev));
>  	}
> -- 
> 2.43.0
>