Summary: | [BAT][CI] igt@kms_flip@' - Failed assertion: es->current_seq == es->last_seq + o->seq_step | Failed assertion: ev.sequence == last_seq + 1 | ||||||
---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> | ||||
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Status: | RESOLVED MOVED | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> | ||||
Severity: | normal | ||||||
Priority: | medium | CC: | intel-gfx-bugs, jani.saarinen, marta.lofstedt | ||||
Version: | DRI git | ||||||
Hardware: | Other | ||||||
OS: | All | ||||||
Whiteboard: | ReadyForDev | ||||||
i915 platform: | BSW/CHT, BXT, CFL, CNL, GLK, HSW, ILK, IVB, KBL, SKL, SNB | i915 features: | display/Other | ||||
Attachments: |
|
Description
Martin Peres
2017-03-24 09:27:39 UTC
Selecting the platform and updating the importance. Note that the run this failed on was a KASAN test, i.e. the kernel was a bit slower than normal. Dropping the priority, since it is only seen with KASAN. It needs to be fixed though! Adding tag into "Whiteboard" field - ReadyForDev The bug still active *Status is correct *Platform is included *Feature is included *Priority and Severity correctly set *Logs included (In reply to Martin Peres from comment #3) > Dropping the priority, since it is only seen with KASAN. It needs to be > fixed though! Hello, Is there any update on this bug? Thank you. Elisabet, please note that that was seen on special KASAN build. Now also seen on the sharded runs: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2973/shard-hsw1/igt@kms_flip@flip-vs-absolute-wf_vblank.html (In reply to Martin Peres from comment #7) > Now also seen on the sharded runs: > https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_2973/shard-hsw1/ > igt@kms_flip@flip-vs-absolute-wf_vblank.html Also seen here: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3012/shard-hsw3/igt@kms_flip@plain-flip-ts-check.html Also seen on SNB when running igt@kms_flip@plain-flip-fb-recreate-interruptible: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3047/shard-snb2/igt@kms_flip@plain-flip-fb-recreate-interruptible.html *** Bug 103005 has been marked as a duplicate of this bug. *** Also, on APL-shards: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3200/shard-apl4/igt@kms_flip@flip-vs-wf_vblank-interruptible.html Also, CI_DRM_3212 KBL- and APL-shards this time on: igt@kms_flip@plain-flip-fb-recreate (kms_flip:1610) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:1610) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1610) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1610) CRITICAL: unexpected flip seq 5140, expected 5139 Subtest plain-flip-fb-recreate failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3212/shard-kbl5/igt@kms_flip@plain-flip-fb-recreate.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3212/shard-apl4/igt@kms_flip@plain-flip-fb-recreate.html Also, APL-shards CI_DRM_3220 this time on: igt@kms_flip@wf_vblank-ts-check-interruptible (kms_flip:1445) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:1445) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1445) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:1445) CRITICAL: unexpected vblank seq 3943, expected 3941 Subtest wf_vblank-ts-check-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3220/shard-apl2/igt@kms_flip@wf_vblank-ts-check-interruptible.html reproduced on new subtest: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3251/shard-apl5/igt@kms_flip@vblank-vs-suspend-interruptible.html APL-shards new subtest: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3251/shard-apl5/igt@kms_flip@vblank-vs-suspend.html CI_DRM_3254 GLK-shards igt@kms_flip@vblank-vs-suspend fail: (kms_flip:1738) CRITICAL: Test assertion failure function check_state, file kms_flip.c:508: (kms_flip:1738) CRITICAL: Failed assertion: es->current_seq - es->last_seq <= 150 (kms_flip:1738) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1738) CRITICAL: unexpected vblank seq 999, should be < 788 Subtest vblank-vs-suspend failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3254/shard-glkb4/igt@kms_flip@vblank-vs-suspend.html *** Bug 102699 has been marked as a duplicate of this bug. *** CI_DRM_3287 shard-apl6 igt@kms_flip@vblank-vs-suspend-interruptible fail: (kms_flip:3044) CRITICAL: Test assertion failure function check_state, file kms_flip.c:497: (kms_flip:3044) CRITICAL: Failed assertion: es->current_seq - (es->last_seq + o->seq_step) <= 1UL << 23 (kms_flip:3044) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3044) CRITICAL: unexpected vblank seq 6853, should be >= 6854 Subtest vblank-vs-suspend-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3287/shard-apl6/igt@kms_flip@vblank-vs-suspend-interruptible.html new subtest: CI_DRM_3288 shard-glkb3 igt@kms_flip@plain-flip-fb-recreate (kms_flip:4115) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:4115) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:4115) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:4115) CRITICAL: unexpected flip seq 46944, expected 46943 Subtest plain-flip-fb-recreate failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3288/shard-glkb3/igt@kms_flip@plain-flip-fb-recreate.html CI_DRM_3288 shard-apl4 igt@kms_flip@plain-flip-fb-recreate (kms_flip:3751) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:3751) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:3751) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3751) CRITICAL: unexpected flip seq 31360, expected 31359 Subtest plain-flip-fb-recreate failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3288/shard-apl4/igt@kms_flip@plain-flip-fb-recreate.html *** Bug 102504 has been marked as a duplicate of this bug. *** Fixing the confusing title, it's for a lot more machines than just hsw. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3364/shard-apl4/igt@kms_flip@flip-vs-blocking-wf-vblank.html (kms_flip:3878) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:3878) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:3878) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3878) CRITICAL: unexpected flip seq 10390, expected 10389 Subtest flip-vs-blocking-wf-vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3364/shard-glkb1/igt@kms_flip@flip-vs-blocking-wf-vblank.html (kms_flip:5751) CRITICAL: Test assertion failure function calibrate_ts, file kms_flip.c:1196: (kms_flip:5751) CRITICAL: Failed assertion: ev.sequence == last_seq + 1 (kms_flip:5751) CRITICAL: error: 75764 != 75763 Subtest flip-vs-blocking-wf-vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4017/fi-hsw-4770r/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:3899) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:3899) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:3899) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3899) CRITICAL: unexpected flip seq 784, expected 783 Subtest basic-flip-vs-wf_vblank failed. Note this is from the 4.15.0-rc5 kernel, which is currently affected by bug 103951. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3464/shard-apl3/igt@kms_flip@blocking-wf_vblank.html and so far on all consecutive runs, i.e. CI_DRM_3470 (kms_flip:1706) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:1706) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1706) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1706) CRITICAL: unexpected vblank seq 7490, expected 7489 Subtest blocking-wf_vblank failed. In https://intel-gfx-ci.01.org/cibuglog/index.html%3Faction_failures_history=213.html I also see some stuff not covered by this bug. In particular this bug doesn't cover incompletes or dmesg-fail. (In reply to Maarten Lankhorst from comment #27) > In > https://intel-gfx-ci.01.org/cibuglog/index. > html%3Faction_failures_history=213.html > > I also see some stuff not covered by this bug. In particular this bug > doesn't cover incompletes or dmesg-fail. This bug is only about tests failing due to "Failed assertion: es->current_seq == es->last_seq + o->seq_step". The history thing in cibuglog is useless. If an issue is filed on a (machine,test) pair, all other issues for that pair is "covered" and never seen in cibuglog. This is why Martin is working on cibuglog 2.0. This tests has failed on CFL QA igt@kms_flip@flip-vs-absolute-wf_vblank-interruptible igt@kms_flip@plain-flip-fb-recreate-interruptible igt@kms_flip@plain-flip-ts-check-interruptible IGT-Version: 1.20-g4cd4cc4 (x86_64) (Linux: 4.15.0-rc5-drm-tip-ww52-commit-42a41a5+ x86_64) (kms_flip:3103) igt-kms-WARNING: connector 49/eDP-1 has no modes (kms_flip:3103) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:3103) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:3103) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3103) CRITICAL: unexpected flip seq 69437, expected 69435 Created attachment 136434 [details] kernel log (comment 29) Note, we added 2x displays for HSW a couple of days ago: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3664/shard-hsw6/igt@kms_flip@2x-wf_vblank-ts-check.html (kms_flip:1926) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:536: (kms_flip:1926) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1926) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1926) CRITICAL: unexpected vblank seq 1636, expected 1635 Subtest 2x-wf_vblank-ts-check failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3675/shard-hsw7/igt@kms_flip@2x-plain-flip-fb-recreate.html (kms_flip:9163) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:9163) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:9163) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:9163) CRITICAL: unexpected flip seq 61073, expected 61072 Subtest 2x-plain-flip-fb-recreate failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4177/shard-hsw1/igt@kms_flip@2x-plain-flip-ts-check-interruptible.html (kms_flip:2695) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:2695) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:2695) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:2695) CRITICAL: unexpected flip seq 163476, expected 163475 Subtest 2x-plain-flip-ts-check-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4173/shard-hsw6/igt@kms_flip@2x-flip-vs-absolute-wf_vblank-interruptible.html (kms_flip:3054) CRITICAL: Test assertion failure function calibrate_ts, file kms_flip.c:1164: (kms_flip:3054) CRITICAL: Failed assertion: ev.sequence == last_seq + 1 (kms_flip:3054) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:3054) CRITICAL: error: 19155 != 19154 Subtest 2x-flip-vs-absolute-wf_vblank-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3696/shard-hsw6/igt@kms_flip@2x-flip-vs-absolute-wf_vblank.html (kms_flip:9142) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:9142) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:9142) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:9142) CRITICAL: unexpected flip seq 49497, expected 49496 Subtest 2x-flip-vs-absolute-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4207/shard-hsw6/igt@kms_flip@2x-flip-vs-wf_vblank.html (kms_flip:4319) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:4319) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:4319) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:4319) CRITICAL: unexpected vblank seq 16893, expected 16892 Subtest 2x-flip-vs-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3720/shard-hsw7/igt@kms_flip@2x-plain-flip-ts-check.html (kms_flip:5651) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:5651) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:5651) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:5651) CRITICAL: unexpected flip seq 40065, expected 40064 Subtest 2x-plain-flip-ts-check failed. These test fail on CFL QA igt@kms_flip@plain-flip-fb-recreate igt@kms_flip@plain-flip-fb-recreate-interruptible igt@kms_flip@plain-flip-ts-check igt@kms_flip@plain-flip-ts-check-interruptible using IGT-Version: 1.21-g08e8621 (x86_64) (Linux: 4.15.0-drm-intel-qa-ww6-commit-64279a8+ x86_64) (kms_flip:2402) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:2402) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:2402) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:2402) CRITICAL: unexpected flip seq 9795, expected 9793 Subtest plain-flip-fb-recreate-interruptible failed. fi-hsw-4770r impact removed since we don't have data links for any reproduction from that machine anymore https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3747/shard-hsw7/igt@kms_flip@2x-plain-flip-fb-recreate-interruptible.html (kms_flip:2867) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:2867) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:2867) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:2867) CRITICAL: unexpected flip seq 18773, expected 18772 Subtest 2x-plain-flip-fb-recreate-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4232/shard-hsw1/igt@kms_flip@2x-flip-vs-wf_vblank-interruptible.html (kms_flip:2259) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:2259) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:2259) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:2259) CRITICAL: unexpected flip seq 2025, expected 2024 Subtest 2x-flip-vs-wf_vblank-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4247/shard-hsw6/igt@kms_flip@2x-flip-vs-blocking-wf-vblank.html (kms_flip:13531) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:13531) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:13531) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:13531) CRITICAL: unexpected flip seq 49076, expected 49075 Subtest 2x-flip-vs-blocking-wf-vblank failed. *** Bug 100369 has been marked as a duplicate of this bug. *** Also visible on braswell (with KASAN): (kms_flip:1465) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:1465) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1465) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1465) CRITICAL: unexpected flip seq 5675, expected 5674 Subtest basic-flip-vs-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/kasan_6/fi-bsw-n3050/igt@kms_flip@basic-flip-vs-wf_vblank.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3796/shard-hsw4/igt@kms_flip@2x-blocking-wf_vblank.html (kms_flip:6776) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:6776) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:6776) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:6776) CRITICAL: unexpected vblank seq 32769, expected 32768 Subtest 2x-blocking-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4309/fi-cfl-s2/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:4354) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:4354) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:4354) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:4354) CRITICAL: unexpected flip seq 16136, expected 16135 Subtest basic-flip-vs-wf_vblank failed. *** Bug 103928 has been marked as a duplicate of this bug. *** https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3930/fi-skl-6770hq/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:4046) CRITICAL: Test assertion failure function calibrate_ts, file ../tests/kms_flip.c:1163: (kms_flip:4046) CRITICAL: Failed assertion: ev.sequence == last_seq + 1 (kms_flip:4046) CRITICAL: error: 525 != 524 Subtest basic-flip-vs-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-snb-2520m/igt@kms_flip@2x-plain-flip-fb-recreate-interruptible.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-snb-2520m/igt@kms_flip@2x-plain-flip-ts-check.html https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1/fi-snb-2520m/igt@kms_flip@2x-plain-flip-fb-recreate.html (kms_flip:1473) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:535: (kms_flip:1473) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1473) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:1473) CRITICAL: unexpected flip seq 5238, expected 5237 Subtest 2x-plain-flip-fb-recreate-interruptible failed. The below test list fail on CFL QA igt@kms_flip@plain-flip-fb-recreate igt@kms_flip@plain-flip-fb-recreate-interruptible igt@kms_flip@plain-flip-ts-check IGT-Version: 1.22-g94e8862 (x86_64) (Linux: 4.16.0-rc6-drm-intel-qa-ww12-commit-9d737ce+ x86_64) (kms_flip:1675) CRITICAL: Test assertion failure function check_state, file kms_flip.c:535: (kms_flip:1675) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1675) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:1675) CRITICAL: unexpected flip seq 754, expected 752 Subtest plain-flip-fb-recreate failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_6/fi-bdw-gvtdvm/igt@kms_flip@plain-flip-fb-recreate-interruptible.html (kms_flip:1232) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:535: (kms_flip:1232) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:1232) CRITICAL: Last errno: 4, Interrupted system call (kms_flip:1232) CRITICAL: unexpected flip seq 606, expected 605 Subtest plain-flip-fb-recreate-interruptible failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4382/fi-cfl-s3/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:3956) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:496: (kms_flip:3956) CRITICAL: Failed assertion: es->current_seq - (es->last_seq + o->seq_step) <= 1UL << 23 (kms_flip:3956) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3956) CRITICAL: unexpected flip seq 302, should be >= 303 Subtest basic-flip-vs-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4390/fi-cnl-psr/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:3703) CRITICAL: Test assertion failure function calibrate_ts, file ../tests/kms_flip.c:1163: (kms_flip:3703) CRITICAL: Failed assertion: ev.sequence == last_seq + 1 (kms_flip:3703) CRITICAL: error: 18157 != 18156 Subtest basic-flip-vs-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4072/fi-ilk-m540/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:3663) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:496: (kms_flip:3663) CRITICAL: Failed assertion: es->current_seq - (es->last_seq + o->seq_step) <= 1UL << 23 (kms_flip:3663) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3663) CRITICAL: unexpected flip seq 653, should be >= 654 Subtest basic-flip-vs-wf_vblank failed. https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4269_2/fi-cnl-psr/igt@kms_flip@basic-flip-vs-wf_vblank.html (kms_flip:3722) CRITICAL: Test assertion failure function check_state, file ../tests/kms_flip.c:496: (kms_flip:3722) CRITICAL: Failed assertion: es->current_seq - (es->last_seq + o->seq_step) <= 1UL << 23 (kms_flip:3722) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3722) CRITICAL: unexpected flip seq 18695, should be >= 18696 Subtest basic-flip-vs-wf_vblank failed. *** Bug 103004 has been marked as a duplicate of this bug. *** A CI Bug Log filter associated to this bug has been updated: {- fi-skl-6770hq, fi-cfl-s2/3, fi-cnl-psr: igt@kms_flip@basic-flip-vs-wf_vblank - Failed assertion: ev.sequence == last_seq + 1 -} {+ SKL GLK CFL CNL: igt@kms_flip@(basic-flip-vs-wf_vblank|plain-flip-ts-check) - Failed assertion: ev.sequence == last_seq + 1 +} No new failures caught with the new filter Seems that we are a bit too slow processing in one vblank, especially with the slower machines. It depends on machines capability of scheduling and how well the tasks are executed. Sometimes, it may require more time to complete. If we fail to fix the test we will take a hit on test coverage. I don't expect any noticeable flickering on userspace to happen, if we fail to complete tasks in one vblank. Seems that we are a bit too slow processing in one vblank, especially with the slower machines. It depends on machines capability of scheduling and how well the tasks are executed. Sometimes, it may require more time to complete. If we fail to fix the test we will take a hit on test coverage. I don't expect any noticeable flickering on userspace to happen, if we fail to complete tasks in one vblank. Seems that we are a bit too slow processing in one vblank, especially with the slower machines. It depends on machines capability of scheduling and how well the tasks are executed. Sometimes, it may require more time to complete. If we fail to fix the test we will take a hit on test coverage. I don't expect any noticeable flickering on userspace to happen, if we fail to complete tasks in one vblank. According to Mika, no user impact. (In reply to Mika Kahola from comment #61) > Seems that we are a bit too slow processing in one vblank, especially with > the slower machines. It depends on machines capability of scheduling and how > well the tasks are executed. Sometimes, it may require more time to complete. > > If we fail to fix the test we will take a hit on test coverage. I don't > expect any noticeable flickering on userspace to happen, if we fail to > complete tasks in one vblank. Have you checked that they always fail by 1? (In reply to Martin Peres from comment #63) > (In reply to Mika Kahola from comment #61) > > Seems that we are a bit too slow processing in one vblank, especially with > > the slower machines. It depends on machines capability of scheduling and how > > well the tasks are executed. Sometimes, it may require more time to complete. > > > > If we fail to fix the test we will take a hit on test coverage. I don't > > expect any noticeable flickering on userspace to happen, if we fail to > > complete tasks in one vblank. > > Have you checked that they always fail by 1? I went through the last 2 weeks and the only other delta I could find is this: https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_252/fi-snb-2520m/igt@kms_flip@plain-flip-ts-check-interruptible.html with is 4 vblanks, so no, not always by 1. Maybe we could still relax the test a bit, let's say accept the fact that we may have +2 vblanks until completion of the test. A CI Bug Log filter associated to this bug has been updated: {- all machines: Failed assertion: es->current_seq == es->last_seq + o->seq_step -} {+ all machines: fail/dmesg-fail - Failed assertion: es->current_seq == es->last_seq + o->seq_step +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_406/fi-skl-6770hq/igt@kms_flip@plain-flip-fb-recreate.html -- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/34. |
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.