Also,

(kms_vblank:1467) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:201:
(kms_vblank:1467) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:1467) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:1467) CRITICAL: error: 12132 != 12129
Subtest accuracy-idle failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3222/shard-apl4/igt@kms_vblank@accuracy-idle.html

Also, CI_DRM_3295 GLK-shards:

(kms_vblank:9829) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:201:
(kms_vblank:9829) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:9829) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:9829) CRITICAL: error: 1378 != 1376
Subtest accuracy-idle failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3295/shard-glkb4/igt@kms_vblank@accuracy-idle.html

Above link are dead, but this issue is still happening:
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3609/shard-kbl7/igt@kms_vblank@accuracy-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3542/shard-apl1/igt@kms_vblank@accuracy-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3542/shard-glkb6/igt@kms_vblank@accuracy-idle.html

HSW was long time ago:
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4051/shard-hsw2/igt@kms_vblank@accuracy-idle.html

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4208/shard-apl7/igt@kms_vblank@pipe-a-accuracy-idle.html
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4208/shard-glkb6/igt@kms_vblank@pipe-a-accuracy-idle.html

	
(kms_vblank:2679) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:250:
(kms_vblank:2679) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:2679) CRITICAL: Last errno: 25, Inappropriate ioctl for device

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4214/shard-hsw1/igt@kms_vblank@pipe-c-accuracy-idle.html

(kms_vblank:4662) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:250:
(kms_vblank:4662) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:4662) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:4662) CRITICAL: error: 4384 != 4382
Subtest pipe-C-accuracy-idle failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3751/shard-snb2/igt@kms_vblank@pipe-b-accuracy-idle.html

(kms_vblank:2022) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:255:
(kms_vblank:2022) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:2022) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:2022) CRITICAL: error: 458 != 457
Subtest pipe-B-accuracy-idle failed.

https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4232/shard-apl6/igt@kms_vblank@pipe-b-accuracy-idle.html

(kms_vblank:3015) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:255:
(kms_vblank:3015) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:3015) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:3015) CRITICAL: error: 661 != 658
Subtest pipe-B-accuracy-idle failed.

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_11/fi-skl-guc/igt@kms_vblank@pipe-a-accuracy-idle.html

(kms_vblank:4062) CRITICAL: Test assertion failure function accuracy, file ../tests/kms_vblank.c:255:
(kms_vblank:4062) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:4062) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:4062) CRITICAL: error: 10058 != 10057
Subtest pipe-A-accuracy-idle failed.

Bug was quite reproducible 10 months ago. Something has changed back then and after that we have seen it very few times (about once every 100 runs).

The issue was last seen 4 months ago.

We can close it when we hit CI_DRM_5949 without hitting it again (10*100 = 1000 runs since the last occurrence).

(In reply to Arek Hiler from comment #8)
> Bug was quite reproducible 10 months ago. Something has changed back then
> and after that we have seen it very few times (about once every 100 runs).
> 
> The issue was last seen 4 months ago.
> 
> We can close it when we hit CI_DRM_5949 without hitting it again (10*100 =
> 1000 runs since the last occurrence).

This is appearing again and failed couple of times during this week on BSW/GLK.

Seeting the priority to low based on Ankit's assessment.
Assessment:
Reproducible : 1-2% From recent history the test is passing for the mentioned platforms, The issue seems to be very rare.
Impact : Low. There is only 1 vblank mismatch in most of the cases.
Fdo bug : https://bugs.freedesktop.org/show_bug.cgi?id=102583

What does the sub-test do:
the test accuracy idle, tests the accuracy of the vblank events received by the userspace.
The test sets a target of say 'n' vblanks and gets the absolute sequence of the current vblank say 'x'.
Theoretically after 'n' vblanks, we should get the 'n' th vblank's absolute sequence no. as (n + x).

The issue:
The cases that fail, though rare, have the actual absolute vblank sequence no. (received after 'n' vblanks) more than the expected value.

-- 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/43.