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 GuC CT devm actions improvements
Date: Tue, 9 Sep 2025 11:44:39 +0200	[thread overview]
Message-ID: <8487c18e-10a3-45d2-ac63-77e61803f10b@intel.com> (raw)
In-Reply-To: <175738646299.315157.14732138584916909682@1538d3639d33>



On 9/9/2025 4:54 AM, Patchwork wrote:
> *Patch Details*
> *Series:*	GuC CT devm actions improvements
> *URL:*	https://patchwork.freedesktop.org/series/154180/ <https://patchwork.freedesktop.org/series/154180/>
> *State:*	failure
> *Details:*	https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154180v1/index.html <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154180v1/index.html>
> 
> 
>   CI Bug Log - changes from xe-3703-6da3b81612a8f96c0b70981f173381ca05f80ce0_FULL -> xe-pw-154180v1_FULL
> 
> 
>     Summary
> 
> *FAILURE*
> 
> Serious unknown changes coming with xe-pw-154180v1_FULL absolutely need to be
> verified manually.
> 
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-154180v1_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-154180v1_FULL:
> 
> 
>       IGT changes
> 
> 
>         Possible regressions
> 
>   * igt@xe_exec_threads@threads-cm-fd-rebind:
>       o shard-bmg: PASS <https://intel-gfx-ci.01.org/tree/intel-xe/xe-3703-6da3b81612a8f96c0b70981f173381ca05f80ce0/shard-bmg-6/igt@xe_exec_threads@threads-cm-fd-rebind.html> -> FAIL <https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-154180v1/shard-bmg-3/igt@xe_exec_threads@threads-cm-fd-rebind.html>

unrelated, series was about GuC CT initialization, while failure is due to engine CAT error

<7> [402.031369] xe 0000:03:00.0: [drm:pf_queue_work_func [xe]] GT1: Fault response: Unsuccessful -EINVAL
<7> [402.031751] xe 0000:03:00.0: [drm:xe_guc_exec_queue_memory_cat_error_handler [xe]] GT1: Engine memory CAT error [18]: class=vecs, logical_mask: 0x1, guc_id=63
<5> [402.032492] xe 0000:03:00.0: [drm] GT1: log buffer overflow
<7> [402.569719] xe 0000:03:00.0: [drm:xe_guc_capture_process [xe]] GT1: Capture extraction failed:-5


      reply	other threads:[~2025-09-09  9:44 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-08 10:20 [PATCH 0/2] GuC CT devm actions improvements Michal Wajdeczko
2025-09-08 10:20 ` [PATCH 1/2] drm/xe/guc: Always add CT disable action during second init step Michal Wajdeczko
2025-09-08 11:50   ` K V P, Satyanarayana
2025-09-08 10:20 ` [PATCH 2/2] drm/xe/guc: Don't invoke disable_ct action during replacement Michal Wajdeczko
2025-09-08 10:57   ` K V P, Satyanarayana
2025-09-08 22:05 ` ✓ CI.KUnit: success for GuC CT devm actions improvements Patchwork
2025-09-08 22:43 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-09  2:54 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-09  9:44   ` 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=8487c18e-10a3-45d2-ac63-77e61803f10b@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