From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/debugfs: Avoid use of wrapper functions
Date: Tue, 30 Sep 2025 10:15:29 +0200 [thread overview]
Message-ID: <449c4fc1-0b6f-4f83-91e7-53ffd3c5626f@intel.com> (raw)
In-Reply-To: <175867966427.360509.16902292047990176768@1538d3639d33>
On 9/24/2025 4:07 AM, Patchwork wrote:
> *Patch Details*
> *Series:* drm/xe/debugfs: Avoid use of wrapper functions
> *URL:* https://patchwork.freedesktop.org/series/154927/ <https://patchwork.freedesktop.org/series/154927/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154927v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154927v1/index.html>
>
>
> CI Bug Log - changes from xe-3820-547682ff49fc0459e80b1dca71dcbfec7082b43b_FULL -> xe-pw-154927v1_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-154927v1_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-154927v1_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-154927v1_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> *
>
> igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic:
>
> o shard-dg2-set2: NOTRUN -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154927v1/shard-dg2-464/igt@kms_cursor_legacy@2x-long-cursor-vs-flip-atomic.html>
unrelated
(kms_cursor_legacy:6555) CRITICAL: Test assertion failure function two_screens_cursor_vs_flip, file ../tests/kms_cursor_legacy.c:1544:
(kms_cursor_legacy:6555) CRITICAL: Failed assertion: vbl.sequence <= vblank_start[child] + 5 * vrefresh[child] / 8
(kms_cursor_legacy:6555) CRITICAL: error: 437 > 428
> *
>
> igt@kms_pm_rpm@system-suspend-modeset:
>
> o shard-dg2-set2: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3820-547682ff49fc0459e80b1dca71dcbfec7082b43b/shard-dg2-466/igt@kms_pm_rpm@system-suspend-modeset.html> -> INCOMPLETE <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154927v1/shard-dg2-433/igt@kms_pm_rpm@system-suspend-modeset.html>
unrelated
runner: This test was killed due to exceeding disk usage limit. (Used 10532962 bytes, limit 10485760
> *
>
> igt@xe_fault_injection@probe-fail-guc-xe_guc_mmio_send_recv:
>
> o shard-dg2-set2: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3820-547682ff49fc0459e80b1dca71dcbfec7082b43b/shard-dg2-466/igt@xe_fault_injection@probe-fail-guc-xe_guc_mmio_send_recv.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154927v1/shard-dg2-433/igt@xe_fault_injection@probe-fail-guc-xe_guc_mmio_send_recv.html>
valid, but unrelated
<5> [279.319264] FAULT_INJECTION: forcing a failure.
name fail_function, interval 0, probability 100, space 1, times 98
<3> [279.319276] xe 0000:00:02.0: [drm] *ERROR* Tile0: GT0: Failed to enable GuC CT (-ENOMEM)
<5> [279.319900] FAULT_INJECTION: forcing a failure.
name fail_function, interval 0, probability 100, space 1, times 97
<3> [279.319922] xe 0000:00:02.0: [drm] *ERROR* Tile0: GT0: resume failed (-ENOMEM)
> *
>
> igt@xe_pm@s4-vm-bind-unbind-all:
>
> o shard-lnl: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3820-547682ff49fc0459e80b1dca71dcbfec7082b43b/shard-lnl-7/igt@xe_pm@s4-vm-bind-unbind-all.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154927v1/shard-lnl-8/igt@xe_pm@s4-vm-bind-unbind-all.html>
unrelated
<6> [250.985668] Restarting tasks: Starting
<6> [250.985994] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops xe_gsc_proxy_component_ops [xe])
<3> [250.994550] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_ipc_send_receive_internal(): IPC receive failed: type VPU_JSM_MSG_PWR_D0I3_ENTER, ret -110
<3> [250.995118] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_pm_runtime_suspend_cb(): Failed to prepare for d0i3: -110
<6> [250.995656] Restarting tasks: Done
<3> [250.998764] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_pm_runtime_suspend_cb(): Forcing cold boot due to previous errors
<6> [251.002059] PM: hibernation: hibernation exit
prev parent reply other threads:[~2025-09-30 8:15 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-23 21:16 [PATCH 0/5] drm/xe/debugfs: Avoid use of wrapper functions Michal Wajdeczko
2025-09-23 21:16 ` [PATCH 1/5] drm/xe/debugfs: Update xe_gt_topology_dump signature Michal Wajdeczko
2025-09-29 23:25 ` Rodrigo Vivi
2025-09-30 8:45 ` Jani Nikula
2025-09-30 10:17 ` Michal Wajdeczko
2025-09-30 11:43 ` Jani Nikula
2025-09-30 17:23 ` Raag Jadav
2025-09-30 17:46 ` Michal Wajdeczko
2025-10-01 15:35 ` Rodrigo Vivi
2025-09-23 21:16 ` [PATCH 2/5] drm/xe/debugfs: Update xe_wa_dump signature Michal Wajdeczko
2025-09-29 23:25 ` Rodrigo Vivi
2025-09-23 21:16 ` [PATCH 3/5] drm/xe/debugfs: Update xe_tuning_dump signature Michal Wajdeczko
2025-09-29 23:26 ` Rodrigo Vivi
2025-09-23 21:16 ` [PATCH 4/5] drm/xe/debugfs: Update xe_mocs_dump signature Michal Wajdeczko
2025-09-29 23:26 ` Rodrigo Vivi
2025-09-23 21:16 ` [PATCH 5/5] drm/xe/debugfs: Update xe_pat_dump signature Michal Wajdeczko
2025-09-29 23:27 ` Rodrigo Vivi
2025-09-23 21:23 ` ✓ CI.KUnit: success for drm/xe/debugfs: Avoid use of wrapper functions Patchwork
2025-09-23 22:22 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-24 2:07 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-30 8:15 ` Michal Wajdeczko [this message]
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=449c4fc1-0b6f-4f83-91e7-53ffd3c5626f@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