]> git.ipfire.org Git - thirdparty/kernel/linux.git/commitdiff
drm/xe: Update xe_device_declare_wedged() error log
authorRaag Jadav <raag.jadav@intel.com>
Thu, 5 Feb 2026 11:34:24 +0000 (17:04 +0530)
committerRodrigo Vivi <rodrigo.vivi@intel.com>
Thu, 12 Feb 2026 13:55:57 +0000 (08:55 -0500)
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>
drivers/gpu/drm/xe/xe_device.c

index 743c18e0c580dad11698ae8a8ee19b0c9f44468e..4b68a2d5565122ac7e9e653b57ed7fe3e13070c9 100644 (file)
@@ -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));
        }