https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_6/fi-kbl-7500u/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking.html (kms_atomic_transition:5181) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3225: (kms_atomic_transition:5181) igt_kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:5181) igt_kms-CRITICAL: Last errno: 16, Device or resource busy (kms_atomic_transition:5181) igt_kms-CRITICAL: error: -16 != 0 Subtest 1x-modeset-transitions-nonblocking failed. I was considering re-open of bug 104848. However, that bug only contains dead links so there is no point in re-opening that one.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_7/fi-cnl-y3/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing.html (kms_atomic_transition:1268) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3225: (kms_atomic_transition:1268) igt_kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1268) igt_kms-CRITICAL: Last errno: 16, Device or resource busy (kms_atomic_transition:1268) igt_kms-CRITICAL: error: -16 != 0 Subtest 1x-modeset-transitions-nonblocking-fencing failed.
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_11/fi-ivb-3770/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing.html (kms_atomic_transition:1252) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3231: (kms_atomic_transition:1252) igt_kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1252) igt_kms-CRITICAL: Last errno: 16, Device or resource busy (kms_atomic_transition:1252) igt_kms-CRITICAL: error: -16 != 0 Subtest 1x-modeset-transitions-nonblocking-fencing failed.
Used to be seen every 10 runs, not seen since CI_DRM_4726_full (2 months / 883 runs ago).
Came back again https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_145/fi-kbl-7500u/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing.html Starting subtest: 1x-modeset-transitions-nonblocking-fencing (kms_atomic_transition:1394) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3399: (kms_atomic_transition:1394) igt_kms-CRITICAL: Failed assertion: ret == 0 (kms_atomic_transition:1394) igt_kms-CRITICAL: Last errno: 16, Device or resource busy (kms_atomic_transition:1394) igt_kms-CRITICAL: error: -16 != 0 Subtest 1x-modeset-transitions-nonblocking-fencing failed.
A CI Bug Log filter associated to this bug has been updated: {- fi-igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy -} {+ fi-igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_177/fi-cfl-8109u/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing.html
A CI Bug Log filter associated to this bug has been updated: {- fi-igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy -} {+ ILK KBL GLK CFL: fi-igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy +} No new failures caught with the new filter
Adding SKL and CFL to the platform list and removing CNL. SKL had failures six months ago that were blamed on bug 108228 so they weren't captured by the filter here.
A CI Bug Log filter associated to this bug has been updated: {- ILK KBL GLK CFL: fi-igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy -} {+ ILK shard-skl* KBL GLK CFL: fi-igt@kms_atomic_transition@1x-modeset-transitions-nonblocking* - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy +} No new failures caught with the new filter
The last hit reported by cibuglog is almost 10 months old and doesn't have any smoking guns that I can see in the logs. Marking this as resolved; we can reopen if more failures turn up in the future.
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.