Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Matthew Brost <matthew.brost@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.BAT: failure for Fix serialization on burst of unbinds - v2
Date: Mon, 3 Nov 2025 13:46:23 -0800	[thread overview]
Message-ID: <aQkir0rFTyWv8ZJN@lstrano-desk.jf.intel.com> (raw)
In-Reply-To: <176196828101.8736.6651475582499170446@10055242dc62>

On Sat, Nov 01, 2025 at 03:38:01AM +0000, Patchwork wrote:
> == Series Details ==
> 
> Series: Fix serialization on burst of unbinds - v2
> URL   : https://patchwork.freedesktop.org/series/156873/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-4027-089e83683d58db86cc4c69d34fba3a96904e40e1_BAT -> xe-pw-156873v1_BAT
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-156873v1_BAT absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-156873v1_BAT, 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 (12 -> 12)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-156873v1_BAT:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@xe_waitfence@reltime:
>     - bat-dg2-oem2:       [PASS][1] -> [FAIL][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4027-089e83683d58db86cc4c69d34fba3a96904e40e1/bat-dg2-oem2/igt@xe_waitfence@reltime.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156873v1/bat-dg2-oem2/igt@xe_waitfence@reltime.html

I haven't able to reproduce this one.

Matt

> 
>   
> Known issues
> ------------
> 
>   Here are the changes found in xe-pw-156873v1_BAT that come from known issues:
> 
> ### IGT changes ###
> 
> #### Possible fixes ####
> 
>   * igt@kms_flip@basic-plain-flip@d-edp1:
>     - bat-adlp-7:         [DMESG-WARN][3] ([Intel XE#4543]) -> [PASS][4] +1 other test pass
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4027-089e83683d58db86cc4c69d34fba3a96904e40e1/bat-adlp-7/igt@kms_flip@basic-plain-flip@d-edp1.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156873v1/bat-adlp-7/igt@kms_flip@basic-plain-flip@d-edp1.html
> 
>   
>   [Intel XE#4543]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/4543
> 
> 
> Build changes
> -------------
> 
>   * Linux: xe-4027-089e83683d58db86cc4c69d34fba3a96904e40e1 -> xe-pw-156873v1
> 
>   IGT_8605: 8605
>   xe-4027-089e83683d58db86cc4c69d34fba3a96904e40e1: 089e83683d58db86cc4c69d34fba3a96904e40e1
>   xe-pw-156873v1: 156873v1
> 
> == Logs ==
> 
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156873v1/index.html

  reply	other threads:[~2025-11-03 21:46 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-31 23:40 [PATCH v7 0/6] Fix serialization on burst of unbinds - v2 Matthew Brost
2025-10-31 23:40 ` [PATCH v7 1/6] drm/xe: Enforce correct user fence signaling order using Matthew Brost
2025-10-31 23:40 ` [PATCH v7 2/6] drm/xe: Attach last fence to TLB invalidation job queues Matthew Brost
2025-10-31 23:40 ` [PATCH v7 3/6] drm/xe: Decouple bind queue last fence from TLB invalidations Matthew Brost
2025-10-31 23:40 ` [PATCH v7 4/6] drm/xe: Skip TLB invalidation waits in page fault binds Matthew Brost
2025-10-31 23:40 ` [PATCH v7 5/6] drm/xe: Disallow input fences on zero batch execs and zero binds Matthew Brost
2025-10-31 23:40 ` [PATCH v7 6/6] drm/xe: Remove last fence dependency check from binds and execs Matthew Brost
2025-11-01  2:49 ` ✗ CI.checkpatch: warning for Fix serialization on burst of unbinds - v2 Patchwork
2025-11-01  2:50 ` ✓ CI.KUnit: success " Patchwork
2025-11-01  3:38 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-11-03 21:46   ` Matthew Brost [this message]
2025-11-01 22:55 ` ✓ Xe.CI.Full: success " Patchwork
  -- strict thread matches above, loose matches on Subject: below --
2025-10-31 18:09 [PATCH v6 0/6] " Matthew Brost
2025-10-31 21:10 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-10-27 18:27 [PATCH v4 0/5] " Matthew Brost
2025-10-27 19:13 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-10-24 22:20 [PATCH v3 0/2] " Matthew Brost
2025-10-24 23:15 ` ✗ Xe.CI.BAT: failure for " Patchwork
2025-10-24 15:23 [PATCH v2 0/2] " Matthew Brost
2025-10-24 16:40 ` ✗ Xe.CI.BAT: failure for " 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=aQkir0rFTyWv8ZJN@lstrano-desk.jf.intel.com \
    --to=matthew.brost@intel.com \
    --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