From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.Full: failure for drm/i915/dmc_wl: Do not check for DMC payload (rev2)
Date: Wed, 5 Feb 2025 08:46:57 -0300 [thread overview]
Message-ID: <173875601778.111435.12433294739961539471@intel.com> (raw)
In-Reply-To: <173824864151.2884264.8045096506404751820@b555e5b46a47>
Quoting Patchwork (2025-01-30 11:50:41-03:00)
>== Series Details ==
>
>Series: drm/i915/dmc_wl: Do not check for DMC payload (rev2)
>URL : https://patchwork.freedesktop.org/series/143951/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_16041_full -> Patchwork_143951v2_full
>====================================================
>
>Summary
>-------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_143951v2_full absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_143951v2_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.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_143951v2/index.html
>
>Participating hosts (11 -> 11)
>------------------------------
>
> No changes in participating hosts
>
>Possible new issues
>-------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_143951v2_full:
>
>### IGT changes ###
>
>#### Possible regressions ####
None of the failures below are related to this patch, since only PTL
effectively uses the DMC wakelock.
> * igt@gem_exec_gttfill@engines:
> - shard-dg2: [PASS][1] -> [FAIL][2] +1 other test fail
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16041/shard-dg2-5/igt@gem_exec_gttfill@engines.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_143951v2/shard-dg2-3/igt@gem_exec_gttfill@engines.html
This maps to
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13546 .
>
> * igt@perf_pmu@module-unload:
> - shard-tglu: [PASS][3] -> [INCOMPLETE][4]
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16041/shard-tglu-5/igt@perf_pmu@module-unload.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_143951v2/shard-tglu-9/igt@perf_pmu@module-unload.html
This possibly maps to
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13604 .
>
> * igt@sysfs_heartbeat_interval@nopreempt@vcs1:
> - shard-mtlp: [PASS][5] -> [DMESG-WARN][6]
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16041/shard-mtlp-1/igt@sysfs_heartbeat_interval@nopreempt@vcs1.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_143951v2/shard-mtlp-7/igt@sysfs_heartbeat_interval@nopreempt@vcs1.html
This maps to
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/13193 .
--
Gustavo Sousa
next prev parent reply other threads:[~2025-02-05 11:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-24 19:12 [PATCH] drm/i915/dmc_wl: Do not check for DMC payload Gustavo Sousa
2025-01-24 21:22 ` ✗ i915.CI.BAT: failure for " Patchwork
2025-01-27 13:31 ` Gustavo Sousa
2025-01-28 5:11 ` Ravali, JupallyX
2025-01-28 4:56 ` ✓ i915.CI.BAT: success " Patchwork
2025-01-30 9:41 ` [PATCH] " Luca Coelho
2025-01-30 12:58 ` ✓ i915.CI.BAT: success for drm/i915/dmc_wl: Do not check for DMC payload (rev2) Patchwork
2025-01-30 14:18 ` [PATCH] drm/i915/dmc_wl: Do not check for DMC payload Krzysztof Karas
2025-01-31 20:16 ` Gustavo Sousa
2025-01-31 23:49 ` Lucas De Marchi
2025-02-03 11:44 ` Gustavo Sousa
2025-02-05 9:07 ` Krzysztof Karas
2025-01-30 14:50 ` ✗ i915.CI.Full: failure for drm/i915/dmc_wl: Do not check for DMC payload (rev2) Patchwork
2025-02-05 11:46 ` Gustavo Sousa [this message]
2025-02-05 14:18 ` [PATCH] drm/i915/dmc_wl: Do not check for DMC payload Gustavo Sousa
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=173875601778.111435.12433294739961539471@intel.com \
--to=gustavo.sousa@intel.com \
--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