CI_DRM_3240 igt@kms_flip@plain-flip-interruptible KBL-shards (kms_flip:1411) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1328: (kms_flip:1411) CRITICAL: Failed assertion: crtc_count > 1 || crtc_idxs[0] < 2 (kms_flip:1411) CRITICAL: Last errno: 22, Invalid argument (kms_flip:1411) CRITICAL: set_mode may only fail on the 3rd pipe or in multiple crtc tests Subtest plain-flip-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3240/shard-kbl1/igt@kms_flip@plain-flip-interruptible.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3331/shard-kbl3/igt@kms_flip@modeset-vs-vblank-race-interruptible.html (kms_flip:1656) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1328: (kms_flip:1656) CRITICAL: Failed assertion: crtc_count > 1 || crtc_idxs[0] < 2 (kms_flip:1656) CRITICAL: Last errno: 22, Invalid argument (kms_flip:1656) CRITICAL: set_mode may only fail on the 3rd pipe or in multiple crtc tests Subtest modeset-vs-vblank-race-interruptible failed.
This test have the same fail in BXT igt@kms_flip@rcs-wf_vblank-vs-dpms igt@kms_flip@wf_vblank-vs-modeset -------------------------------------------------------------------------- IGT-Version: 1.20-g39ac6b8 (x86_64) (Linux: 4.15.0-rc2-drm-intel-qa-ww49-commit-bdf9b36+ x86_64) -------------------------------------------------------------------------- (kms_flip:1789) CRITICAL: Test assertion failure function run_test_on_crtc_set, file kms_flip.c:1324: (kms_flip:1789) CRITICAL: Failed assertion: crtc_count > 1 || crtc_idxs[0] < 2 (kms_flip:1789) CRITICAL: Last errno: 22, Invalid argument (kms_flip:1789) CRITICAL: set_mode may only fail on the 3rd pipe or in multiple crtc tests Subtest wf_vblank-vs-modeset failed.
The original issue for this bug hasn't happened for +600 runs and we don't even have data links for that. I will archive this bug from cibuglog perspective, but I keep it open since QA seem to have reproduced it.
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.