From: Imre Deak <imre.deak@intel.com>
To: JupallyX Ravali <jupallyx.ravali@intel.com>,
TejasreeX Illipilli <tejasreex.illipilli@intel.com>,
<I915-ci-infra@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.BAT: failure for drm/i915/tc: Fix enabled/disconnected DP-alt sink handling (rev4)
Date: Mon, 11 Aug 2025 18:04:32 +0300 [thread overview]
Message-ID: <aJoGgIX-VPN4_lSt@ideak-desk> (raw)
In-Reply-To: <175490280808.225841.18271231768889882943@1538d3639d33>
Hi CI team,
could you please re-report this result?
The failure is unrelated, see the details below.
On Mon, Aug 11, 2025 at 09:00:08AM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/tc: Fix enabled/disconnected DP-alt sink handling (rev4)
> URL : https://patchwork.freedesktop.org/series/152515/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_16975 -> Patchwork_152515v4
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_152515v4 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_152515v4, 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.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/index.html
>
> Participating hosts (43 -> 43)
> ------------------------------
>
> No changes in participating hosts
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_152515v4:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@core_hotunplug@unbind-rebind:
> - fi-kbl-7567u: [PASS][1] -> [ABORT][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/fi-kbl-7567u/igt@core_hotunplug@unbind-rebind.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/fi-kbl-7567u/igt@core_hotunplug@unbind-rebind.html
kbl doesn't have TypeC connectors, so the changes in the patchset are
unrelated to this failure.
The failure is:
<4> [163.791609] WARNING: CPU: 0 PID: 5768 at ./include/linux/sched.h:2185 __ww_mutex_wound+0xb9/0x160
and looks to be related to:
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/14804
>
> * igt@i915_pm_rpm@module-reload:
> - fi-tgl-1115g4: [PASS][3] -> [ABORT][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/fi-tgl-1115g4/igt@i915_pm_rpm@module-reload.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/fi-tgl-1115g4/igt@i915_pm_rpm@module-reload.html
tgl does have TypeC connectors, however nothing is connected on those,
so none of the TypeC changes in the patchset should have an effect
(they only matter if a sink got ever connected on a TypeC connector).
It looks to be the same ww_mutex() issue above.
> Known issues
> ------------
>
> Here are the changes found in Patchwork_152515v4 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@gem_exec_fence@nb-await@vecs0:
> - bat-rpls-4: [PASS][5] -> [DMESG-WARN][6] ([i915#13400]) +2 other tests dmesg-warn
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/bat-rpls-4/igt@gem_exec_fence@nb-await@vecs0.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/bat-rpls-4/igt@gem_exec_fence@nb-await@vecs0.html
>
> * igt@gem_lmem_swapping@basic:
> - fi-bsw-n3050: NOTRUN -> [SKIP][7] +3 other tests skip
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/fi-bsw-n3050/igt@gem_lmem_swapping@basic.html
>
> * igt@i915_selftest@live:
> - bat-jsl-1: [PASS][8] -> [DMESG-WARN][9] ([i915#13827]) +1 other test dmesg-warn
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/bat-jsl-1/igt@i915_selftest@live.html
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/bat-jsl-1/igt@i915_selftest@live.html
>
>
> #### Possible fixes ####
>
> * igt@core_hotunplug@unbind-rebind:
> - fi-bsw-n3050: [ABORT][10] -> [PASS][11]
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/fi-bsw-n3050/igt@core_hotunplug@unbind-rebind.html
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/fi-bsw-n3050/igt@core_hotunplug@unbind-rebind.html
>
> * igt@gem_exec_parallel@engines@fds:
> - bat-rpls-4: [DMESG-WARN][12] ([i915#13400]) -> [PASS][13] +1 other test pass
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/bat-rpls-4/igt@gem_exec_parallel@engines@fds.html
> [13]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/bat-rpls-4/igt@gem_exec_parallel@engines@fds.html
>
> * igt@i915_pm_rpm@module-reload:
> - bat-arls-5: [ABORT][14] -> [PASS][15]
> [14]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/bat-arls-5/igt@i915_pm_rpm@module-reload.html
> [15]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/bat-arls-5/igt@i915_pm_rpm@module-reload.html
>
> * igt@i915_selftest@live@workarounds:
> - bat-dg2-9: [DMESG-FAIL][16] ([i915#12061]) -> [PASS][17] +1 other test pass
> [16]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16975/bat-dg2-9/igt@i915_selftest@live@workarounds.html
> [17]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/bat-dg2-9/igt@i915_selftest@live@workarounds.html
>
>
> [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
> [i915#13400]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13400
> [i915#13827]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13827
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_16975 -> Patchwork_152515v4
>
> CI-20190529: 20190529
> CI_DRM_16975: b0354f42f0b7052682bfcc2f53b0aa023b6f68d8 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_8489: 4972020ea0f3d0ac8a0d7dd4f5419119b1b30995 @ https://gitlab.freedesktop.org/drm/igt-gpu-tools.git
> Patchwork_152515v4: b0354f42f0b7052682bfcc2f53b0aa023b6f68d8 @ git://anongit.freedesktop.org/gfx-ci/linux
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_152515v4/index.html
next prev parent reply other threads:[~2025-08-11 15:04 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-08-11 8:01 [CI 0/5] drm/i915/tc: Fix enabled/disconnected DP-alt sink handling Imre Deak
2025-08-11 8:01 ` [CI 1/5] drm/i915/lnl+/tc: Fix handling of an enabled/disconnected dp-alt sink Imre Deak
2025-08-11 8:01 ` [CI 2/5] drm/i915/icl+/tc: Cache the max lane count value Imre Deak
2025-08-11 8:01 ` [CI 3/5] drm/i915/lnl+/tc: Fix max lane count HW readout Imre Deak
2025-08-11 8:01 ` [CI 4/5] drm/i915/lnl+/tc: Use the cached max lane count value Imre Deak
2025-08-11 8:01 ` [CI 5/5] drm/i915/icl+/tc: Convert AUX powered WARN to a debug message Imre Deak
2025-08-11 9:00 ` ✗ i915.CI.BAT: failure for drm/i915/tc: Fix enabled/disconnected DP-alt sink handling (rev4) Patchwork
2025-08-11 15:04 ` Imre Deak [this message]
2025-08-12 5:17 ` Ravali, JupallyX
2025-08-12 5:10 ` ✓ i915.CI.BAT: success " Patchwork
2025-08-12 7:28 ` ✗ i915.CI.Full: failure " Patchwork
2025-08-12 9:39 ` Imre Deak
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=aJoGgIX-VPN4_lSt@ideak-desk \
--to=imre.deak@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jupallyx.ravali@intel.com \
--cc=tejasreex.illipilli@intel.com \
/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