From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for Small improvements around VF CCS
Date: Fri, 5 Sep 2025 14:34:51 +0200 [thread overview]
Message-ID: <d301379e-ccfb-4240-b131-e95f9fc99657@intel.com> (raw)
In-Reply-To: <175707334761.307021.5869805195968242012@1538d3639d33>
On 9/5/2025 1:55 PM, Patchwork wrote:
> *Patch Details*
> *Series:* Small improvements around VF CCS
> *URL:* https://patchwork.freedesktop.org/series/154054/ <https://patchwork.freedesktop.org/series/154054/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154054v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154054v1/index.html>
>
>
> CI Bug Log - changes from xe-3679-13f87d5402106b321a373222c64c5a56a05aa3b6_FULL -> xe-pw-154054v1_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-154054v1_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-154054v1_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-154054v1_FULL:
>
>
> IGT changes
>
>
> Possible regressions
unrelated
>
> * igt@xe_exec_threads@threads-cm-fd-rebind:
> o shard-adlp: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3679-13f87d5402106b321a373222c64c5a56a05aa3b6/shard-adlp-9/igt@xe_exec_threads@threads-cm-fd-rebind.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154054v1/shard-adlp-1/igt@xe_exec_threads@threads-cm-fd-rebind.html> +1 other test fail
this was not a VF run
(xe_exec_threads:4450) [thread:4454] xe/xe_ioctl-CRITICAL: Failed assertion: __xe_wait_ufence(fd, addr, value, exec_queue, &timeout) == 0
(xe_exec_threads:4450) [thread:4454] xe/xe_ioctl-CRITICAL: Last errno: 62, Timer expired
(xe_exec_threads:4450) [thread:4454] xe/xe_ioctl-CRITICAL: error: -62 != 0
(xe_exec_threads:4450) igt_thread-CRITICAL: Failure in a thread!
prev parent reply other threads:[~2025-09-05 12:35 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-04 19:29 [PATCH 0/5] Small improvements around VF CCS Michal Wajdeczko
2025-09-04 19:29 ` [PATCH 1/5] drm/xe/guc: Rename xe_guc_register_exec_queue Michal Wajdeczko
2025-09-05 7:05 ` K V P, Satyanarayana
2025-09-04 19:29 ` [PATCH 2/5] drm/xe/guc: Use proper flag definitions when registering context Michal Wajdeczko
2025-09-04 19:36 ` Matthew Brost
2025-09-04 19:29 ` [PATCH 3/5] drm/xe/vf: Drop IS_VF_CCS_INIT_NEEDED macro Michal Wajdeczko
2025-09-05 3:27 ` Matthew Brost
2025-09-05 7:18 ` K V P, Satyanarayana
2025-09-04 19:29 ` [PATCH 4/5] drm/xe/vf: Use single check when calling VF CCS functions Michal Wajdeczko
2025-09-05 7:40 ` K V P, Satyanarayana
2025-09-04 19:29 ` [PATCH 5/5] drm/xe/bo: Add xe_bo_has_valid_ccs_bb helper Michal Wajdeczko
2025-09-04 20:31 ` Matthew Brost
2025-09-05 7:42 ` K V P, Satyanarayana
2025-09-04 19:36 ` ✓ CI.KUnit: success for Small improvements around VF CCS Patchwork
2025-09-04 20:19 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-05 11:55 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-05 12:34 ` 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=d301379e-ccfb-4240-b131-e95f9fc99657@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.