Bug 100368

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/IntelAssignee: Intel GFX Bugs mailing list <intel-gfx-bugs>
Status: ASSIGNED --- 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 Flags
kernel log (comment 29) none

Description Martin Peres 2017-03-24 09:27:39 UTC
The machine fi-hsw-4770 produced a fail when running igt@kms_flip@basic-flip-vs-wf_vblank on CI_DRM_2392 and has not been seen for the past 3 runs.

Relevant hunk in the piglit logs:
(kms_flip:9026) DEBUG: flip ts/seq: last 328.003934/17103, current 328.187405/17114: elapsed=183471.0us expected=183473.8us +- 917.4us, error 0.0%
(kms_flip:9026) CRITICAL: Test assertion failure function check_state, file kms_flip.c:538:
(kms_flip:9026) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step
(kms_flip:9026) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_flip:9026) CRITICAL: unexpected flip seq 17114, expected 17113

Raw results: https://intel-gfx-ci.01.org/CI/CI_DRM_2392/fi-hsw-4770/igt@kms_flip@basic-flip-vs-wf_vblank.html
Comment 1 Martin Peres 2017-03-24 09:28:10 UTC
Selecting the platform and updating the importance.
Comment 2 Chris Wilson 2017-03-24 10:05:44 UTC
Note that the run this failed on was a KASAN test, i.e. the kernel was a bit slower than normal.
Comment 3 Martin Peres 2017-03-29 11:28:11 UTC
Dropping the priority, since it is only seen with KASAN. It needs to be fixed though!
Comment 4 Ricardo 2017-05-09 19:32:14 UTC
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
Comment 5 Elizabeth 2017-06-23 22:25:56 UTC
(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.
Comment 6 Jani Saarinen 2017-07-31 13:56:51 UTC
Elisabet, please note that that was seen on special KASAN build.
Comment 9 Martin Peres 2017-09-07 12:05:25 UTC
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
Comment 10 Jani Saarinen 2017-09-28 10:34:31 UTC
*** Bug 103005 has been marked as a duplicate of this bug. ***
Comment 12 Marta Löfstedt 2017-10-12 06:24:10 UTC
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
Comment 13 Marta Löfstedt 2017-10-12 07:39:01 UTC
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
Comment 16 Marta Löfstedt 2017-10-18 10:59:31 UTC
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
Comment 17 Marta Löfstedt 2017-10-26 05:54:53 UTC
*** Bug 102699 has been marked as a duplicate of this bug. ***
Comment 18 Marta Löfstedt 2017-10-27 07:28:37 UTC
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
Comment 19 Marta Löfstedt 2017-10-27 07:34:15 UTC
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
Comment 20 Marta Löfstedt 2017-10-27 07:35:11 UTC
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
Comment 21 Marta Löfstedt 2017-10-30 08:19:56 UTC
*** Bug 102504 has been marked as a duplicate of this bug. ***
Comment 22 Daniel Vetter 2017-11-08 13:32:46 UTC
Fixing the confusing title, it's for a lot more machines than just hsw.
Comment 23 Marta Löfstedt 2017-11-21 07:44:50 UTC
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.
Comment 25 Marta Löfstedt 2017-11-28 13:17:49 UTC
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.
Comment 26 Marta Löfstedt 2017-12-07 14:20:06 UTC
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.
Comment 27 Maarten Lankhorst 2017-12-11 17:15:15 UTC
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.
Comment 28 Marta Löfstedt 2017-12-12 06:41:00 UTC
(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.
Comment 29 Hector Velazquez 2017-12-28 22:21:56 UTC
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
Comment 30 Hector Velazquez 2017-12-28 22:25:17 UTC
Created attachment 136434 [details]
kernel log (comment 29)
Comment 31 Marta Löfstedt 2018-01-22 08:30:15 UTC
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.
Comment 32 Marta Löfstedt 2018-01-24 07:11:46 UTC
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.
Comment 33 Marta Löfstedt 2018-01-25 06:36:29 UTC
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.
Comment 34 Marta Löfstedt 2018-01-25 06:37:59 UTC
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.
Comment 35 Marta Löfstedt 2018-01-30 14:20:54 UTC
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.
Comment 36 Marta Löfstedt 2018-02-01 07:34:30 UTC
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.
Comment 37 Marta Löfstedt 2018-02-05 07:07:23 UTC
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.
Comment 38 Octavio 2018-02-07 20:50:09 UTC
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.
Comment 39 Marta Löfstedt 2018-02-08 12:17:05 UTC
fi-hsw-4770r impact removed since we don't have data links for any reproduction from that machine anymore
Comment 40 Marta Löfstedt 2018-02-09 06:22:20 UTC
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.
Comment 41 Marta Löfstedt 2018-02-12 08:19:02 UTC
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.
Comment 42 Marta Löfstedt 2018-02-13 07:17:15 UTC
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.
Comment 43 Martin Peres 2018-02-19 10:33:10 UTC
*** Bug 100369 has been marked as a duplicate of this bug. ***
Comment 44 Martin Peres 2018-02-19 10:34:13 UTC
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
Comment 45 Marta Löfstedt 2018-02-19 12:47:18 UTC
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.
Comment 46 Marta Löfstedt 2018-02-28 10:14:30 UTC
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.
Comment 47 Marta Löfstedt 2018-03-13 07:55:58 UTC
*** Bug 103928 has been marked as a duplicate of this bug. ***
Comment 48 Marta Löfstedt 2018-03-15 07:06:37 UTC
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.
Comment 49 Marta Löfstedt 2018-03-19 07:32:42 UTC
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.
Comment 50 Octavio 2018-03-21 20:26:42 UTC
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.
Comment 51 Marta Löfstedt 2018-03-23 09:08:00 UTC
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.
Comment 52 Marta Löfstedt 2018-03-27 05:37:53 UTC
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.
Comment 53 Marta Löfstedt 2018-03-29 07:04:23 UTC
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.
Comment 55 Martin Peres 2018-04-20 12:21:27 UTC
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.
Comment 56 Martin Peres 2018-06-05 11:53:51 UTC
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.
Comment 57 Lakshmi 2018-09-25 11:25:39 UTC
*** Bug 103004 has been marked as a duplicate of this bug. ***
Comment 58 CI Bug Log 2019-01-16 11:58:44 UTC
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
Comment 59 Mika Kahola 2019-04-15 13:13:51 UTC
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.
Comment 60 Mika Kahola 2019-04-15 13:14:06 UTC
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.
Comment 61 Mika Kahola 2019-04-15 13:14:16 UTC
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.
Comment 62 Lakshmi 2019-04-15 13:16:32 UTC
According to Mika, no user impact.
Comment 63 Martin Peres 2019-04-15 13:17:36 UTC
(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?
Comment 64 Arek Hiler 2019-04-15 13:33:40 UTC
(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.
Comment 65 Mika Kahola 2019-04-17 08:19:05 UTC
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.

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.