From: "Piotr Piórkowski" <piotr.piorkowski@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.BAT: failure for drm/xe: Force EXEC_QUEUE_FLAG_KERNEL for kernel internal VMs
Date: Fri, 13 Feb 2026 10:07:10 +0100 [thread overview]
Message-ID: <20260213090710.e4fpjfxb2fpqge2v@intel.com> (raw)
In-Reply-To: <177083287401.246446.6708996765005495710@a3b018990fe9>
Patchwork <patchwork@emeril.freedesktop.org> wrote on śro [2026-lut-11 18:01:14 +0000]:
> == Series Details ==
>
> Series: drm/xe: Force EXEC_QUEUE_FLAG_KERNEL for kernel internal VMs
> URL : https://patchwork.freedesktop.org/series/161506/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-4544-2938ce73d01357a5816ed7dbd041154b58635a37_BAT -> xe-pw-161506v1_BAT
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-161506v1_BAT absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-161506v1_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 (9 -> 12)
> ------------------------------
>
> Additional (3): bat-wcl-1 bat-wcl-2 bat-bmg-3
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in xe-pw-161506v1_BAT:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@kms_pipe_crc_basic@hang-read-crc:
> - bat-wcl-2: NOTRUN -> [SKIP][1] +43 other tests skip
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/bat-wcl-2/igt@kms_pipe_crc_basic@hang-read-crc.html
Normal skip:
Using IGT_SRANDOM=1770831758 for randomisation
Opened device: /dev/dri/card0
No valid crtc/connector combinations found.
Subtest hang-read-crc: SKIP (0.000s)
>
> * igt@xe_live_ktest@xe_migrate@xe_validate_ccs_kunit:
> - bat-wcl-1: NOTRUN -> [SKIP][2] +20 other tests skip
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/bat-wcl-1/igt@xe_live_ktest@xe_migrate@xe_validate_ccs_kunit.html
Also expected SKIP:
<6> [461.512757] [IGT] xe_live_ktest: starting dynamic subtest xe_validate_ccs_kunit
<6> [461.578672] KTAP version 1
<6> [461.578686] 1..1
<6> [461.579253] KTAP version 1
<6> [461.579260] # Subtest: xe_migrate
<6> [461.579263] # module: xe
<6> [461.579299] 1..1
<6> [461.579310] KTAP version 1
<6> [461.579331] # Subtest: xe_validate_ccs_kunit
<6> [461.579716] # xe_validate_ccs_kunit: running on PANTHERLAKE device
<6> [461.580069] ok 1 0000:00:02.0 # SKIP non-xe2 discrete device
<6> [461.580119] ok 1 xe_validate_ccs_kunit # SKIP
<6> [461.580149] ok 1 xe_migrate # SKIP
Thanks
Piotr
>
>
> Known issues
> ------------
>
> Here are the changes found in xe-pw-161506v1_BAT that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@kms_psr@psr-sprite-plane-onoff:
> - bat-wcl-2: NOTRUN -> [SKIP][3] ([Intel XE#1406]) +2 other tests skip
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/bat-wcl-2/igt@kms_psr@psr-sprite-plane-onoff.html
>
> * igt@xe_peer2peer@read@read-gpua-vram01-gpub-system-p2p:
> - bat-bmg-3: NOTRUN -> [SKIP][4] ([Intel XE#6566]) +3 other tests skip
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/bat-bmg-3/igt@xe_peer2peer@read@read-gpua-vram01-gpub-system-p2p.html
>
> * igt@xe_waitfence@reltime:
> - bat-dg2-oem2: [PASS][5] -> [FAIL][6] ([Intel XE#6520])
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4544-2938ce73d01357a5816ed7dbd041154b58635a37/bat-dg2-oem2/igt@xe_waitfence@reltime.html
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/bat-dg2-oem2/igt@xe_waitfence@reltime.html
>
>
> #### Possible fixes ####
>
> * igt@xe_waitfence@reltime:
> - bat-ptl-1: [FAIL][7] -> [PASS][8]
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4544-2938ce73d01357a5816ed7dbd041154b58635a37/bat-ptl-1/igt@xe_waitfence@reltime.html
> [8]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/bat-ptl-1/igt@xe_waitfence@reltime.html
>
>
> [Intel XE#1406]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/1406
> [Intel XE#6520]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6520
> [Intel XE#6566]: https://gitlab.freedesktop.org/drm/xe/kernel/issues/6566
>
>
> Build changes
> -------------
>
> * IGT: IGT_8749 -> IGT_8751
> * Linux: xe-4544-2938ce73d01357a5816ed7dbd041154b58635a37 -> xe-pw-161506v1
>
> IGT_8749: 195f101f25a7984686f36f340aa88d44a1716ec6 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> IGT_8751: af788251f1ef729d17c802aec2c4547b52059e58 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> xe-4544-2938ce73d01357a5816ed7dbd041154b58635a37: 2938ce73d01357a5816ed7dbd041154b58635a37
> xe-pw-161506v1: 161506v1
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161506v1/index.html
--
next prev parent reply other threads:[~2026-02-13 9:07 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-11 17:14 [PATCH v1] drm/xe: Force EXEC_QUEUE_FLAG_KERNEL for kernel internal VMs Piórkowski, Piotr
2026-02-11 17:22 ` ✓ CI.KUnit: success for " Patchwork
2026-02-11 17:44 ` [PATCH v1] " Matthew Brost
2026-02-12 17:38 ` Matthew Brost
2026-02-11 18:01 ` ✗ Xe.CI.BAT: failure for " Patchwork
2026-02-13 9:07 ` Piotr Piórkowski [this message]
2026-02-13 2:36 ` ✗ Xe.CI.FULL: " Patchwork
2026-02-13 9:10 ` Piotr Piórkowski
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=20260213090710.e4fpjfxb2fpqge2v@intel.com \
--to=piotr.piorkowski@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