Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Julia Filipchuk <julia.filipchuk@intel.com>
To: <intel-xe@lists.freedesktop.org>
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/guc: Bump GUC version for NVL-S, CRI
Date: Thu, 8 Jan 2026 11:00:39 -0800	[thread overview]
Message-ID: <e83e6e11-2c7b-48d8-a9ce-988ae5a7dcba@intel.com> (raw)
In-Reply-To: <176774886068.130906.4232613977721226253@a3b018990fe9>

On 1/6/2026 5:21 PM, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/guc: Bump GUC version for NVL-S, CRI
> URL   : https://patchwork.freedesktop.org/series/159711/
> State : failure

> #### Possible regressions ####
> 
>   * igt@device_reset@unbind-reset-rebind:
>     - shard-bmg:          [PASS][1] -> [ABORT][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4336-3d6700a02638d446a4e8ad92a8212c3efef84ae0/shard-bmg-1/igt@device_reset@unbind-reset-rebind.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159711v1/shard-bmg-2/igt@device_reset@unbind-reset-rebind.html

Errors unrelated to this change. Look to be related to existing error.
> <4> [472.667507] ------------[ cut here ]------------
> <4> [472.667509] list_del corruption. next->prev should be ffff888116227400, but was 0000000000000000. (next=ffff8881bc8fee00)
> <4> [472.667512] WARNING: lib/list_debug.c:65 at __list_del_entry_valid_or_report+0xfe/0x120, CPU#0: device_reset/7989


> 
>   * igt@xe_pm@s4-vm-bind-prefetch:
>     - shard-lnl:          [PASS][3] -> [DMESG-WARN][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4336-3d6700a02638d446a4e8ad92a8212c3efef84ae0/shard-lnl-2/igt@xe_pm@s4-vm-bind-prefetch.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159711v1/shard-lnl-4/igt@xe_pm@s4-vm-bind-prefetch.html
Errors look unrelated from intel_vpu component.
> <6> [395.721186] mei_gsc_proxy 0000:00:16.0-0f73db04-97ab-4125-b893-e904ad0d5464: bound 0000:00:02.0 (ops xe_gsc_proxy_component_ops [xe])
> <3> [395.728859] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_ipc_send_receive_internal(): IPC receive failed: type VPU_JSM_MSG_PWR_D0I3_ENTER, ret -110
> <3> [395.729470] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_pm_runtime_suspend_cb(): Failed to prepare for d0i3: -110
> <6> [395.729732] Restarting tasks: Done
> <6> [395.729906] efivarfs: resyncing variable state
> <3> [395.732659] intel_vpu 0000:00:0b.0: [drm] *ERROR* ivpu_pm_runtime_suspend_cb(): Forcing cold boot due to previous errors


      reply	other threads:[~2026-01-08 19:00 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-06 21:27 [PATCH topic/xe-for-CI 0/4] drm/xe/guc: Bump GUC version for NVL-S, CRI Julia Filipchuk
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 1/4] Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 2/4] Revert "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 3/4] drm/xe/nvls: Define GuC firmware for NVL-S Julia Filipchuk
2026-01-06 21:27 ` [PATCH topic/xe-for-CI 4/4] topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Julia Filipchuk
2026-01-06 21:51 ` ✗ CI.checkpatch: warning for drm/xe/guc: Bump GUC version for NVL-S, CRI Patchwork
2026-01-08 19:01   ` Julia Filipchuk
2026-01-06 21:53 ` ✓ CI.KUnit: success " Patchwork
2026-01-06 22:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-07  1:21 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-08 19:00   ` Julia Filipchuk [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=e83e6e11-2c7b-48d8-a9ce-988ae5a7dcba@intel.com \
    --to=julia.filipchuk@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