On Thursday, 22 September 2022 21:18:51 CEST Patchwork wrote: > == Series Details == > > Series: iommu: Remove iova cpu hotplugging flushing > URL : https://patchwork.freedesktop.org/series/108880/ > State : failure > > == Summary == > > CI Bug Log - changes from CI_DRM_12166_full -> Patchwork_108880v1_full > ==================================================== > > Summary > ------- > > **FAILURE** > > Serious unknown changes coming with Patchwork_108880v1_full absolutely need to be > verified manually. > > If you think the reported changes have nothing to do with the changes > introduced in Patchwork_108880v1_full, please notify your bug team to allow them > to document this new failure mode, which will reduce false positives in CI. > > > > Participating hosts (11 -> 12) > ------------------------------ > > Additional (1): shard-dg1 > > Possible new issues > ------------------- > > Here are the unknown changes that may have been introduced in Patchwork_108880v1_full: > > ### IGT changes ### > > #### Possible regressions #### > > * igt@i915_pm_dc@dc6-psr: > - shard-skl: NOTRUN -> [CRASH][1] > [1]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108880v1/shard-skl9/igt@i915_pm_dc@xxxxxxxxxxxx > > * igt@i915_selftest@live@gt_pm: > - shard-skl: NOTRUN -> [DMESG-FAIL][2] > [2]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108880v1/shard-skl4/igt@i915_selftest@live@gt_pm.html > > * igt@kms_color@ctm-0-75@pipe-b-edp-1: > - shard-skl: NOTRUN -> [FAIL][3] +5 similar issues > [3]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108880v1/shard-skl9/igt@kms_color@ctm-0-75@xxxxxxxxxxxxxxxxx > > * igt@kms_cursor_legacy@cursor-vs-flip@varying-size: > - shard-skl: NOTRUN -> [INCOMPLETE][4] +2 similar issues > [4]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108880v1/shard-skl3/igt@kms_cursor_legacy@cursor-vs-flip@xxxxxxxxxxxxxxxxx > > * igt@perf@non-zero-reason: > - shard-skl: NOTRUN -> [TIMEOUT][5] > [5]: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_108880v1/shard-skl9/igt@perf@xxxxxxxxxxxxxxxxxxxx All those "regressions" look to me like not related, possibly old, potentially hidden before due to CI blocked on some platforms by the issue that the patch has just resolved. I've asked Bug Filing to update CI buglog filters and re- report. Thanks, Janusz