* [PATCH v1] drm: Log recovery method with wedged event
@ 2026-10-19 2:58 Raag Jadav
2026-10-19 14:29 ` Christian König
0 siblings, 1 reply; 3+ messages in thread
From: Raag Jadav @ 2026-10-19 2:58 UTC (permalink / raw)
To: dri-devel
Cc: riana.tauro, mallesh.koujalagi, matthew.brost, rodrigo.vivi,
christian.koenig, andrealmeid, Raag Jadav
Currently, drm_dev_wedged_event() logs a basic message of device being
wedged, but doesn't print the recovery method used by the caller. Log it
for easier bug report analysis.
While at it, as the device wedging is a catastrophic event, raise its log
level to drm_warn().
Signed-off-by: Raag Jadav <raag.jadav@intel.com>
---
drivers/gpu/drm/drm_drv.c | 4 ++--
1 file changed, 2 insertions(+), 2 deletions(-)
diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
index cb53baa70995..1a1213f4235c 100644
--- a/drivers/gpu/drm/drm_drv.c
+++ b/drivers/gpu/drm/drm_drv.c
@@ -598,8 +598,8 @@ int drm_dev_wedged_event(struct drm_device *dev, unsigned long method,
/* Caller is unsure about recovery, do the best we can at this point. */
snprintf(event_string, sizeof(event_string), "%s", "WEDGED=unknown");
- drm_info(dev, "device wedged, %s\n", method == DRM_WEDGE_RECOVERY_NONE ?
- "but no recovery needed" : "needs recovery");
+ drm_warn(dev, "device wedged with method %#lx, %s\n", method,
+ method == DRM_WEDGE_RECOVERY_NONE ? "no recovery needed" : "needs recovery");
if (info && (info->comm[0] != '\0') && (info->pid >= 0)) {
snprintf(pid_string, sizeof(pid_string), "PID=%u", info->pid);
--
2.43.0
^ permalink raw reply related [flat|nested] 3+ messages in thread
* Re: [PATCH v1] drm: Log recovery method with wedged event
2026-10-19 2:58 [PATCH v1] drm: Log recovery method with wedged event Raag Jadav
@ 2026-10-19 14:29 ` Christian König
2026-10-19 22:00 ` Rodrigo Vivi
0 siblings, 1 reply; 3+ messages in thread
From: Christian König @ 2026-10-19 14:29 UTC (permalink / raw)
To: Raag Jadav, dri-devel
Cc: riana.tauro, mallesh.koujalagi, matthew.brost, rodrigo.vivi,
andrealmeid
On 10/19/26 04:58, Raag Jadav wrote:
> Currently, drm_dev_wedged_event() logs a basic message of device being
> wedged, but doesn't print the recovery method used by the caller. Log it
> for easier bug report analysis.
That sounds like a good idea to me.
> While at it, as the device wedging is a catastrophic event, raise its log
> level to drm_warn().
Device wedging is rarely something catastrophic but rather normal part of execution handling.
So I would rather object to that.
Regards,
Christian.
>
> Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> ---
> drivers/gpu/drm/drm_drv.c | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
> index cb53baa70995..1a1213f4235c 100644
> --- a/drivers/gpu/drm/drm_drv.c
> +++ b/drivers/gpu/drm/drm_drv.c
> @@ -598,8 +598,8 @@ int drm_dev_wedged_event(struct drm_device *dev, unsigned long method,
> /* Caller is unsure about recovery, do the best we can at this point. */
> snprintf(event_string, sizeof(event_string), "%s", "WEDGED=unknown");
>
> - drm_info(dev, "device wedged, %s\n", method == DRM_WEDGE_RECOVERY_NONE ?
> - "but no recovery needed" : "needs recovery");
> + drm_warn(dev, "device wedged with method %#lx, %s\n", method,
> + method == DRM_WEDGE_RECOVERY_NONE ? "no recovery needed" : "needs recovery");
>
> if (info && (info->comm[0] != '\0') && (info->pid >= 0)) {
> snprintf(pid_string, sizeof(pid_string), "PID=%u", info->pid);
^ permalink raw reply [flat|nested] 3+ messages in thread
* Re: [PATCH v1] drm: Log recovery method with wedged event
2026-10-19 14:29 ` Christian König
@ 2026-10-19 22:00 ` Rodrigo Vivi
0 siblings, 0 replies; 3+ messages in thread
From: Rodrigo Vivi @ 2026-10-19 22:00 UTC (permalink / raw)
To: Christian König
Cc: Raag Jadav, dri-devel, riana.tauro, mallesh.koujalagi,
matthew.brost, andrealmeid
On Mon, Oct 19, 2026 at 04:29:35PM +0200, Christian König wrote:
> On 10/19/26 04:58, Raag Jadav wrote:
> > Currently, drm_dev_wedged_event() logs a basic message of device being
> > wedged, but doesn't print the recovery method used by the caller. Log it
> > for easier bug report analysis.
>
> That sounds like a good idea to me.
+1
>
> > While at it, as the device wedging is a catastrophic event, raise its log
> > level to drm_warn().
>
> Device wedging is rarely something catastrophic but rather normal part of execution handling.
>
> So I would rather object to that.
right, unless it has some option to differentiate the temporary wedge by the
cathastrofic one I'd also prefer to keep the info.
>
> Regards,
> Christian.
>
> >
> > Signed-off-by: Raag Jadav <raag.jadav@intel.com>
> > ---
> > drivers/gpu/drm/drm_drv.c | 4 ++--
> > 1 file changed, 2 insertions(+), 2 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/drm_drv.c b/drivers/gpu/drm/drm_drv.c
> > index cb53baa70995..1a1213f4235c 100644
> > --- a/drivers/gpu/drm/drm_drv.c
> > +++ b/drivers/gpu/drm/drm_drv.c
> > @@ -598,8 +598,8 @@ int drm_dev_wedged_event(struct drm_device *dev, unsigned long method,
> > /* Caller is unsure about recovery, do the best we can at this point. */
> > snprintf(event_string, sizeof(event_string), "%s", "WEDGED=unknown");
> >
> > - drm_info(dev, "device wedged, %s\n", method == DRM_WEDGE_RECOVERY_NONE ?
> > - "but no recovery needed" : "needs recovery");
> > + drm_warn(dev, "device wedged with method %#lx, %s\n", method,
> > + method == DRM_WEDGE_RECOVERY_NONE ? "no recovery needed" : "needs recovery");
> >
> > if (info && (info->comm[0] != '\0') && (info->pid >= 0)) {
> > snprintf(pid_string, sizeof(pid_string), "PID=%u", info->pid);
>
^ permalink raw reply [flat|nested] 3+ messages in thread
end of thread, other threads:[~2026-10-19 22:01 UTC | newest]
Thread overview: 3+ messages (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2026-10-19 2:58 [PATCH v1] drm: Log recovery method with wedged event Raag Jadav
2026-10-19 14:29 ` Christian König
2026-10-19 22:00 ` Rodrigo Vivi
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.