Hi,

https://patchwork.freedesktop.org/series/141932/ - Re-reported.

Thanks,
Tejasree

-----Original Message-----
From: Intel-gfx <intel-gfx-boun...@lists.freedesktop.org> On Behalf Of Gustavo 
Sousa
Sent: Friday, November 29, 2024 11:07 PM
To: i915-ci-in...@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)

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-in...@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_l...@reload.html
>   [2]: 
> https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_141932v2/bat-arlh-3
> /igt@i915_module_l...@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 via email to