Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for Use MI_MATH to apply RMW WA in LRC (rev3)
Date: Mon, 10 Mar 2025 17:31:12 +0100	[thread overview]
Message-ID: <888e00f8-dc32-4b6f-a6af-9be62409388a@intel.com> (raw)
In-Reply-To: <174146681147.6714.9590700088356022715@18a75f3d1eae>



On 08.03.2025 21:46, Patchwork wrote:
> == Series Details ==
> 
> Series: Use MI_MATH to apply RMW WA in LRC (rev3)
> URL   : https://patchwork.freedesktop.org/series/145732/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2777-066c46f28642479869d2d1dd27cc6ae476de4abc_full -> xe-pw-145732v3_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-145732v3_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-145732v3_full, please notify your bug team (I915-ci-infra@lists.freedesktop.org) to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   
> 
> Participating hosts (4 -> 4)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-145732v3_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_oa@buffer-size:
>     - shard-lnl:          [PASS][1] -> [FAIL][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2777-066c46f28642479869d2d1dd27cc6ae476de4abc/shard-lnl-5/igt@xe_oa@buffer-size.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-145732v3/shard-lnl-6/igt@xe_oa@buffer-size.html

Starting subtest: buffer-size
Starting dynamic subtest: rcs-0-256K
(xe_oa:4458) CRITICAL: Test assertion failure function
test_non_zero_reason, file ../tests/intel/xe_oa.c:2509:
(xe_oa:4458) CRITICAL: Failed assertion: !(oa_status &
DRM_XE_OASTATUS_BUFFER_OVERFLOW)
Dynamic subtest rcs-0-256K failed.

hmm, based on the below, this test should be suppressed, no?

> 
>   
> #### Suppressed ####
> 
>   The following results come from untrusted machines, tests, or statuses.
>   They do not affect the overall result.
> 
>   * {igt@xe_oa@buffer-size@rcs-0-256k}:
>     - shard-lnl:          [PASS][3] -> [FAIL][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2777-066c46f28642479869d2d1dd27cc6ae476de4abc/shard-lnl-5/igt@xe_oa@buffer-size@rcs-0-256k.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-145732v3/shard-lnl-6/igt@xe_oa@buffer-size@rcs-0-256k.html
> 
>   

  reply	other threads:[~2025-03-10 16:31 UTC|newest]

Thread overview: 52+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-03-03 17:35 [PATCH 0/5] Use MI_MATH to apply RMW WA in LRC Michal Wajdeczko
2025-03-03 17:35 ` [PATCH 1/5] drm/xe: Add MI_LOAD_REGISTER_REG command definition Michal Wajdeczko
2025-03-03 21:18   ` Matt Roper
2025-03-03 17:35 ` [PATCH 2/5] drm/xe: Add MI_MATH and ALU instruction definitions Michal Wajdeczko
2025-03-03 21:50   ` Matt Roper
2025-03-04 16:23   ` [PATCH v2 " Michal Wajdeczko
2025-03-03 17:35 ` [PATCH 3/5] drm/xe: Avoid reading RMW registers in emit_wa_job Michal Wajdeczko
2025-03-03 18:06   ` Lucas De Marchi
2025-03-03 18:47     ` Michal Wajdeczko
2025-03-04 16:50       ` Lucas De Marchi
2025-03-03 22:06   ` Matt Roper
2025-03-03 17:35 ` [PATCH 4/5] drm/xe/vf: Stop applying save-restore MMIOs if VF Michal Wajdeczko
2025-03-03 18:09   ` Lucas De Marchi
2025-03-03 22:16     ` Matt Roper
2025-03-03 22:16   ` Matt Roper
2025-03-03 17:35 ` [PATCH 5/5] drm/xe/vf: Unblock xe_rtp_process_to_sr for VFs Michal Wajdeczko
2025-03-03 22:17   ` Matt Roper
2025-03-11 10:52   ` [PATCH v2 " Michal Wajdeczko
2025-03-03 17:44 ` ✓ CI.Patch_applied: success for Use MI_MATH to apply RMW WA in LRC Patchwork
2025-03-03 17:44 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-03 17:46 ` ✓ CI.KUnit: success " Patchwork
2025-03-03 18:02 ` ✓ CI.Build: " Patchwork
2025-03-03 18:05 ` ✓ CI.Hooks: " Patchwork
2025-03-03 18:06 ` ✓ CI.checksparse: " Patchwork
2025-03-03 18:38 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-03 20:12 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-04 17:27 ` ✓ CI.Patch_applied: success for Use MI_MATH to apply RMW WA in LRC (rev2) Patchwork
2025-03-04 17:27 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-04 17:28 ` ✓ CI.KUnit: success " Patchwork
2025-03-04 17:45 ` ✓ CI.Build: " Patchwork
2025-03-04 17:47 ` ✓ CI.Hooks: " Patchwork
2025-03-04 17:48 ` ✓ CI.checksparse: " Patchwork
2025-03-05  5:43 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-03-07 16:34   ` Michal Wajdeczko
2025-03-07 18:12 ` ✓ CI.Patch_applied: success for Use MI_MATH to apply RMW WA in LRC (rev3) Patchwork
2025-03-07 18:13 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-07 18:14 ` ✓ CI.KUnit: success " Patchwork
2025-03-07 18:36 ` ✓ CI.Build: " Patchwork
2025-03-07 18:39 ` ✓ CI.Hooks: " Patchwork
2025-03-07 18:41 ` ✓ CI.checksparse: " Patchwork
2025-03-07 19:03 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-08 20:46 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-10 16:31   ` Michal Wajdeczko [this message]
2025-03-11 12:55 ` ✓ CI.Patch_applied: success for Use MI_MATH to apply RMW WA in LRC (rev4) Patchwork
2025-03-11 12:55 ` ✗ CI.checkpatch: warning " Patchwork
2025-03-11 12:56 ` ✓ CI.KUnit: success " Patchwork
2025-03-11 13:13 ` ✓ CI.Build: " Patchwork
2025-03-11 13:15 ` ✓ CI.Hooks: " Patchwork
2025-03-11 13:17 ` ✓ CI.checksparse: " Patchwork
2025-03-11 13:37 ` ✓ Xe.CI.BAT: " Patchwork
2025-03-12  5:41 ` ✗ Xe.CI.Full: failure " Patchwork
2025-03-12 10:34   ` Michal Wajdeczko

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=888e00f8-dc32-4b6f-a6af-9be62409388a@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    /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