From: "Tauro, Riana" <riana.tauro@intel.com>
To: Sk Anirban <sk.anirban@intel.com>, <igt-dev@lists.freedesktop.org>
Cc: <anshuman.gupta@intel.com>, <badal.nilawar@intel.com>,
<karthik.poosa@intel.com>, <raag.jadav@intel.com>,
<soham.purkait@intel.com>, <mallesh.koujalagi@intel.com>
Subject: Re: [PATCH v6 1/2] tests/intel/xe_survivability: update ignored dmesg regex
Date: Wed, 30 Sep 2026 14:46:44 +0530 [thread overview]
Message-ID: <8c517bfc-3bfb-4387-8313-3ece896ee761@intel.com> (raw)
In-Reply-To: <20260929032354.1971070-5-sk.anirban@intel.com>
On 29-09-2026 08:53, Sk Anirban wrote:
> The kernel now reports -ENOTRECOVERABLE when the device is wedged.
> As runtime-survivability deliberately wedges the device, update
> dmesg regex so igt_runner does not treat the expected error logs
> as failures.
>
> v2: Keep older error codes (Kamil)
> Modify regex (Kamil)
> v3: Modify regex (Riana)
> v4: Support sigid based logging (Riana)
> v5: Use constant sigid values instead of strings (Riana)
> v6: Fix strings (Riana)
>
> kernel implementation:
> https://patchwork.freedesktop.org/series/168780/
>
> Signed-off-by: Sk Anirban <sk.anirban@intel.com>
Reviewed-by: Riana Tauro <riana.tauro@intel.com>
> ---
> tests/intel/xe_survivability.c | 13 ++++++++++---
> 1 file changed, 10 insertions(+), 3 deletions(-)
>
> diff --git a/tests/intel/xe_survivability.c b/tests/intel/xe_survivability.c
> index 74488bbea..e63f2c063 100644
> --- a/tests/intel/xe_survivability.c
> +++ b/tests/intel/xe_survivability.c
> @@ -43,12 +43,19 @@ static char bus_addr[NAME_MAX];
> static void ignore_wedged_in_dmesg(void)
> {
> /* this is needed for igt_runner so it will ignore it */
> - igt_emit_ignore_dmesg_regex("GT[0-9A-Fa-f]*: failed to enable GuC scheduling policies: -ECANCELED"
> + igt_emit_ignore_dmesg_regex("GT[0-9A-Fa-f]*: failed to enable GuC scheduling policies: "
> + "(-ECANCELED|-ENOTRECOVERABLE)"
> + "|GT[0-9A-Fa-f]*: reset failed .(-ECANCELED|-ENOTRECOVERABLE)"
> "|CRITICAL: Xe has declared device [0-9A-Fa-f:.]* as wedged"
> - "|GT[0-9A-Fa-f]*: reset failed .-ECANCELED"
> + "|xe [0-9A-Fa-f:.]*:.*-ENOTRECOVERABLE"
> "|GT[0-9A-Fa-f]*: Failed to submit"
> "|Modules linked in:"
> - "|__pfx___drm_");
> + "|__pfx___drm_"
> + /* SIGID-based logging (newer kernels) */
> + "|IOCTLs and executions are now blocked"
> + "|SIGID=[0-9]+ .*GT: reset failed"
> + "|SIGID=102"
> + "|SIGID=103");
> }
>
> static bool check_survivability_mode_sysfs(void)
next prev parent reply other threads:[~2026-09-30 9:17 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 3:23 [PATCH v6 0/2] tests/intel/xe_survivability: update ignored dmesg regex Sk Anirban
2026-09-29 3:23 ` [PATCH v6 1/2] " Sk Anirban
2026-09-30 9:16 ` Tauro, Riana [this message]
2026-09-29 3:23 ` [PATCH v6 2/2] HAX intel-ci: Add xe_survivability to xe-fast-feedback Sk Anirban
2026-09-29 4:24 ` ✗ Xe.CI.BAT: failure for tests/intel/xe_survivability: update ignored dmesg regex (rev8) Patchwork
2026-09-29 4:47 ` ✓ i915.CI.BAT: success " Patchwork
2026-09-29 6:35 ` ✓ Xe.CI.FULL: " Patchwork
2026-09-29 9:16 ` ✗ i915.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=8c517bfc-3bfb-4387-8313-3ece896ee761@intel.com \
--to=riana.tauro@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=badal.nilawar@intel.com \
--cc=igt-dev@lists.freedesktop.org \
--cc=karthik.poosa@intel.com \
--cc=mallesh.koujalagi@intel.com \
--cc=raag.jadav@intel.com \
--cc=sk.anirban@intel.com \
--cc=soham.purkait@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