Summary: | [CI] igt@kms_flip@plain-flip-fb-recreate failed assertion: ev.sequence == last_seq + 1 | ||
---|---|---|---|
Product: | DRI | Reporter: | Jani Saarinen <jani.saarinen> |
Component: | DRM/Intel | Assignee: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Status: | CLOSED DUPLICATE | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | major | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | x86-64 (AMD64) | ||
OS: | Linux (All) | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | HSW | i915 features: | display/Other |
Description
Jani Saarinen
2017-09-01 06:19:16 UTC
Similar seen on https://bugs.freedesktop.org/show_bug.cgi?id=101599 Note: from CI_DRM_3287 to so far, CI_DRM_3292 APL- and GLK-shards failed this tests. either: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3287/shard-apl8/igt@kms_flip@plain-flip-fb-recreate.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3289/shard-glkb3/igt@kms_flip@plain-flip-fb-recreate.html (kms_flip:3816) CRITICAL: Test assertion failure function check_state, file kms_flip.c:536: (kms_flip:3816) CRITICAL: Failed assertion: es->current_seq == es->last_seq + o->seq_step (kms_flip:3816) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_flip:3816) CRITICAL: unexpected flip seq 45150, expected 45149 Subtest plain-flip-fb-recreate failed. or: https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3291/shard-apl4/igt@kms_flip@plain-flip-fb-recreate.html https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3287/shard-glkb5/igt@kms_flip@plain-flip-fb-recreate.html (kms_flip:3783) CRITICAL: Test assertion failure function calibrate_ts, file kms_flip.c:1200: (kms_flip:3783) CRITICAL: Failed assertion: ev.sequence == last_seq + 1 (kms_flip:3783) CRITICAL: error: 31938 != 31937 Subtest plain-flip-fb-recreate failed. Also, the es->current_seq == es->last_seq + o->seq_step is filed on bug 100368. I will duplicate to that one. *** 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.