From: Michal Wajdeczko <michal.wajdeczko@intel.com>
To: intel-xe@lists.freedesktop.org
Subject: Re: ✗ Xe.CI.Full: failure for drm/xe/relay: Don't use GFP_KERNEL for new transactions
Date: Tue, 4 Feb 2025 11:58:10 +0100 [thread overview]
Message-ID: <9008880d-e91e-4f29-a4c8-7b1e90bdc602@intel.com> (raw)
In-Reply-To: <173835851583.3314806.11712122875644547206@b555e5b46a47>
On 31.01.2025 22:21, Patchwork wrote:
> == Series Details ==
>
> Series: drm/xe/relay: Don't use GFP_KERNEL for new transactions
> URL : https://patchwork.freedesktop.org/series/144192/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from xe-2581-9ad9ba100db6b9b53b314a7c4f20674593614ae0_full -> xe-pw-144192v1_full
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with xe-pw-144192v1_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in xe-pw-144192v1_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-144192v1_full:
>
> ### IGT changes ###
>
> #### Possible regressions ####
all false positives
>
> * igt@kms_cursor_crc@cursor-offscreen-256x256@pipe-d-hdmi-a-6:
> - shard-dg2-set2: NOTRUN -> [INCOMPLETE][1] +1 other test incomplete
> [1]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144192v1/shard-dg2-434/igt@kms_cursor_crc@cursor-offscreen-256x256@pipe-d-hdmi-a-6.html
<7>[ 335.336488] [IGT] kms_cursor_crc: finished subtest
pipe-D-HDMI-A-6, SUCCESS
<7>[ 335.336759] [IGT] kms_cursor_crc: finished subtest
cursor-offscreen-256x256, SUCCESS
>
> * igt@kms_plane@plane-position-covered@pipe-b-plane-5:
> - shard-dg2-set2: [PASS][2] -> [ABORT][3] +1 other test abort
> [2]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2581-9ad9ba100db6b9b53b314a7c4f20674593614ae0/shard-dg2-463/igt@kms_plane@plane-position-covered@pipe-b-plane-5.html
> [3]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144192v1/shard-dg2-432/igt@kms_plane@plane-position-covered@pipe-b-plane-5.html
<6> [140.458994] [IGT] kms_plane: finished subtest pipe-B-plane-5, SUCCESS
<6> [140.459295] [IGT] kms_plane: finished subtest
plane-position-covered, SUCCESS
...
<6> [140.541820] [IGT] kms_plane: exiting, ret=0
>
> * igt@kms_plane_lowres@tiling-4@pipe-a-dp-2:
> - shard-bmg: [PASS][4] -> [INCOMPLETE][5] +1 other test incomplete
> [4]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2581-9ad9ba100db6b9b53b314a7c4f20674593614ae0/shard-bmg-5/igt@kms_plane_lowres@tiling-4@pipe-a-dp-2.html
> [5]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144192v1/shard-bmg-5/igt@kms_plane_lowres@tiling-4@pipe-a-dp-2.html
<7>[ 214.567241] [IGT] kms_plane_lowres: starting subtest tiling-4
<7>[ 214.568131] [IGT] kms_plane_lowres: starting dynamic subtest
pipe-A-DP-2
...
<7>[ 225.128597] [IGT] kms_plane_lowres: finished subtest pipe-A-DP-2,
SUCCESS
>
> * igt@xe_fault_injection@inject-fault-probe-function-xe_sriov_init:
> - shard-adlp: [PASS][6] -> [DMESG-WARN][7]
> [6]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-2581-9ad9ba100db6b9b53b314a7c4f20674593614ae0/shard-adlp-2/igt@xe_fault_injection@inject-fault-probe-function-xe_sriov_init.html
> [7]: https://intel-gfx-ci.01.org/tree/intel-xe/xe-pw-144192v1/shard-adlp-2/igt@xe_fault_injection@inject-fault-probe-function-xe_sriov_init.html
<3> [370.681177] xe 0000:00:02.0: [drm] *ERROR* AUX B/DDI B/PHY B: did
not complete or timeout within 10ms (status 0xad40023f)
<3> [370.691621] xe 0000:00:02.0: [drm] *ERROR* AUX B/DDI B/PHY B: did
not complete or timeout within 10ms (status 0xad40023f)
next prev parent reply other threads:[~2025-02-04 10:58 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-31 15:37 [PATCH] drm/xe/relay: Don't use GFP_KERNEL for new transactions Michal Wajdeczko
2025-01-31 15:42 ` ✓ CI.Patch_applied: success for " Patchwork
2025-01-31 15:43 ` ✓ CI.checkpatch: " Patchwork
2025-01-31 15:45 ` ✓ CI.KUnit: " Patchwork
2025-01-31 16:01 ` ✓ CI.Build: " Patchwork
2025-01-31 16:04 ` ✓ CI.Hooks: " Patchwork
2025-01-31 16:05 ` ✓ CI.checksparse: " Patchwork
2025-01-31 16:25 ` ✓ Xe.CI.BAT: " Patchwork
2025-01-31 21:21 ` ✗ Xe.CI.Full: failure " Patchwork
2025-02-04 10:58 ` Michal Wajdeczko [this message]
2025-02-03 9:20 ` [PATCH] " Bernatowicz, Marcin
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=9008880d-e91e-4f29-a4c8-7b1e90bdc602@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