Igt-dev Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <nishit.sharma@intel.com>, <shuicheng.lin@intel.com>,
	<kamil.konieczny@linux.intel.com>
Subject: Re: [PATCH v2] tests/intel/xe_wedged: ignore expected GuC error in dmesg
Date: Thu, 22 Oct 2026 11:44:15 +0530	[thread overview]
Message-ID: <2d6af3e5-d280-459e-9e2e-4a473ba1e2d2@intel.com> (raw)
In-Reply-To: <11421d19-81d3-4c51-91bd-a064c08ee6b4@intel.com>


On 21-10-2026 10:28 am, Tauro, Riana wrote:
>
> On 21-10-2026 10:19, Mallesh Koujalagi wrote:
>> Ignore the expected GuC uncorrectable local error message seen
>> during wedge tests.
>>
>> Cc: Riana Tauro <riana.tauro@intel.com>
>> Cc: Nishit Sharma <nishit.sharma@intel.com>
>> Cc: Shuicheng Lin <shuicheng.lin@intel.com>
>> Cc: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>> Signed-off-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
>
> Please confirm if any logs are missing in this path for local errors 
> before merge.
>
Yes, all local error logs from the xe_guc_uncorrectable_error_handler() 
path are covered.

I don't see any missing logs.

> This patch looks good to me.
> Reviewed-by: Riana Tauro <riana.tauro@intel.com>

Thanks Riana!

>
>
>> ---
>> v2:
>> - Remove '!' and short the string. (Kamil)
>> ---
>>   tests/intel/xe_wedged.c | 1 +
>>   1 file changed, 1 insertion(+)
>>
>> diff --git a/tests/intel/xe_wedged.c b/tests/intel/xe_wedged.c
>> index fe8ea6969..ba7efbe1d 100644
>> --- a/tests/intel/xe_wedged.c
>> +++ b/tests/intel/xe_wedged.c
>> @@ -55,6 +55,7 @@ static void ignore_wedged_in_dmesg(void)
>>                       "|EngineInstance: [0-9]+"
>>                       "|Tile[0-9]+: GT[0-9A-Fa-f]*: Fault response: 
>> Unsuccessful -EINVAL"
>>                       "|Tile[0-9]+: GT[0-9A-Fa-f]*: Engine memory CAT 
>> error"
>> +                    "|Tile[0-9]+: GT[0-9A-Fa-f]*: GuC: Uncorrectable"
>>                       "|SIGID=203");
>>   }

  reply	other threads:[~2026-10-22  6:15 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-10-21  4:49 [PATCH v2] tests/intel/xe_wedged: ignore expected GuC error in dmesg Mallesh Koujalagi
2026-10-21  4:58 ` Tauro, Riana
2026-10-22  6:14   ` Mallesh, Koujalagi [this message]
2026-10-21  5:25 ` ✓ Xe.CI.BAT: success for tests/intel/xe_wedged: ignore expected GuC error in dmesg (rev2) Patchwork
2026-10-21  5:40 ` ✓ i915.CI.BAT: " Patchwork
2026-10-21  7:09 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-10-21  8:46 ` ✗ i915.CI.Full: " 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=2d6af3e5-d280-459e-9e2e-4a473ba1e2d2@intel.com \
    --to=mallesh.koujalagi@intel.com \
    --cc=igt-dev@lists.freedesktop.org \
    --cc=kamil.konieczny@linux.intel.com \
    --cc=nishit.sharma@intel.com \
    --cc=riana.tauro@intel.com \
    --cc=shuicheng.lin@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