From: Imre Deak <imre.deak@intel.com>
To: <I915-ci-infra@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.BAT: failure for drm/i915/dp: Fix panel replay in DSC mode (rev2)
Date: Fri, 17 Oct 2025 12:30:47 +0300 [thread overview]
Message-ID: <aPIMx-HJrhuM_xo7@ideak-desk> (raw)
In-Reply-To: <176055989763.19094.12450157913190398736@97596180aaec>
Hi CI team,
the failure is unrelated to the changes, see below for details, could
you please forward the patchset to testing on shards as well?
On Wed, Oct 15, 2025 at 08:24:57PM +0000, Patchwork wrote:
> == Series Details ==
>
> Series: drm/i915/dp: Fix panel replay in DSC mode (rev2)
> URL : https://patchwork.freedesktop.org/series/155587/
> State : failure
>
> == Summary ==
>
> CI Bug Log - changes from CI_DRM_17368 -> Patchwork_155587v2
> ====================================================
>
> Summary
> -------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_155587v2 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_155587v2, 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_155587v2/index.html
>
> Participating hosts (40 -> 38)
> ------------------------------
>
> Missing (2): fi-snb-2520m bat-adls-6
>
> Possible new issues
> -------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_155587v2:
>
> ### IGT changes ###
>
> #### Possible regressions ####
>
> * igt@gem_sync@basic-each:
> - fi-kbl-guc: [PASS][1] -> [INCOMPLETE][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_17368/fi-kbl-guc/igt@gem_sync@basic-each.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/fi-kbl-guc/igt@gem_sync@basic-each.html
There doesn't seem to be any display connected to fi-kbl-guc, so the
display specific changes in the patchset are unrelated to the failure.
It took me a while to determine that no display is connected. Is an
empty "i915_display_info0" linked on the CI result page supposed to
indicat this always? Could you indicate in a more obvious way that "No
display connected" on the results page?
The failure imo, is either due to a network connection issue (no WARNs,
errors in the log, dmesg ending with a flood of 0 bytes read) or some
GFX device DC6 -> DC0 transition or some GFX GEM related issue, see
more below. There are no pstore or other post-mortem logs available, so
it's impossible to know the root cause for sure. Putting much more
effort into making such logs available everywhere would be really
appreciated.
The fact that the connection is lost while the system is active, so not
around system suspend/resume (where network device failures were typical
in the past) makes the likelihood of a network device failure lower.
I see the GFX device being in DC6 when the connection is lost, so it's
possible the machine hangs when GFX is trying to exit to DC0.
A recent similar connection lost failure during a GEM/GT test on the
same fi-kbl-guc machine is:
https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_154881v1/fi-kbl-guc/igt@i915_selftest@live@requests.html
> Known issues
> ------------
>
> Here are the changes found in Patchwork_155587v2 that come from known issues:
>
> ### IGT changes ###
>
> #### Issues hit ####
>
> * igt@dmabuf@all-tests:
> - bat-apl-1: [PASS][3] -> [ABORT][4] ([i915#12904]) +1 other test abort
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_17368/bat-apl-1/igt@dmabuf@all-tests.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/bat-apl-1/igt@dmabuf@all-tests.html
>
> * igt@i915_selftest@live@late_gt_pm:
> - fi-cfl-8109u: [PASS][5] -> [DMESG-WARN][6] ([i915#13735]) +80 other tests dmesg-warn
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_17368/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/fi-cfl-8109u/igt@i915_selftest@live@late_gt_pm.html
>
> * igt@i915_selftest@live@workarounds:
> - bat-dg2-9: [PASS][7] -> [DMESG-FAIL][8] ([i915#12061]) +1 other test dmesg-fail
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_17368/bat-dg2-9/igt@i915_selftest@live@workarounds.html
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/bat-dg2-9/igt@i915_selftest@live@workarounds.html
> - bat-arls-6: [PASS][9] -> [DMESG-FAIL][10] ([i915#12061]) +1 other test dmesg-fail
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_17368/bat-arls-6/igt@i915_selftest@live@workarounds.html
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/bat-arls-6/igt@i915_selftest@live@workarounds.html
>
> * igt@kms_pipe_crc_basic@read-crc:
> - fi-cfl-8109u: [PASS][11] -> [DMESG-WARN][12] ([i915#13735] / [i915#13890]) +49 other tests dmesg-warn
> [11]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_17368/fi-cfl-8109u/igt@kms_pipe_crc_basic@read-crc.html
> [12]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/fi-cfl-8109u/igt@kms_pipe_crc_basic@read-crc.html
>
>
> [i915#12061]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12061
> [i915#12904]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/12904
> [i915#13735]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13735
> [i915#13890]: https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13890
>
>
> Build changes
> -------------
>
> * Linux: CI_DRM_17368 -> Patchwork_155587v2
>
> CI-20190529: 20190529
> CI_DRM_17368: 69ca30df000b382e7657f300148be505083377f2 @ git://anongit.freedesktop.org/gfx-ci/linux
> IGT_8585: 8585
> Patchwork_155587v2: 69ca30df000b382e7657f300148be505083377f2 @ git://anongit.freedesktop.org/gfx-ci/linux
>
> == Logs ==
>
> For more details see: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_155587v2/index.html
next prev parent reply other threads:[~2025-10-17 9:31 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-15 16:19 [PATCH v2 0/7] drm/i915/dp: Fix panel replay in DSC mode Imre Deak
2025-10-15 16:19 ` [PATCH v2 1/7] drm/i915/dsc: Add helper to enable the DSC configuration for a CRTC Imre Deak
2025-10-16 16:39 ` Hogander, Jouni
2025-10-15 16:19 ` [PATCH v2 2/7] drm/i915/dp: Ensure the FEC state stays disabled for UHBR links Imre Deak
2025-10-16 16:47 ` Hogander, Jouni
2025-10-15 16:19 ` [PATCH v2 3/7] drm/i915/dp: Export helper to determine if FEC on non-UHBR links is required Imre Deak
2025-10-16 16:56 ` Hogander, Jouni
2025-10-16 17:18 ` Imre Deak
2025-10-16 18:23 ` Hogander, Jouni
2025-10-16 20:00 ` Imre Deak
2025-10-17 4:00 ` Hogander, Jouni
2025-10-15 16:19 ` [PATCH v2 4/7] drm/i915/dp_mst: Reuse the DP-SST helper function to compute FEC config Imre Deak
2025-10-16 16:58 ` Hogander, Jouni
2025-10-15 16:19 ` [PATCH v2 5/7] drm/i915/dp_mst: Track DSC enabled status on the MST link Imre Deak
2025-10-16 17:01 ` Hogander, Jouni
2025-10-15 16:19 ` [PATCH v2 6/7] drm/i915/dp_mst: Recompute all MST link CRTCs if DSC gets enabled on the link Imre Deak
2025-10-16 17:04 ` Hogander, Jouni
2025-10-15 16:19 ` [PATCH v2 7/7] drm/i915/dp: Fix panel replay when DSC is enabled Imre Deak
2025-10-16 7:06 ` Hogander, Jouni
2025-10-15 20:24 ` ✗ i915.CI.BAT: failure for drm/i915/dp: Fix panel replay in DSC mode (rev2) Patchwork
2025-10-17 9:30 ` Imre Deak [this message]
2025-10-17 9:43 ` Grabski, Mateusz
2025-10-17 9:44 ` Imre Deak
2025-10-17 17:57 ` ✗ i915.CI.Full: " Patchwork
2025-10-17 18:58 ` 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=aPIMx-HJrhuM_xo7@ideak-desk \
--to=imre.deak@intel.com \
--cc=I915-ci-infra@lists.freedesktop.org \
--cc=intel-gfx@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