From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe/pf: Fix VF's scheduling priority reporting
Date: Thu, 16 Apr 2026 23:24:59 +0200 [thread overview]
Message-ID: <0d1f835a-e7a2-4233-a20c-5f145624bd6b@intel.com> (raw)
In-Reply-To: <177635380524.469471.45147512968706428@a3b018990fe9>
On 4/16/2026 5:36 PM, Patchwork wrote:
> *Patch Details*
> *Series:* drm/xe/pf: Fix VF's scheduling priority reporting
> *URL:* https://patchwork.freedesktop.org/series/164999/ <https://patchwork.freedesktop.org/series/164999/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164999v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164999v1/index.html>
>
>
> CI Bug Log - changes from xe-4913-207a25698a481a39132b52060d7bb294384876ac_FULL -> xe-pw-164999v1_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-164999v1_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-164999v1_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 (2 -> 2)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in xe-pw-164999v1_FULL:
>
>
> IGT changes
>
>
> Possible regressions
all unrelated
>
> *
>
> igt@kms_concurrent@multi-plane-atomic-lowres@pipe-d-dp-2:
>
> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4913-207a25698a481a39132b52060d7bb294384876ac/shard-bmg-9/igt@kms_concurrent@multi-plane-atomic-lowres@pipe-d-dp-2.html> -> SKIP <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164999v1/shard-bmg-6/igt@kms_concurrent@multi-plane-atomic-lowres@pipe-d-dp-2.html> +3 other tests skip
Test requirement: !(mode_default->hdisplay < 1024)
No suitable resolution was found
> *
>
> igt@kms_plane@pixel-format-linear-modifier-source-clamping:
>
> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4913-207a25698a481a39132b52060d7bb294384876ac/shard-bmg-9/igt@kms_plane@pixel-format-linear-modifier-source-clamping.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164999v1/shard-bmg-6/igt@kms_plane@pixel-format-linear-modifier-source-clamping.html> +6 other tests dmesg-warn
<4> [462.224006] drm_dp_i2c_do_msg: 13 callbacks suppressed
> *
>
> igt@kms_vblank@wait-forked@pipe-a-dp-2:
>
> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4913-207a25698a481a39132b52060d7bb294384876ac/shard-bmg-9/igt@kms_vblank@wait-forked@pipe-a-dp-2.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-164999v1/shard-bmg-6/igt@kms_vblank@wait-forked@pipe-a-dp-2.html> +2 other tests fail
kms_vblank:6468) CRITICAL: Test assertion failure function vblank_wait, file ../tests/kms_vblank.c:379:
(kms_vblank:6468) CRITICAL: Failed assertion: wait_vblank(fd, &vbl) == 0
(kms_vblank:6474) CRITICAL: Last errno: 22, Invalid argument
(kms_vblank:6474) CRITICAL: error: -22 != 0
next prev parent reply other threads:[~2026-04-16 21:25 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-16 13:18 [PATCH] drm/xe/pf: Fix VF's scheduling priority reporting Michal Wajdeczko
2026-04-16 13:24 ` ✗ CI.checkpatch: warning for " Patchwork
2026-04-16 13:26 ` ✓ CI.KUnit: success " Patchwork
2026-04-16 14:32 ` ✓ Xe.CI.BAT: " Patchwork
2026-04-16 15:36 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-04-16 21:24 ` Michal Wajdeczko [this message]
2026-04-16 16:06 ` [PATCH] " 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=0d1f835a-e7a2-4233-a20c-5f145624bd6b@intel.com \
--to=michal.wajdeczko@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