From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for RFC: Add dedicated printk macros for tile and device (rev3)
Date: Fri, 12 Sep 2025 12:18:24 +0200 [thread overview]
Message-ID: <441b7d2d-7b45-425b-b1e2-df41c9016acd@intel.com> (raw)
In-Reply-To: <175767112475.328926.9683820517827903192@1538d3639d33>
On 9/12/2025 11:58 AM, Patchwork wrote:
> *Patch Details*
> *Series:* RFC: Add dedicated printk macros for tile and device (rev3)
> *URL:* https://patchwork.freedesktop.org/series/153985/ <https://patchwork.freedesktop.org/series/153985/>
> *State:* failure
> *Details:* https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-153985v3/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-153985v3/index.html>
>
>
> CI Bug Log - changes from xe-3732-6d209e86cb298782b5afa278b7b0fc73cb433b4c_FULL -> xe-pw-153985v3_FULL
>
>
> Summary
>
> *FAILURE*
>
> Serious unknown changes coming with xe-pw-153985v3_FULL absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-153985v3_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-153985v3_FULL:
>
>
> IGT changes
>
>
> Possible regressions
>
> * igt@xe_exec_threads@threads-cm-shared-vm-basic:
> o shard-adlp: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3732-6d209e86cb298782b5afa278b7b0fc73cb433b4c/shard-adlp-2/igt@xe_exec_threads@threads-cm-shared-vm-basic.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-153985v3/shard-adlp-1/igt@xe_exec_threads@threads-cm-shared-vm-basic.html>
>
unrelated:
(xe_exec_threads:3160) [thread:3166] xe/xe_ioctl-CRITICAL: Test assertion failure function xe_wait_ufence, file ../lib/xe/xe_ioctl.c:676:
(xe_exec_threads:3160) [thread:3166] xe/xe_ioctl-CRITICAL: Failed assertion: __xe_wait_ufence(fd, addr, value, exec_queue, &timeout) == 0
(xe_exec_threads:3160) [thread:3166] xe/xe_ioctl-CRITICAL: Last errno: 62, Timer expired
(xe_exec_threads:3160) [thread:3166] xe/xe_ioctl-CRITICAL: error: -62 != 0
and new messages look correct:
xe 0000:00:02.0: [drm:xe_guc_exec_queue_memory_cat_error_handler [xe]] Tile0: GT0: Engine memory CAT error: class=vcs, logical_mask: 0x2, guc_id=40
xe 0000:00:02.0: [drm] Tile0: GT0: Engine reset: engine_class=vcs, logical_mask: 0x1, guc_id=80
prev parent reply other threads:[~2025-09-12 10:18 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 16:59 [PATCH v2 0/5] RFC: Add dedicated printk macros for tile and device Michal Wajdeczko
2025-09-09 16:59 ` [PATCH v2 1/5] drm/xe: Keep xe_gt_err() macro definitions together Michal Wajdeczko
2025-09-09 16:59 ` [PATCH v2 2/5] drm/xe: Drop "gt_" prefix from xe_gt_WARN() macros Michal Wajdeczko
2025-09-09 16:59 ` [PATCH v2 3/5] drm/xe: Prepare format for GT-oriented messages in one place Michal Wajdeczko
2025-09-10 21:28 ` Rodrigo Vivi
2025-09-11 3:49 ` Lucas De Marchi
2025-09-09 16:59 ` [PATCH v2 4/5] drm/xe: Add dedicated printk macros for tile and device Michal Wajdeczko
2025-09-10 21:28 ` Rodrigo Vivi
2025-09-11 3:51 ` Lucas De Marchi
2025-09-09 16:59 ` [PATCH v2 5/5] drm/xe: Use tile-oriented messages in GGTT code Michal Wajdeczko
2025-09-09 17:52 ` ✗ CI.checkpatch: warning for RFC: Add dedicated printk macros for tile and device (rev2) Patchwork
2025-09-09 17:53 ` ✓ CI.KUnit: success " Patchwork
2025-09-12 7:25 ` ✗ CI.checkpatch: warning for RFC: Add dedicated printk macros for tile and device (rev3) Patchwork
2025-09-12 7:26 ` ✓ CI.KUnit: success " Patchwork
2025-09-12 8:08 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-12 9:58 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-12 10:18 ` 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=441b7d2d-7b45-425b-b1e2-df41c9016acd@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.