From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for Don't allocate managed BO for each policy change (rev2)
Date: Thu, 15 May 2025 08:29:28 +0200 [thread overview]
Message-ID: <beb8f231-de29-413b-b0e2-48c030fc0c8c@intel.com> (raw)
In-Reply-To: <174727989854.82414.17399421351066129824@c664b1dc75d1>
On 15.05.2025 05:31, Patchwork wrote:
> == Series Details ==
>
> Series: Don't allocate managed BO for each policy change (rev2)
> URL : https://patchwork.freedesktop.org/series/148913/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-3088-dd6a856541dd90fa4ef755783898fcfbea3b9961_FULL -> xe-pw-148913v2_FULL
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-148913v2_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-148913v2_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-148913v2_FULL:
>
> ### IGT changes ###
>
> #### Possible regressions ####
all KMS, all unrelated to this series
>
> * igt@kms_flip@blocking-wf_vblank@c-hdmi-a6:
> - shard-dg2-set2: [PASS][1] -> [FAIL][2]
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-3088-dd6a856541dd90fa4ef755783898fcfbea3b9961/shard-dg2-433/igt@kms_flip@blocking-wf_vblank@c-hdmi-a6.html
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-148913v2/shard-dg2-435/igt@kms_flip@blocking-wf_vblank@c-hdmi-a6.html
Expected frametime: 16667us; measured 16427.2us +- 7.724us accuracy 0.14%
vblank interval differs from modeline! expected 16666.7us, measured
16427us +- 7.724us, difference 239.4us (31.0 sigma)
>
> * igt@kms_setmode@invalid-clone-single-crtc-stealing@pipe-a-hdmi-a-6-dp-4:
> - shard-dg2-set2: NOTRUN -> [ABORT][3]
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-148913v2/shard-dg2-463/igt@kms_setmode@invalid-clone-single-crtc-stealing@pipe-a-hdmi-a-6-dp-4.html
<4> [221.990004] xe 0000:03:00.0: [drm] vblank wait timed out on crtc 0
<4> [221.990043] WARNING: CPU: 5 PID: 4290 at
drivers/gpu/drm/drm_vblank.c:1307 drm_wait_one_vblank+0x185/0x220
>
>
> #### Warnings ####
>
> * igt@kms_setmode@invalid-clone-single-crtc-stealing:
> - shard-dg2-set2: [SKIP][4] ([Intel XE#4208] / [i915#2575]) -> [ABORT][5]
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-3088-dd6a856541dd90fa4ef755783898fcfbea3b9961/shard-dg2-464/igt@kms_setmode@invalid-clone-single-crtc-stealing.html
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-148913v2/shard-dg2-463/igt@kms_setmode@invalid-clone-single-crtc-stealing.html
<4> [221.990004] xe 0000:03:00.0: [drm] vblank wait timed out on crtc 0
<4> [221.990043] WARNING: CPU: 5 PID: 4290 at
drivers/gpu/drm/drm_vblank.c:1307 drm_wait_one_vblank+0x185/0x220
next prev parent reply other threads:[~2025-05-15 6:29 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-12 22:00 [PATCH 0/2] Don't allocate managed BO for each policy change Michal Wajdeczko
2025-05-12 22:00 ` [PATCH 1/2] drm/xe/guc: Unblock GuC buffer cache for all modes Michal Wajdeczko
2025-05-12 22:11 ` Matthew Brost
2025-05-13 20:57 ` Lucas De Marchi
2025-05-12 22:32 ` Daniele Ceraolo Spurio
2025-05-12 22:00 ` [PATCH 2/2] drm/xe/guc: Don't allocate managed BO for each policy change Michal Wajdeczko
2025-05-12 22:12 ` Matthew Brost
2025-05-12 22:15 ` ✓ CI.Patch_applied: success for " Patchwork
2025-05-12 22:15 ` ✓ CI.checkpatch: " Patchwork
2025-05-12 22:16 ` ✓ CI.KUnit: " Patchwork
2025-05-12 22:26 ` ✗ CI.Build: failure " Patchwork
2025-05-13 14:24 ` ✓ CI.Patch_applied: success " Patchwork
2025-05-13 14:24 ` ✓ CI.checkpatch: " Patchwork
2025-05-13 14:25 ` ✓ CI.KUnit: " Patchwork
2025-05-13 14:35 ` ✓ CI.Build: " Patchwork
2025-05-14 18:51 ` ✓ CI.Patch_applied: success for Don't allocate managed BO for each policy change (rev2) Patchwork
2025-05-14 18:51 ` ✓ CI.checkpatch: " Patchwork
2025-05-14 18:53 ` ✓ CI.KUnit: " Patchwork
2025-05-14 19:03 ` ✓ CI.Build: " Patchwork
2025-05-14 19:06 ` ✓ CI.Hooks: " Patchwork
2025-05-14 19:07 ` ✓ CI.checksparse: " Patchwork
2025-05-14 19:59 ` ✓ Xe.CI.BAT: " Patchwork
2025-05-15 3:31 ` ✗ Xe.CI.Full: failure " Patchwork
2025-05-15 6:29 ` Michal Wajdeczko [this message]
2025-05-27 0:49 ` ✗ CI.Patch_applied: " Patchwork
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=beb8f231-de29-413b-b0e2-48c030fc0c8c@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.