From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.FULL: failure for drm/xe: Don't expose display modparam if no display support
Date: Thu, 26 Feb 2026 13:33:37 +0100 [thread overview]
Message-ID: <334a019a-06dc-4979-9c68-78c9d4a007b7@intel.com> (raw)
In-Reply-To: <177128382240.256994.8303814739819454363@a3b018990fe9>
On 2/17/2026 12:17 AM, Patchwork wrote:
> *Patch Details*
> *Series:* drm/xe: Don't expose display modparam if no display support
> *URL:* https://patchwork.freedesktop.org/series/161666/ <https://patchwork.freedesktop.org/series/161666/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161666v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161666v1/index.html>
>
>
> CI Bug Log - changes from xe-4563-483cf2d774a08fdf83f0e4c7a6ab671a53656d3c_FULL -> xe-pw-161666v1_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-161666v1_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-161666v1_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-161666v1_FULL:
>
>
> IGT changes
>
>
> Possible regressions
unrelated
>
> *
>
> igt@kms_cursor_crc@cursor-suspend:
>
> o shard-bmg: NOTRUN -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161666v1/shard-bmg-3/igt@kms_cursor_crc@cursor-suspend.html> +1 other test incomplete
no errors in dmesg, looks like a CI glitch
Starting subtest: cursor-suspend
Starting dynamic subtest: pipe-A-DP-2
Dynamic subtest pipe-A-DP-2: SUCCESS (3.621s)
Starting dynamic subtest: pipe-D-DP-2
> *
>
> igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc:
>
> o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4563-483cf2d774a08fdf83f0e4c7a6ab671a53656d3c/shard-bmg-2/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc.html> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161666v1/shard-bmg-2/igt@kms_frontbuffer_tracking@fbc-rgb101010-draw-mmap-wc.html>
<3> [517.609394] xe 0000:03:00.0: [drm] *ERROR* Failed to bring PHY F to idle.
<4> [517.735648] xe 0000:03:00.0: [drm] energy read from pmt failed, ret -19
> *
>
> igt@xe_pmu@gt-frequency:
>
> o shard-lnl: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4563-483cf2d774a08fdf83f0e4c7a6ab671a53656d3c/shard-lnl-1/igt@xe_pmu@gt-frequency.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-161666v1/shard-lnl-7/igt@xe_pmu@gt-frequency.html> +1 other test fail
(xe_pmu:4993) CRITICAL: Test assertion failure function test_gt_frequency, file ../tests/intel/xe_pmu.c:961:
(xe_pmu:4993) CRITICAL: Failed assertion: current_min == orig_min || current_min == orig_rpe
Dynamic subtest gt0 failed.
next prev parent reply other threads:[~2026-02-26 12:33 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 18:32 [PATCH] drm/xe: Don't expose display modparam if no display support Michal Wajdeczko
2026-02-16 18:38 ` ✓ CI.KUnit: success for " Patchwork
2026-02-16 19:22 ` ✓ Xe.CI.BAT: " Patchwork
2026-02-16 23:17 ` ✗ Xe.CI.FULL: failure " Patchwork
2026-02-26 12:33 ` Michal Wajdeczko [this message]
2026-02-23 13:53 ` [PATCH] " Rodrigo Vivi
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=334a019a-06dc-4979-9c68-78c9d4a007b7@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