All of 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 drm/xe: Don't treat SR-IOV platforms as reclaim unsafe
Date: Wed, 5 Feb 2025 18:21:18 +0100	[thread overview]
Message-ID: <06b41a9f-db03-4348-8bf2-e62a2a4652ea@intel.com> (raw)
In-Reply-To: <173877505287.1534803.3974260777427551466@b555e5b46a47>



On 05.02.2025 18:04, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe: Don't treat SR-IOV platforms as reclaim unsafe
> URL   : https://patchwork.freedesktop.org/series/144369/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2600-5f025a38e4ddb453bfbf89d4ab37facf07427721_full -> xe-pw-144369v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-144369v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-144369v1_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-144369v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####

unrelated

> 
>   * igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@pipe-a-hdmi-a-1:
>     - shard-adlp:         [PASS][1] -> [DMESG-WARN][2] +1 other test dmesg-warn
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2600-5f025a38e4ddb453bfbf89d4ab37facf07427721/shard-adlp-8/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@pipe-a-hdmi-a-1.html
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144369v1/shard-adlp-6/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing@pipe-a-hdmi-a-1.html

<3> [297.013815] xe 0000:00:02.0: [drm] *ERROR* AUX B/DDI B/PHY B: did
not complete or timeout within 10ms (status 0xad40023f)

> 
>   * igt@xe_module_load@many-reload:
>     - shard-dg2-set2:     [PASS][3] -> [FAIL][4] +1 other test fail
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2600-5f025a38e4ddb453bfbf89d4ab37facf07427721/shard-dg2-466/igt@xe_module_load@many-reload.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144369v1/shard-dg2-464/igt@xe_module_load@many-reload.html

FACT: there was no DG2 on boot, only ADLP

[60.032030] [FACT before any test] new:
hardware.pci.gpu_at_addr.0000:00:02.0: 8086:4680 Intel Alderlake_s
(Gen12) AlderLake-S GT1
[60.036187] [FACT before any test] new:
hardware.pci.drm_card_at_addr.0000:00:02.0: card0
[60.038099] [FACT before any test] new: kernel.kmod_is_loaded.xe: true



  reply	other threads:[~2025-02-05 17:21 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-05 12:01 [PATCH] drm/xe: Don't treat SR-IOV platforms as reclaim unsafe Michal Wajdeczko
2025-02-05 13:33 ` ✓ CI.Patch_applied: success for " Patchwork
2025-02-05 13:34 ` ✓ CI.checkpatch: " Patchwork
2025-02-05 13:35 ` ✓ CI.KUnit: " Patchwork
2025-02-05 14:03 ` ✓ CI.Build: " Patchwork
2025-02-05 14:06 ` ✓ CI.Hooks: " Patchwork
2025-02-05 14:07 ` ✓ CI.checksparse: " Patchwork
2025-02-05 14:27 ` ✓ Xe.CI.BAT: " Patchwork
2025-02-05 17:04 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-05 17:21   ` Michal Wajdeczko [this message]
2025-02-06 12:05 ` [PATCH] " Bernatowicz, Marcin
2025-02-06 15:06 ` Thomas Hellström

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=06b41a9f-db03-4348-8bf2-e62a2a4652ea@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.