CI_DRM_3191 KBL-shards igt@kms_atomic_transition@plane-all-modeset-transition-fencing (kms_atomic_transition:1417) igt-kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file igt_kms.c:2753: (kms_atomic_transition:1417) igt-kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1417) igt-kms-CRITICAL: Last errno: 22, Invalid argument (kms_atomic_transition:1417) igt-kms-CRITICAL: error: -22 != 0 Subtest plane-all-modeset-transition-fencing failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3191/shard-kbl2/igt@kms_atomic_transition@plane-all-modeset-transition-fencing.html
Also, CI_DRM_3219 APL-shards (kms_atomic_transition:1607) igt-kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file igt_kms.c:2753: (kms_atomic_transition:1607) igt-kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1607) igt-kms-CRITICAL: Last errno: 16, Device or resource busy (kms_atomic_transition:1607) igt-kms-CRITICAL: error: -16 != 0 Subtest plane-all-transition-nonblocking-fencing failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3219/shard-apl1/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html
new subtest: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3231/shard-apl8/igt@kms_atomic_transition@plane-all-transition-nonblocking.html
Also, GLK-shards: (kms_atomic_transition:1811) igt-kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file igt_kms.c:2753: (kms_atomic_transition:1811) igt-kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1811) igt-kms-CRITICAL: Last errno: 16, Device or resource busy (kms_atomic_transition:1811) igt-kms-CRITICAL: error: -16 != 0 Subtest plane-all-transition-nonblocking-fencing failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3255/shard-glkb3/igt@kms_atomic_transition@plane-all-transition-nonblocking-fencing.html
*** This bug has been marked as a duplicate of bug 102671 ***
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.