From: Raag Jadav <raag.jadav@intel.com>
To: intel-xe@lists.freedesktop.org
Cc: matthew.brost@intel.com, rodrigo.vivi@intel.com,
riana.tauro@intel.com, michal.wajdeczko@intel.com,
matthew.d.roper@intel.com, lukasz.laguna@intel.com
Subject: Re: [PATCH v1] drm/xe: Update xe_device_declare_wedged() error log
Date: Thu, 12 Feb 2026 07:16:29 +0100 [thread overview]
Message-ID: <aY1wPW9SUUTeSwFW@black.igk.intel.com> (raw)
In-Reply-To: <20260205113424.1629204-1-raag.jadav@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>
> ---
Ping.
Raag
> 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
>
next prev parent reply other threads:[~2026-02-12 6:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 11:34 [PATCH v1] drm/xe: Update xe_device_declare_wedged() error log Raag Jadav
2026-02-05 13:28 ` ✓ CI.KUnit: success for " Patchwork
2026-02-05 14:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-06 12:12 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-12 6:16 ` Raag Jadav [this message]
2026-02-12 13:55 ` [PATCH v1] " Rodrigo Vivi
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aY1wPW9SUUTeSwFW@black.igk.intel.com \
--to=raag.jadav@intel.com \
--cc=intel-xe@lists.freedesktop.org \
--cc=lukasz.laguna@intel.com \
--cc=matthew.brost@intel.com \
--cc=matthew.d.roper@intel.com \
--cc=michal.wajdeczko@intel.com \
--cc=riana.tauro@intel.com \
--cc=rodrigo.vivi@intel.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.