✗ Fi.CI.BAT: failure for drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev2)
Gustavo Sousa
gustavo.sousa at intel.com
Thu Nov 7 18:36:39 UTC 2024
Quoting Patchwork (2024-11-06 19:46:38-03:00)
>== Series Details ==
>
>Series: drm/i915/dmc_wl: Fixes and enablement for Xe3_LPD (rev2)
>URL : https://patchwork.freedesktop.org/series/140282/
>State : failure
>
>== Summary ==
>
>CI Bug Log - changes from CI_DRM_15648 -> Patchwork_140282v2
>====================================================
>
>Summary
>-------
>
> **FAILURE**
>
> Serious unknown changes coming with Patchwork_140282v2 absolutely need to be
> verified manually.
>
> If you think the reported changes have nothing to do with the changes
> introduced in Patchwork_140282v2, 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.
>
> External URL: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_140282v2/index.html
>
>Participating hosts (45 -> 43)
>------------------------------
>
> Missing (2): fi-snb-2520m bat-jsl-3
>
>Possible new issues
>-------------------
>
> Here are the unknown changes that may have been introduced in Patchwork_140282v2:
>
>### IGT changes ###
>
>#### Possible regressions ####
>
> * igt at i915_module_load@load:
> - fi-cfl-8109u: [PASS][1] -> [DMESG-WARN][2]
> [1]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15648/fi-cfl-8109u/igt@i915_module_load@load.html
> [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_140282v2/fi-cfl-8109u/igt@i915_module_load@load.html
>
> * igt at i915_selftest@live:
> - bat-twl-1: [PASS][3] -> [INCOMPLETE][4] +1 other test incomplete
> [3]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15648/bat-twl-1/igt@i915_selftest@live.html
> [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_140282v2/bat-twl-1/igt@i915_selftest@live.html
> - fi-skl-6600u: [PASS][5] -> [ABORT][6] +1 other test abort
> [5]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15648/fi-skl-6600u/igt@i915_selftest@live.html
> [6]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_140282v2/fi-skl-6600u/igt@i915_selftest@live.html
>
> * igt at i915_selftest@live at uncore:
> - fi-glk-j4005: [PASS][7] -> [ABORT][8] +1 other test abort
> [7]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15648/fi-glk-j4005/igt@i915_selftest@live@uncore.html
> [8]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_140282v2/fi-glk-j4005/igt@i915_selftest@live@uncore.html
>
> * igt at kms_busy@basic at flip:
> - fi-cfl-8109u: [PASS][9] -> [INCOMPLETE][10] +1 other test incomplete
> [9]: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_15648/fi-cfl-8109u/igt@kms_busy@basic@flip.html
> [10]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_140282v2/fi-cfl-8109u/igt@kms_busy@basic@flip.html
Some of the issues above are due to intel_dmc_wl_get() and
intel_dmc_wl_put() being called by MMIO functions before
intel_dmc_wl_init() was called. I posted a new version of the series to
address that issue.
--
Gustavo Sousa
More information about the Intel-gfx
mailing list