From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/pf: Improve reading VF config blob from debugfs
Date: Mon, 6 Oct 2025 19:36:16 +0200 [thread overview]
Message-ID: <0225b5af-481b-47ee-bd68-1e88f0b4569a@intel.com> (raw)
In-Reply-To: <175960430071.5798.10186927488506032335@6aec98b87f92>
On 10/4/2025 8:58 PM, Patchwork wrote:
> *Patch Details*
> *Series:* drm/xe/pf: Improve reading VF config blob from debugfs
> *URL:* https://patchwork.freedesktop.org/series/155416/ <https://patchwork.freedesktop.org/series/155416/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-155416v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-155416v1/index.html>
>
>
> CI Bug Log - changes from xe-3867-0ce21448d1c984adf76d9dbfb3ad626ef8f33e47_FULL -> xe-pw-155416v1_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-155416v1_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-155416v1_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 (4 -> 4)
>
> No changes in participating hosts
>
>
> Possible new issues
>
> Here are the unknown changes that may have been introduced in xe-pw-155416v1_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@kms_pm_rpm@legacy-planes:
>
> o shard-dg2-set2: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3867-0ce21448d1c984adf76d9dbfb3ad626ef8f33e47/shard-dg2-435/igt@kms_pm_rpm@legacy-planes.html> -> SKIP <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-155416v1/shard-dg2-435/igt@kms_pm_rpm@legacy-planes.html> +15 other tests skip
> *
>
> igt@kms_vblank@ts-continuation-suspend@pipe-c-edp-1:
>
> o shard-lnl: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3867-0ce21448d1c984adf76d9dbfb3ad626ef8f33e47/shard-lnl-4/igt@kms_vblank@ts-continuation-suspend@pipe-c-edp-1.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-155416v1/shard-lnl-1/igt@kms_vblank@ts-continuation-suspend@pipe-c-edp-1.html> +1 other test dmesg-warn
unrelated
<4> [251.875848] xe 0000:00:02.0: [drm] Tile0: GT1: GuC load: excessive init time: 542ms! [status = 0x8002F034]
<4> [251.875908] xe 0000:00:02.0: [drm] Tile0: GT1: GuC load: excessive init time: [freq = 100MHz (req = 800MHz), before = 100MHz, perf_limit_reasons = 0x9C009000]
next prev parent reply other threads:[~2025-10-06 17:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-04 16:20 [PATCH] drm/xe/pf: Improve reading VF config blob from debugfs Michal Wajdeczko
2025-10-04 17:11 ` ✓ CI.KUnit: success for " Patchwork
2025-10-04 17:46 ` ✓ Xe.CI.BAT: " Patchwork
2025-10-04 18:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-10-06 17:36 ` Michal Wajdeczko [this message]
2025-10-07 10:46 ` [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=0225b5af-481b-47ee-bd68-1e88f0b4569a@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