Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: Michal Wajdeczko <michal.wajdeczko@intel.com>
Cc: Varun Gupta <varun.gupta@intel.com>,
	<intel-xe@lists.freedesktop.org>, <zhanjun.dong@intel.com>,
	<daniele.ceraolospurio@intel.com>,
	<himal.prasad.ghimiray@intel.com>
Subject: Re: [PATCH v2] drm/xe/guc: Demote uncorrectable local error log to info
Date: Fri, 18 Sep 2026 10:35:36 -0400	[thread overview]
Message-ID: <aq1MOCcJoTYCMToP@intel.com> (raw)
In-Reply-To: <f49686d7-826d-4715-b04f-8818d6efc8d9@intel.com>

On Fri, Sep 18, 2026 at 09:50:48AM +0200, Michal Wajdeczko wrote:
> 
> 
> On 9/17/2026 3:53 PM, Varun Gupta wrote:
> > The UNCORRECTABLE_LOCAL_ERROR notification sent by the GuC indicates a
> > local, queue-level context termination rather than a global device or
> > driver failure. This can be triggered as part of expected recovery flows,
> > including intentional fault-injection tests.
> > 
> > Printing this at ERROR level is too noisy and causes false-positive
> > dmesg-warn failures in CI. Switch the log level to INFO, matching the
> > adjacent CAT error handler.
> > 
> > v2:
> >   - Also ratelimit the GUC_ID_UNKNOWN to match the CAT error handler.
> >     (Himal)
> > 
> > Fixes: 4e57574fa3a3 ("drm/xe/guc: Handle GuC local uncorrectable error notifications")
> > Signed-off-by: Varun Gupta <varun.gupta@intel.com>
> > ---
> >  drivers/gpu/drm/xe/xe_guc_submit.c | 8 ++++----
> >  1 file changed, 4 insertions(+), 4 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/xe/xe_guc_submit.c b/drivers/gpu/drm/xe/xe_guc_submit.c
> > index f3ba8abfc228..6144a1767f10 100644
> > --- a/drivers/gpu/drm/xe/xe_guc_submit.c
> > +++ b/drivers/gpu/drm/xe/xe_guc_submit.c
> > @@ -3487,7 +3487,7 @@ int xe_guc_uncorrectable_error_handler(struct xe_guc *guc, u32 *msg, u32 len)
> >  	guc_id = msg[0];
> >  
> >  	if (guc_id == GUC_ID_UNKNOWN) {
> 
> btw, shouldn't we check for guc_id >= GUC_ID_UNKNOWN?
> 
> > -		xe_gt_err(gt, "GuC: Uncorrectable local error with unknown GuC id\n");
> > +		xe_gt_err_ratelimited(gt, "GuC: Uncorrectable local error with unknown GuC id\n");
> >  		return 0;
> 
> if GuC shouldn't ever pass invalid guc-id here, as spec says this action is for:
> 
> 	"Notify the context which caused an uncorrectable local error to KMD"
> 
> then IMO instead of ratelimiting this error, we should rather escalate this
> to -EPROTO to force the error dump and reset from the CTB layer, no? 

Himal, next time please do not rush with committing patches like this.

There were 2 unadressed comments in it.

> 
> >  	}
> >  
> > @@ -3495,9 +3495,9 @@ int xe_guc_uncorrectable_error_handler(struct xe_guc *guc, u32 *msg, u32 len)
> >  	if (unlikely(!q))
> >  		return -EPROTO;
> >  
> > -	xe_gt_err(gt,
> > -		  "GuC: Uncorrectable local error! guc_id=%d class=%s, logical_mask=0x%x",
> > -		  guc_id, xe_hw_engine_class_to_str(q->class), q->logical_mask);
> > +	xe_gt_info(gt,

Again, this is a no no!

This is not a CAT ERROR that is expected in any page fault caused by the user.
If we hit this case it is a guc identified uncorrectable error!

Only come back with this idea if we can really justify why you can demote **all**
guc uncoorrectable errors to this.

The errors you mentioned in the commit message are not a good reason and should
be handled by the testing tools.

The patch was removed from the drm-xe-next. Please get back to the drawing board.

Thanks,
Rodrigo.

> > +		   "GuC: Uncorrectable local error! guc_id=%d class=%s, logical_mask=0x%x",
> > +		   guc_id, xe_hw_engine_class_to_str(q->class), q->logical_mask);
> >  
> >  	trace_xe_guc_uncorrectable_error(q);
> >  
> 

  reply	other threads:[~2026-09-18 14:35 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-17 13:53 [PATCH v2] drm/xe/guc: Demote uncorrectable local error log to info Varun Gupta
2026-09-17 14:05 ` ✓ CI.KUnit: success for drm/xe/guc: Demote uncorrectable local error log to info (rev3) Patchwork
2026-09-17 14:44 ` ✓ Xe.CI.BAT: " Patchwork
2026-09-17 16:04 ` ✓ Xe.CI.FULL: " Patchwork
2026-09-18  3:32 ` [PATCH v2] drm/xe/guc: Demote uncorrectable local error log to info Ghimiray, Himal Prasad
2026-09-18  7:50 ` Michal Wajdeczko
2026-09-18 14:35   ` Rodrigo Vivi [this message]
2026-09-18 16:23     ` Ghimiray, Himal Prasad
2026-09-29 19:02     ` Matt Roper
2026-09-29 19:47       ` Summers, Stuart

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=aq1MOCcJoTYCMToP@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=daniele.ceraolospurio@intel.com \
    --cc=himal.prasad.ghimiray@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@intel.com \
    --cc=varun.gupta@intel.com \
    --cc=zhanjun.dong@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox