✗ i915.CI.Full: failure for drm/i915: Fix harmfull driver register/unregister assymetry (rev4)

[Janusz Krzysztofik]

Hi I915-ci-infra at lists.freedesktop.org,

On Thursday, 6 March 2025 03:08:57 CET Patchwork wrote:
> == Series Details ==
> 
> Series: drm/i915: Fix harmfull driver register/unregister assymetry (rev4)
> URL   : https://patchwork.freedesktop.org/series/144436/
> State : failure
> 
> == Summary ==
> 
> CI Bug Log - changes from CI_DRM_16231_full -> Patchwork_144436v4_full
> ====================================================
> 
> Summary
> -------
> 
>   **FAILURE**
> 
>   Serious unknown changes coming with Patchwork_144436v4_full absolutely need to be
>   verified manually.
>   
>   If you think the reported changes have nothing to do with the changes
>   introduced in Patchwork_144436v4_full, please notify your bug team (I915-ci-infra at lists.freedesktop.org) to allow them
>   to document this new failure mode, which will reduce false positives in CI.
> 
>   
> 
> Participating hosts (10 -> 10)
> ------------------------------
> 
>   No changes in participating hosts
> 
> Possible new issues
> -------------------
> 
>   Here are the unknown changes that may have been introduced in Patchwork_144436v4_full:
> 
> ### IGT changes ###
> 
> #### Possible regressions ####
> 
>   * igt at i915_module_load@reload-with-fault-injection:
>     - shard-snb:          [PASS][1] -> [DMESG-WARN][2]
>    [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16231/shard-snb7/igt@i915_module_load@reload-with-fault-injection.html
>    [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144436v4/shard-snb6/igt@i915_module_load@reload-with-fault-injection.html

There is already a bug focused on this kernel message,
https://gitlab.freedesktop.org/drm/i915/kernel/-/issues/9820 ,
only expecting either abort or incomplete, not dmesg-warn result.
This series resolves issues standing behind those aborts/incompletes, but 
does not address that error message, leaving it untouched so now dmesg-warn is 
triggered.  Then, please extend filters of that bug with dmesg-warn result.  
Such reports will start appearing in regular CI runs as soon as the patch is 
accepted and applied.

> 
>   * igt at kms_flip@plain-flip-fb-recreate-interruptible at a-edp1:
>     - shard-mtlp:         [PASS][3] -> [FAIL][4]
>    [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16231/shard-mtlp-4/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
>    [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144436v4/shard-mtlp-2/igt@kms_flip@plain-flip-fb-recreate-interruptible@a-edp1.html
> 
>   * igt at kms_flip@plain-flip-ts-check-interruptible at a-hdmi-a2:
>     - shard-rkl:          [PASS][5] -> [FAIL][6]
>    [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_16231/shard-rkl-5/igt@kms_flip@plain-flip-ts-check-interruptible@a-hdmi-a2.html
>    [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_144436v4/shard-rkl-3/igt@kms_flip@plain-flip-ts-check-interruptible@a-hdmi-a2.html

Since the series only touches driver unregister path, and the two above listed 
tests don't enter that path, these two issues are not related.  Please update 
filters and re-report.

Thanks,
Janusz