Starting at CI_DRM_3693 fail: (kms_atomic_transition:1667) igt-kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file igt_kms.c:3064: (kms_atomic_transition:1667) igt-kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1667) igt-kms-CRITICAL: Last errno: 22, Invalid argument (kms_atomic_transition:1667) igt-kms-CRITICAL: error: -22 != 0 Subtest plane-all-modeset-transition failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-snb5/igt@kms_atomic_transition@plane-all-modeset-transition.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-hsw7/igt@kms_atomic_transition@plane-all-modeset-transition.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-apl7/igt@kms_atomic_transition@plane-all-modeset-transition.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-kbl5/igt@kms_atomic_transition@plane-all-modeset-transition.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-snb3/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-hsw5/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-apl6/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-kbl6/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html GLK is OK on above tests, but strted hitting below with same error at the same run: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-glkb2/igt@kms_atomic_transition@plane-all-modeset-transition-fencing-internal-panels.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3693/shard-glkb2/igt@kms_atomic_transition@plane-all-modeset-transition-internal-panels.html
All patches integrated to CI_DRM_3693 are from Ville.
Reference: https://patchwork.freedesktop.org/series/37353/
Fix integrated IGT_4204 tests are green
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.