Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Summers, Stuart" <stuart.summers@intel.com>
To: "intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: Xe.CI.BAT: failure for Fix a couple of wedge corner-case memory leaks (rev4)
Date: Tue, 14 Oct 2025 21:14:54 +0000	[thread overview]
Message-ID: <a1b9e5b9f6402be37eb8593450f5731282b69047.camel@intel.com> (raw)
In-Reply-To: <176046920292.12561.3412450757967118718@97596180aaec>

On Tue, 2025-10-14 at 19:13 +0000, Patchwork wrote:
> Patch Details
> Series: Fix a couple of wedge corner-case memory leaks (rev4) URL:
> https://patchwork.freedesktop.org/series/155352/ State: failure
> Details:
> https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-155352v4/index.html 
> CI Bug Log - changes from xe-3920-
> b172f4e7a8beb0bae2feda7f7edfb49e661fd3be_BAT -> xe-pw-
> 155352v4_BATSummaryFAILURE
> Serious unknown changes coming with xe-pw-155352v4_BAT absolutely
> need to be
>  verified manually.
> If you think the reported changes have nothing to do with the changes
>  introduced in xe-pw-155352v4_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 (10 -> 10)No changes in participating hosts
> Possible new issuesHere are the unknown changes that may have been
> introduced in xe-pw-155352v4_BAT:
> IGT changesPossible regressions *
> igt@core_hotunplug@unbind-rebind:bat-lnl-2: PASS -> ABORTbat-dg2-
> oem2: PASS -> ABORTbat-adlp-vm: PASS -> ABORTbat-lnl-1: PASS -> ABORT
>  * igt@sriov_basic@enable-vfs-autoprobe-on:bat-bmg-2: PASS -> ABORT
> +1 other test abortbat-adlp-7: PASS -> ABORT +1 other test abort
>  * igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1:bat-bmg-1: PASS -
> > ABORT +1 other test abortbat-atsm-2: PASS -> ABORT +1 other test

I'm not sure what's going on here exactly (speaking for all of the
above). I ran each of these on a PTL at least and they all look ok. I'm
working on checking this out on at least a BMG.

Thanks,
Stuart

> abort
> Known issuesHere are the changes found in xe-pw-155352v4_BAT that
> come from known issues:
> IGT changesPossible fixes * igt@kms_flip@basic-plain-flip@a-edp1:bat-
> adlp-7: DMESG-WARN (Intel XE#4543) -> PASS +1 other test pass
> Build changes * Linux: xe-3920-
> b172f4e7a8beb0bae2feda7f7edfb49e661fd3be -> xe-pw-155352v4
> IGT_8582: 8582
>  xe-3920-b172f4e7a8beb0bae2feda7f7edfb49e661fd3be:
> b172f4e7a8beb0bae2feda7f7edfb49e661fd3be
>  xe-pw-155352v4: 155352v4


  reply	other threads:[~2025-10-14 21:15 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-10-14 18:09 [PATCH 0/6] Fix a couple of wedge corner-case memory leaks Stuart Summers
2025-10-14 18:09 ` [PATCH 1/6] drm/xe: Add additional trace points for LRCs Stuart Summers
2025-10-14 18:09 ` [PATCH 2/6] drm/xe: Add a trace point for VM close Stuart Summers
2025-10-14 18:09 ` [PATCH 3/6] drm/xe: Add the BO pointer info to the BO trace Stuart Summers
2025-10-14 18:09 ` [PATCH 4/6] drm/xe: Add new exec queue trace points Stuart Summers
2025-10-14 18:09 ` [PATCH 5/6] drm/xe: Correct migration VM teardown order Stuart Summers
2025-10-15  0:59   ` Matthew Brost
2025-10-15 17:55     ` Summers, Stuart
2025-10-14 18:09 ` [PATCH 6/6] drm/xe: Clean up GuC software state after a wedge Stuart Summers
2025-10-15 19:45   ` Summers, Stuart
2025-10-16  3:42     ` Matthew Brost
2025-10-16 17:50       ` Summers, Stuart
2025-10-16 22:10         ` Matthew Brost
2025-10-17 14:48           ` Summers, Stuart
2025-10-14 18:15 ` ✗ CI.checkpatch: warning for Fix a couple of wedge corner-case memory leaks (rev4) Patchwork
2025-10-14 18:16 ` ✓ CI.KUnit: success " Patchwork
2025-10-14 19:13 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-10-14 21:14   ` Summers, Stuart [this message]
2025-10-15  5:18 ` ✗ 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=a1b9e5b9f6402be37eb8593450f5731282b69047.camel@intel.com \
    --to=stuart.summers@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