Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: Matt Roper <matthew.d.roper@intel.com>, <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.BAT: failure for series starting with [v2,1/2] drm/xe: Track pre-production workaround support (rev2)
Date: Thu, 20 Nov 2025 22:59:46 +0100	[thread overview]
Message-ID: <4c89c31e-54ca-45b9-a8ef-081048f2591a@intel.com> (raw)
In-Reply-To: <20251120211828.GI4063759@mdroper-desk1.amr.corp.intel.com>



On 11/20/2025 10:18 PM, Matt Roper wrote:
> On Thu, Nov 20, 2025 at 09:14:40PM +0000, Patchwork wrote:
>> == Series Details ==
>>
>> Series: series starting with [v2,1/2] drm/xe: Track pre-production workaround support (rev2)
>> URL   : https://patchwork.freedesktop.org/series/157804/
>> State : failure
>>
>> == Summary ==
>>
>> CI Bug Log - changes from xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7_BAT -> xe-pw-157804v2_BAT
>> ====================================================
>>
>> Summary
>> -------
>>
>>   **FAILURE**
>>
>>   Serious unknown changes coming with xe-pw-157804v2_BAT absolutely need to be
>>   verified manually.
>>   
>>   If you think the reported changes have nothing to do with the changes
>>   introduced in xe-pw-157804v2_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 (13 -> 13)
>> ------------------------------
>>
>>   No changes in participating hosts
>>
>> Possible new issues
>> -------------------
>>
>>   Here are the unknown changes that may have been introduced in xe-pw-157804v2_BAT:
>>
>> ### IGT changes ###
>>
>> #### Possible regressions ####
>>
>>   * igt@sriov_basic@enable-vfs-autoprobe-on:
>>     - bat-ptl-1:          [PASS][1] -> [ABORT][2] +1 other test abort
>>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-ptl-1/igt@sriov_basic@enable-vfs-autoprobe-on.html
>>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-ptl-1/igt@sriov_basic@enable-vfs-autoprobe-on.html
> 
> Looks like I'll need to add a !sriov check in the next version as well
> since VFs don't have access to this register.
> 
> Michal, we don't have any other means of determining production vs
> pre-production status on a VF, right?

we could try to add 0x9120 register to the runtime_regs, but that would be unofficial hack

so I guess it's easier to assume that VFs will be enabled only on production parts

> 
> 
> Matt
> 
>>     - bat-adlp-7:         [PASS][3] -> [ABORT][4] +1 other test abort
>>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-adlp-7/igt@sriov_basic@enable-vfs-autoprobe-on.html
>>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-adlp-7/igt@sriov_basic@enable-vfs-autoprobe-on.html
>>
>>   * igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1:
>>     - bat-ptl-2:          [PASS][5] -> [ABORT][6] +1 other test abort
>>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-ptl-2/igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1.html
>>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-ptl-2/igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1.html
>>     - bat-atsm-2:         [PASS][7] -> [ABORT][8] +1 other test abort
>>    [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-atsm-2/igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1.html
>>    [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-atsm-2/igt@sriov_basic@enable-vfs-autoprobe-on@numvfs-1.html
>>
>>   * igt@xe_module_load@load:
>>     - bat-adlp-vm:        [PASS][9] -> [ABORT][10]
>>    [9]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-adlp-vm/igt@xe_module_load@load.html
>>    [10]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-adlp-vm/igt@xe_module_load@load.html
>>     - bat-ptl-vm:         [PASS][11] -> [ABORT][12]
>>    [11]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-ptl-vm/igt@xe_module_load@load.html
>>    [12]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-ptl-vm/igt@xe_module_load@load.html
>>
>>   
>> Known issues
>> ------------
>>
>>   Here are the changes found in xe-pw-157804v2_BAT that come from known issues:
>>
>> ### IGT changes ###
>>
>> #### Possible fixes ####
>>
>>   * igt@xe_waitfence@reltime:
>>     - bat-dg2-oem2:       [FAIL][13] ([Intel XE#6520]) -> [PASS][14]
>>    [13]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7/bat-dg2-oem2/igt@xe_waitfence@reltime.html
>>    [14]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/bat-dg2-oem2/igt@xe_waitfence@reltime.html
>>
>>   
>>   [Intel XE#6520]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6520
>>
>>
>> Build changes
>> -------------
>>
>>   * Linux: xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7 -> xe-pw-157804v2
>>
>>   IGT_8636: 254cd102396ff95d61f2ebe49fc09128878bf483 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
>>   xe-4135-3d718db04a365cc44a3bc81ffa4db7bbd2e645d7: 3d718db04a365cc44a3bc81ffa4db7bbd2e645d7
>>   xe-pw-157804v2: 157804v2
>>
>> == Logs ==
>>
>> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-157804v2/index.html
> 


  reply	other threads:[~2025-11-20 22:00 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-19 22:05 [PATCH 1/2] drm/xe: Track pre-production workaround support Matt Roper
2025-11-19 22:05 ` [PATCH 2/2] drm/xe/lnl: Drop " Matt Roper
2025-11-20  1:46 ` ✓ CI.KUnit: success for series starting with [1/2] drm/xe: Track " Patchwork
2025-11-20  2:36 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-11-20  7:45 ` ✗ Xe.CI.Full: " Patchwork
2025-11-20 16:21 ` [PATCH v2 1/2] " Matt Roper
2025-11-20 17:00 ` [PATCH " Jani Nikula
2025-11-20 18:07 ` Lucas De Marchi
2025-11-20 18:35   ` Matt Roper
2025-11-20 19:13     ` Lucas De Marchi
2025-11-20 20:31 ` ✓ CI.KUnit: success for series starting with [v2,1/2] drm/xe: Track pre-production workaround support (rev2) Patchwork
2025-11-20 21:14 ` ✗ Xe.CI.BAT: failure " Patchwork
2025-11-20 21:18   ` Matt Roper
2025-11-20 21:59     ` Michal Wajdeczko [this message]
2025-11-20 22:05       ` Matt Roper
2025-11-21  2:13 ` ✗ 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=4c89c31e-54ca-45b9-a8ef-081048f2591a@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=matthew.d.roper@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