Bug 102583 - [CI] igt@kms_vblank@*-accuracy-idle - Failed assertion: vbl.reply.sequence == target
Summary: [CI] igt@kms_vblank@*-accuracy-idle - Failed assertion: vbl.reply.sequence ==...
Status: NEW
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: XOrg git
Hardware: Other All
: low normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-07 12:09 UTC by Martin Peres
Modified: 2019-08-06 10:37 UTC (History)
2 users (show)

See Also:
i915 platform: ALL
i915 features: display/Other


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Martin Peres 2017-09-07 12:09:16 UTC
On CI_DRM_3048, the machine shard-hsw hit the following assert when running igt@kms_vblank@accuracy-idle:

(kms_vblank:1685) CRITICAL: Test assertion failure function accuracy, file kms_vblank.c:201:
(kms_vblank:1685) CRITICAL: Failed assertion: vbl.reply.sequence == target
(kms_vblank:1685) CRITICAL: Last errno: 25, Inappropriate ioctl for device
(kms_vblank:1685) CRITICAL: error: 716 != 715

Full logs: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3048/shard-hsw6/igt@kms_vblank@accuracy-idle.html
Comment 1 Marta Löfstedt 2017-10-12 11:30:07 UTC
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
Comment 2 Marta Löfstedt 2017-10-31 09:01:29 UTC
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
Comment 4 Marta Löfstedt 2018-02-01 11:07:20 UTC
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
Comment 5 Marta Löfstedt 2018-02-05 07:06:19 UTC
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.
Comment 6 Marta Löfstedt 2018-02-12 08:03:42 UTC
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.
Comment 7 Marta Löfstedt 2018-04-03 12:24:39 UTC
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.
Comment 8 Arek Hiler 2019-04-04 11:15:57 UTC
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).
Comment 9 Lakshmi 2019-05-31 11:54:51 UTC
(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.
Comment 10 Lakshmi 2019-08-06 10:37:09 UTC
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.


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.