On CI_DRM_3140 igt@kms_flip@plain-flip-ts-check-interruptible failed on HSW-shard (kms_flip:1709) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:1709) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1709) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:1709) CRITICAL: unexpected flip seq 597, expected 596 Subtest plain-flip-ts-check-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3140/shard-hsw4/igt@kms_flip@plain-flip-ts-check-interruptible.html
This test has failed on CFL QA Tests List: igt@kms_flip@2x-plain-flip-ts-check-interruptible ====================================== output sample ====================================== . . . (kms_flip:1909) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:1909) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1909) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:1909) CRITICAL: unexpected flip seq 3656, expected 3654 Subtest 2x-plain-flip-ts-check-interruptible failed. . . . This is my configuration: ====================================== Software ====================================== IGT-Version: 1.20-gb64c093 (x86_64) (Linux: 4.15.0-rc7-drm-tip-ww2-commit-fcf7fdf+ x86_64)
Created attachment 136702 [details] kernel log
This test fails on CFL QA igt@kms_flip@plain-flip-ts-check-interruptible IGT-Version: 1.22-g1bb3995 (x86_64) (Linux: 4.16.0-rc5-drm-intel-qa-ww11-commit-307515c+ x86_64) (kms_flip:1746) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:1746) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1746) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:1746) CRITICAL: unexpected flip seq 1660, expected 1658 Subtest 2x-plain-flip-ts-check-interruptible failed.
*** This bug has been marked as a duplicate of bug 100368 ***
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.