summaryrefslogtreecommitdiff
path: root/drivers
diff options
context:
space:
mode:
authorRaag Jadav <raag.jadav@intel.com>2026-02-05 14:34:24 +0300
committerRodrigo Vivi <rodrigo.vivi@intel.com>2026-02-12 16:55:57 +0300
commit6d83ef1adaae89c2b85ec486ec90397538deba1b (patch)
tree6fdb15adb1d9a8d0768a36c3455e3d6422b48139 /drivers
parent1a3c0049b3f56278c9caf2784c53f6ab435fd12c (diff)
downloadlinux-6d83ef1adaae89c2b85ec486ec90397538deba1b.tar.xz
drm/xe: Update xe_device_declare_wedged() error log
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> Link: https://patch.msgid.link/20260205113424.1629204-1-raag.jadav@intel.com Signed-off-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
Diffstat (limited to 'drivers')
-rw-r--r--drivers/gpu/drm/xe/xe_device.c3
1 files changed, 2 insertions, 1 deletions
diff --git a/drivers/gpu/drm/xe/xe_device.c b/drivers/gpu/drm/xe/xe_device.c
index 743c18e0c580..4b68a2d55651 100644
--- a/drivers/gpu/drm/xe/xe_device.c
+++ b/drivers/gpu/drm/xe/xe_device.c
@@ -1308,7 +1308,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));
}