Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: Umesh Nerlige Ramappa <umesh.nerlige.ramappa@intel.com>,
	<intel-xe@lists.freedesktop.org>, <rodrigo.vivi@intel.com>,
	<badal.nilawar@intel.com>, <riana.tauro@intel.com>,
	<michal.wajdeczko@intel.com>,
	<aravind.iddamsetty@linux.intel.com>
Subject: Re: [PATCH 2/2] drm/xe/ras: Report internal HW errors from PUNIT
Date: Wed, 19 Aug 2026 14:40:15 +0530	[thread overview]
Message-ID: <6e04a328-06ec-4d32-82b5-e8c408b83ba1@intel.com> (raw)
In-Reply-To: <20260818231716.731788-6-umesh.nerlige.ramappa@intel.com>

[-- Attachment #1: Type: text/plain, Size: 1441 bytes --]


On 19-08-2026 04:47 am, Umesh Nerlige Ramappa wrote:
> Report internal HW errors from PUNIT using the xe_log_comp() helper. Since
> the error results in a wedge, use CPER_SEV_FATAL as the severity.
>
> Signed-off-by: Umesh Nerlige Ramappa<umesh.nerlige.ramappa@intel.com>
> ---
>   drivers/gpu/drm/xe/xe_ras.c | 7 ++++---
>   1 file changed, 4 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/xe/xe_ras.c b/drivers/gpu/drm/xe/xe_ras.c
> index 13ae54afedf7..aa790571f716 100644
> --- a/drivers/gpu/drm/xe/xe_ras.c
> +++ b/drivers/gpu/drm/xe/xe_ras.c
> @@ -353,9 +353,10 @@ static u8 handle_soc_internal_errors(struct xe_device *xe, struct xe_ras_error_a
>   		struct xe_ras_ieh_error *ieh_error = (void *)info->details;
>   
>   		if (ieh_error->global_error_status & XE_RAS_SOC_IEH_PUNIT) {
> -			xe_err(xe, "[RAS]: PUNIT %s detected: 0x%x\n",
> -			       sev_to_str(counter->common.severity),
> -			       ieh_error->global_error_status);
> +			xe_log_comp(xe, CPER_SEV_FATAL, SOC_INTERNAL, counter, sizeof(*counter),

Please do n't hardcore severity, use counter->common.severityone.

For cper preparation, we need counter+response, need to confirm from @ 
Badal.

> +				    "PUNIT %s detected: 0x%x\n",
> +				    sev_to_str(counter->common.severity),

drop severity.

Thanks,

-/Mallesh

> +				    ieh_error->global_error_status);
>   			punit_error_handler(xe);
>   			return XE_RAS_RECOVERY_ACTION_DISCONNECT;
>   		}

[-- Attachment #2: Type: text/html, Size: 2355 bytes --]

  reply	other threads:[~2026-08-19  9:10 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-08-18 23:17 [PATCH 0/2] Convert some HW errors to use SIG ID helpers Umesh Nerlige Ramappa
2026-08-18 23:17 ` [PATCH 1/2] drm/xe/ras: Report internal HW errors from CSC Umesh Nerlige Ramappa
2026-08-19  9:05   ` Mallesh, Koujalagi
2026-08-19 18:34     ` Umesh Nerlige Ramappa
2026-08-18 23:17 ` [PATCH 2/2] drm/xe/ras: Report internal HW errors from PUNIT Umesh Nerlige Ramappa
2026-08-19  9:10   ` Mallesh, Koujalagi [this message]
2026-08-18 23:57 ` ✓ CI.KUnit: success for Convert some HW errors to use SIG ID helpers Patchwork
2026-08-19  0:34 ` ✓ Xe.CI.BAT: " Patchwork
2026-08-19  2:47 ` ✗ Xe.CI.FULL: failure " Patchwork

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=6e04a328-06ec-4d32-82b5-e8c408b83ba1@intel.com \
    --to=mallesh.koujalagi@intel.com \
    --cc=aravind.iddamsetty@linux.intel.com \
    --cc=badal.nilawar@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.wajdeczko@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=rodrigo.vivi@intel.com \
    --cc=umesh.nerlige.ramappa@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