Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/pf: Allow to lockdown the PF using custom guard (rev5)
Date: Wed, 12 Nov 2025 18:07:19 +0100	[thread overview]
Message-ID: <f009dd3e-7736-4357-b485-29699b2b27e1@intel.com> (raw)
In-Reply-To: <176271235200.33584.356440255027254374@10055242dc62>



On 11/9/2025 7:19 PM, Patchwork wrote:
> *Patch Details*
> *Series:*	drm/xe/pf: Allow to lockdown the PF using custom guard (rev5)
> *URL:*	https://patchwork.freedesktop.org/series/156795/ <https://patchwork.freedesktop.org/series/156795/>
> *State:*	failure
> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156795v5/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156795v5/index.html>
> 
> 
>   CI Bug Log - changes from xe-4075-ed09c460ec22d447d1729ebbf913b7229e1f48ea_FULL -> xe-pw-156795v5_FULL
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with xe-pw-156795v5_FULL absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-156795v5_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-156795v5_FULL:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions
> 
>   *
> 
>     igt@kms_cursor_legacy@torture-move@all-pipes:
> 
>       o shard-dg2-set2: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4075-ed09c460ec22d447d1729ebbf913b7229e1f48ea/shard-dg2-435/igt@kms_cursor_legacy@torture-move@all-pipes.html> -> DMESG-WARN <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156795v5/shard-dg2-463/igt@kms_cursor_legacy@torture-move@all-pipes.html>

unrelated

<4> [109.367857] xe 0000:00:02.0: [drm] Tile0: GT0: GuC load: excessive init time: 946ms! [status = 0x8002F0EC]
<4> [109.367864] xe 0000:00:02.0: [drm] Tile0: GT0: GuC load: excessive init time: [freq = 1300MHz (req = 1500MHz), before = 1300MHz, perf_limit_reasons = 0x00000100]


>   *
> 
>     igt@xe_pmu@engine-activity-accuracy-50@engine-drm_xe_engine_class_video_decode0:
> 
>       o shard-lnl: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-4075-ed09c460ec22d447d1729ebbf913b7229e1f48ea/shard-lnl-1/igt@xe_pmu@engine-activity-accuracy-50@engine-drm_xe_engine_class_video_decode0.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-156795v5/shard-lnl-8/igt@xe_pmu@engine-activity-accuracy-50@engine-drm_xe_engine_class_video_decode0.html>

unrelated (non-SRIOV platform)

(xe_pmu:3651) CRITICAL: Test assertion failure function accuracy, file ../tests/intel/xe_pmu.c:625:
(xe_pmu:3651) CRITICAL: Failed assertion: (double)(100.0 * engine_activity) <= ((double)(100.0 * expected) + (3)) && (double)(100.0 * engine_activity) >= ((double)(100.0 * expected) - (3))
(xe_pmu:3651) CRITICAL: 45.599705 not within +3.000000/-3.000000 of 48.717342! ('100.0 * engine_activity' vs '100.0 * expected')
Dynamic subtest engine-DRM_XE_ENGINE_CLASS_VIDEO_DECODE0 failed.




  reply	other threads:[~2025-11-12 17:07 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-11-09 16:24 [CI v5] drm/xe/pf: Allow to lockdown the PF using custom guard Michal Wajdeczko
2025-11-09 16:31 ` ✗ CI.checkpatch: warning for drm/xe/pf: Allow to lockdown the PF using custom guard (rev5) Patchwork
2025-11-09 16:32 ` ✓ CI.KUnit: success " Patchwork
2025-11-09 17:10 ` ✓ Xe.CI.BAT: " Patchwork
2025-11-09 18:19 ` ✗ Xe.CI.Full: failure " Patchwork
2025-11-12 17:07   ` Michal Wajdeczko [this message]
2025-11-12 18:08 ` [CI v5] drm/xe/pf: Allow to lockdown the PF using custom guard Michal Wajdeczko

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=f009dd3e-7736-4357-b485-29699b2b27e1@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