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: Recommend GuC v70.55.3 for BMG, PTL
Date: Tue, 13 Jan 2026 08:42:43 -0800	[thread overview]
Message-ID: <df27979a-cda9-4ac6-8090-92419834b737@intel.com> (raw)
In-Reply-To: <176825926565.147986.10487189943479831807@a3b018990fe9>

On 1/12/2026 3:07 PM, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/guc: Recommend GuC v70.55.3 for BMG, PTL
> URL   : https://patchwork.freedesktop.org/series/159975/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-4368-e9383891a008f23b432b7b3c4ca2d7dd0f49824d_FULL -> xe-pw-159975v1_FULL
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-159975v1_FULL absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-159975v1_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 (2 -> 2)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in xe-pw-159975v1_FULL:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt@kms_cursor_legacy@cursorb-vs-flipa-legacy:
>     - shard-bmg:          [PASS][1] -> [INCOMPLETE][2]
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4368-e9383891a008f23b432b7b3c4ca2d7dd0f49824d/shard-bmg-8/igt@kms_cursor_legacy@cursorb-vs-flipa-legacy.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159975v1/shard-bmg-7/igt@kms_cursor_legacy@cursorb-vs-flipa-legacy.html
Failure seems unrelated. System looks stopped after this test.
> 
>   * igt@kms_flip@flip-vs-expired-vblank:
>     - shard-bmg:          [PASS][3] -> [FAIL][4] +1 other test fail
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4368-e9383891a008f23b432b7b3c4ca2d7dd0f49824d/shard-bmg-10/igt@kms_flip@flip-vs-expired-vblank.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159975v1/shard-bmg-4/igt@kms_flip@flip-vs-expired-vblank.html
Failure unrelated. Timing exceeded on kms-flip test.
> 
>   * igt@xe_pmu@engine-activity-suspend:
>     - shard-bmg:          [PASS][5] -> [DMESG-WARN][6]
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-4368-e9383891a008f23b432b7b3c4ca2d7dd0f49824d/shard-bmg-10/igt@xe_pmu@engine-activity-suspend.html
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-159975v1/shard-bmg-9/igt@xe_pmu@engine-activity-suspend.html
Failure seems unrelated.

Warning present related to missing fan firmware.
> <3> [389.062310] xe 0000:03:00.0: [drm] *ERROR* Load fan_control firmware failed with err -25

Test fails with ENOMEM. Seems to be resource constrained.
> <7> [390.908320] xe 0000:03:00.0: [drm:xe_pci_sriov_configure [xe]] PF: enabling 2 VFs
> <6> [390.958532] xe 0000:03:00.0: [drm] PF: Tile0: GT0: VF1..VF2 provisioned with 1073741824 (1.00 GiB) GGTT
> <6> [390.966513] xe 0000:03:00.0: [drm] PF: Tile0: GT0: VF1..VF2 provisioned with 6310330368 (5.88 GiB) LMEM
> <6> [390.966911] xe 0000:03:00.0: [drm] PF: Tile0: GT0: VF1..VF2 provisioned with 16384 GuC context IDs
> <6> [390.967130] xe 0000:03:00.0: [drm] PF: Tile0: GT0: VF1..VF2 provisioned with 64 GuC doorbell IDs
> <6> [390.967713] xe 0000:03:00.0: [drm] PF: Tile0: GT1: VF1..VF2 provisioned with 16384 GuC context IDs
> <6> [390.968341] xe 0000:03:00.0: [drm] PF: Tile0: GT1: VF1..VF2 provisioned with 64 GuC doorbell IDs
> <3> [390.968347] xe 0000:03:00.0: not enough MMIO resources for SR-IOV
> <5> [391.018719] xe 0000:03:00.0: [drm] PF: Failed to enable 2 VFs (-ENOMEM)
> <7> [391.048855] xe 0000:03:00.0: [drm:drm_client_dev_restore] fbdev: ret=0



      reply	other threads:[~2026-01-13 16:42 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-12 18:07 [PATCH 0/7] drm/xe/guc: Recommend GuC v70.55.3 for BMG, PTL Julia Filipchuk
2026-01-12 18:07 ` [PATCH 1/7] Revert "topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI" Julia Filipchuk
2026-01-12 18:07 ` [PATCH 2/7] Revert "drm/xe/nvls: Define GuC firmware for NVL-S" Julia Filipchuk
2026-01-12 18:07 ` [PATCH 3/7] Revert "drm/xe/pvc: Add GuC firmware definition" Julia Filipchuk
2026-01-12 18:07 ` [PATCH 4/7] drm/xe/guc: Recommend GuC v70.55.3 for BMG,PTL Julia Filipchuk
2026-01-14 23:56   ` Daniele Ceraolo Spurio
2026-01-12 18:07 ` [PATCH 5/7] drm/xe/pvc: Add GuC firmware definition Julia Filipchuk
2026-01-12 18:07 ` [PATCH 6/7] drm/xe/nvls: Define GuC firmware for NVL-S Julia Filipchuk
2026-01-12 18:07 ` [PATCH 7/7] topic/for-xe-CI: drm/xe/cri: Define GuC firmware for CRI Julia Filipchuk
2026-01-12 18:14 ` ✗ CI.checkpatch: warning for drm/xe/guc: Recommend GuC v70.55.3 for BMG, PTL Patchwork
2026-01-12 18:15 ` ✓ CI.KUnit: success " Patchwork
2026-01-12 18:58 ` ✓ Xe.CI.BAT: " Patchwork
2026-01-12 23:07 ` ✗ Xe.CI.Full: failure " Patchwork
2026-01-13 16:42   ` 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=df27979a-cda9-4ac6-8090-92419834b737@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