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, I915-ci-infra@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/pf: Fix migration initialization
Date: Tue, 21 Jan 2025 21:41:40 +0100	[thread overview]
Message-ID: <eb3eecb7-343b-4200-b468-c7d8bd9bfcc3@intel.com> (raw)
In-Reply-To: <173742274949.2389727.16860213807102826496@b555e5b46a47>



On 21.01.2025 02:25, Patchwork wrote:
> == Series Details ==
> 
> Series: drm/xe/pf: Fix migration initialization
> URL   : https://patchwork.freedesktop.org/series/143765/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from xe-2516-fb87b4e061d1844beaca66c8446cfcf60db99a23_full -> xe-pw-143765v1_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with xe-pw-143765v1_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in xe-pw-143765v1_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-143765v1_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####

all unrelated

> 
>   * igt@kms_flip@2x-flip-vs-expired-vblank@ab-dp2-hdmi-a3:
>     - shard-bmg:          NOTRUN -> [FAIL][1] +1 other test fail
>    [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143765v1/shard-bmg-4/igt@kms_flip@2x-flip-vs-expired-vblank@ab-dp2-hdmi-a3.html
> 
>   * igt@kms_flip@flip-vs-expired-vblank:
>     - shard-bmg:          NOTRUN -> [INCOMPLETE][2] +1 other test incomplete
>    [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143765v1/shard-bmg-8/igt@kms_flip@flip-vs-expired-vblank.html
> 
>   * igt@kms_flip@plain-flip-ts-check@a-hdmi-a6:
>     - shard-dg2-set2:     [PASS][3] -> [INCOMPLETE][4]
>    [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2516-fb87b4e061d1844beaca66c8446cfcf60db99a23/shard-dg2-436/igt@kms_flip@plain-flip-ts-check@a-hdmi-a6.html
>    [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143765v1/shard-dg2-434/igt@kms_flip@plain-flip-ts-check@a-hdmi-a6.html
> 
>   * igt@xe_fault_injection@inject-fault-probe-function-xe_guc_relay_init:
>     - shard-adlp:         [PASS][5] -> [DMESG-WARN][6] +5 other tests dmesg-warn
>    [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2516-fb87b4e061d1844beaca66c8446cfcf60db99a23/shard-adlp-4/igt@xe_fault_injection@inject-fault-probe-function-xe_guc_relay_init.html
>    [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-143765v1/shard-adlp-8/igt@xe_fault_injection@inject-fault-probe-function-xe_guc_relay_init.html

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



  reply	other threads:[~2025-01-21 20:41 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-01-20 23:24 [PATCH] drm/xe/pf: Fix migration initialization Michal Wajdeczko
2025-01-20 23:39 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-20 23:39 ` ✓ CI.checkpatch: " Patchwork
2025-01-20 23:41 ` ✓ CI.KUnit: " Patchwork
2025-01-20 23:57 ` ✓ CI.Build: " Patchwork
2025-01-20 23:59 ` ✓ CI.Hooks: " Patchwork
2025-01-21  0:00 ` ✓ CI.checksparse: " Patchwork
2025-01-21  0:27 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-21  1:25 ` ✗ Xe.CI.Full: failure " Patchwork
2025-01-21 20:41   ` Michal Wajdeczko [this message]
2025-01-21 16:19 ` [PATCH] " Rodrigo Vivi

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=eb3eecb7-343b-4200-b468-c7d8bd9bfcc3@intel.com \
    --to=michal.wajdeczko@intel.com \
    --cc=I915-ci-infra@lists.freedesktop.org \
    --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