From: "Mallesh, Koujalagi" <mallesh.koujalagi@intel.com>
To: "Tauro, Riana" <riana.tauro@intel.com>,
Kamil Konieczny <kamil.konieczny@linux.intel.com>,
<igt-dev@lists.freedesktop.org>, <anshuman.gupta@intel.com>,
<vinay.belgaumkar@intel.com>, <badal.nilawar@intel.com>,
<karthik.poosa@intel.com>, <sk.anirban@intel.com>,
<raag.jadav@intel.com>, Nishit Sharma <nishit.sharma@intel.com>,
"Shuicheng Lin" <shuicheng.lin@intel.com>
Subject: Re: [PATCH] tests/intel/xe_wedged: ignore expected CORE_COMPUTE error in dmesg
Date: Fri, 16 Oct 2026 11:56:58 +0530 [thread overview]
Message-ID: <9e741a1f-c4fa-4c83-b838-0e32d63d4bdd@intel.com> (raw)
In-Reply-To: <f5584f42-6f36-4dc9-bf7b-6e7c7b4385fa@intel.com>
On 16-10-2026 11:05 am, Tauro, Riana wrote:
>
> On 14-10-2026 19:24, Kamil Konieczny wrote:
>> Hi Mallesh,
>> On 2026-10-14 at 17:20:47 +0530, Mallesh Koujalagi wrote:
>>> Wedge tests intentionally force a GT reset failure, which can trigger
>>> a CORE_COMPUTE hardware error (SIGID=203) in dmesg.
>>>
>>> Ignore this expected error so igt_runner does not treat it as a test
>>> failure.
>>>
>> Add cc before your s-o-b, also add few more devs found by git blame,
>> so also +cc
>>
>> Nishit Sharma <nishit.sharma@intel.com>
>> Shuicheng Lin <shuicheng.lin@intel.com>
>>
>>> Signed-off-by: Mallesh Koujalagi <mallesh.koujalagi@intel.com>
>>> Cc: Riana Tauro <riana.tauro@intel.com>
>>> ---
>>> tests/intel/xe_wedged.c | 3 ++-
>>> 1 file changed, 2 insertions(+), 1 deletion(-)
>>>
>>> diff --git a/tests/intel/xe_wedged.c b/tests/intel/xe_wedged.c
>>> index 4f5197e2a..fe8ea6969 100644
>>> --- a/tests/intel/xe_wedged.c
>>> +++ b/tests/intel/xe_wedged.c
>>> @@ -54,7 +54,8 @@ static void ignore_wedged_in_dmesg(void)
>>> "|EngineClass: [0-9]+ [a-z]+"
>>> "|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]*: Engine memory CAT
>>> error"
>>> + "|SIGID=203");
>> LGTM
>> Reviewed-by: Kamil Konieczny <kamil.konieczny@linux.intel.com>
>
>
> We have to ignore this string as well
>
> *ERROR* Tile0: GT0: GuC: Uncorrectable local error!
Patch is already merged, so I'll create follow up patch to ignore
string "Tile0: GT0: GuC: Uncorrectable local error! ".
like:
Tile[0-9]+: GT[0-9A-Fa-f]*: GuC: Uncorrectable local error!"
Thanks,
-/Mallesh
>
> Thanks
> Riana
>
>>
>> Regards,
>> Kamil
>>
>>> }
>>> static void force_wedged(int fd)
>>> --
>>> 2.48.1
>>>
next prev parent reply other threads:[~2026-10-16 6:28 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-14 11:50 [PATCH] tests/intel/xe_wedged: ignore expected CORE_COMPUTE error in dmesg Mallesh Koujalagi
2026-10-14 13:54 ` Kamil Konieczny
2026-10-15 3:43 ` Mallesh, Koujalagi
2026-10-16 5:35 ` Tauro, Riana
2026-10-16 6:26 ` Mallesh, Koujalagi [this message]
2026-10-14 18:03 ` ✓ i915.CI.BAT: success for " Patchwork
2026-10-15 1:20 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-15 2:49 ` ✗ i915.CI.Full: failure " Patchwork
2026-10-15 11:23 ` ✗ Xe.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=9e741a1f-c4fa-4c83-b838-0e32d63d4bdd@intel.com \
--to=mallesh.koujalagi@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=kamil.konieczny@linux.intel.com \
--cc=karthik.poosa@intel.com \
--cc=nishit.sharma@intel.com \
--cc=raag.jadav@intel.com \
--cc=riana.tauro@intel.com \
--cc=shuicheng.lin@intel.com \
--cc=sk.anirban@intel.com \
--cc=vinay.belgaumkar@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