Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Gustavo Sousa <gustavo.sousa@intel.com>
To: <i915-ci-infra@lists.freedesktop.org>, <intel-gfx@lists.freedesktop.org>
Cc: <intel-gfx@lists.freedesktop.org>
Subject: Re: ✗ i915.CI.BAT: failure for Flush DMC wakelock release work at the end of runtime suspend (rev2)
Date: Fri, 29 Nov 2024 14:36:57 -0300	[thread overview]
Message-ID: <173290181717.1637.311761190341957218@intel.com> (raw)
In-Reply-To: <173290066120.355976.6029837080249973542@b555e5b46a47>

Quoting Patchwork (2024-11-29 14:17:41-03:00)
>== Series Details ==
>
>Series: Flush DMC wakelock release work at the end of runtime suspend (rev2)
>URL   : https://patchwork.freedesktop.org/series/141932/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_15763 -> Patchwork_141932v2
>====================================================
>
>Summary
>-------
>
>  **FAILURE**
>
>  Serious unknown changes coming with Patchwork_141932v2 absolutely need to be
>  verified manually.
>  
>  If you think the reported changes have nothing to do with the changes
>  introduced in Patchwork_141932v2, 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_141932v2/index.html
>
>Participating hosts (46 -> 45)
>------------------------------
>
>  Missing    (1): fi-snb-2520m 
>
>Possible new issues
>-------------------
>
>  Here are the unknown changes that may have been introduced in Patchwork_141932v2:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
>  * igt@i915_module_load@reload:
>    - bat-arlh-3:         [PASS][1] -> [INCOMPLETE][2]
>   [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15763/bat-arlh-3/igt@i915_module_load@reload.html
>   [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_141932v2/bat-arlh-3/igt@i915_module_load@reload.html

This seems unrelated to this series. On the i915-side, the applied
changes are non-functional refactors and nothing on the log indicates an
issue on the DMC wakelock paths (all of which should be functionally a
no-op for ARL).

Please re-report.

--
Gustavo Sousa

  reply	other threads:[~2024-11-29 17:37 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-11-29 16:37 [PATCH v2 0/3] Flush DMC wakelock release work at the end of runtime suspend Gustavo Sousa
2024-11-29 16:37 ` [PATCH v2 1/3] drm/i915/dmc_wl: Extract intel_dmc_wl_flush_release_work() Gustavo Sousa
2024-11-29 18:25   ` Rodrigo Vivi
2024-11-30 17:09     ` Rodrigo Vivi
2024-11-29 16:37 ` [PATCH v2 2/3] drm/xe/display: Extract xe_display_pm_runtime_suspend_late() Gustavo Sousa
2024-11-29 18:25   ` Rodrigo Vivi
2024-11-29 16:37 ` [PATCH v2 3/3] drm/xe/display: Flush DMC wakelock release work on runtime suspend Gustavo Sousa
2024-11-29 18:26   ` Rodrigo Vivi
2024-11-29 17:03 ` ✗ Fi.CI.SPARSE: warning for Flush DMC wakelock release work at the end of runtime suspend (rev2) Patchwork
2024-11-29 17:17 ` ✗ i915.CI.BAT: failure " Patchwork
2024-11-29 17:36   ` Gustavo Sousa [this message]
2024-12-02  9:19     ` Illipilli, TejasreeX
2024-12-02  9:17 ` ✓ i915.CI.BAT: success " Patchwork
2024-12-02 11:31 ` ✗ i915.CI.Full: failure " Patchwork

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=173290181717.1637.311761190341957218@intel.com \
    --to=gustavo.sousa@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