Summary: | [CI] igt@kms_cursor_legacy@2x-long-flip-vs-cursor-* - fail - Test assertion failure function two_screens_flip_vs_cursor - Failed assertion: vbl.sequence == vblank_start + 1 | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | DRI | Reporter: | Marta Löfstedt <marta.lofstedt> | ||||||
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 | ||||||
Version: | XOrg git | ||||||||
Hardware: | Other | ||||||||
OS: | All | ||||||||
Whiteboard: | ReadyForDev | ||||||||
i915 platform: | CFL, CNL, HSW, I965G, ICL, ILK, SKL | i915 features: | display/Other | ||||||
Attachments: |
|
Description
Marta Löfstedt
2018-01-31 07:57:55 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4210/shard-hsw1/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html (kms_cursor_legacy:7786) CRITICAL: Test assertion failure function two_screens_flip_vs_cursor, file kms_cursor_legacy.c:976: (kms_cursor_legacy:7786) CRITICAL: Failed assertion: vbl.sequence == vblank_start + 1 (kms_cursor_legacy:7786) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_cursor_legacy:7786) CRITICAL: error: 31890 != 31889 Subtest 2x-long-flip-vs-cursor-atomic failed. This tests has failing on CNL QA Tests List: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy output sample: . . . (kms_cursor_legacy:834) CRITICAL: Test assertion failure function two_screens_flip_vs_cursor, file kms_cursor_legacy.c:976: (kms_cursor_legacy:834) CRITICAL: Failed assertion: vbl.sequence == vblank_start + 1 (kms_cursor_legacy:834) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_cursor_legacy:834) CRITICAL: error: 364 != 363 (kms_cursor_legacy:834) igt-core-INFO: Stack trace: (kms_cursor_legacy:834) igt-core-INFO: #0 [__igt_fail_assert+0x101] (kms_cursor_legacy:834) igt-core-INFO: #1 [two_screens_flip_vs_cursor+0x85c] (kms_cursor_legacy:834) igt-core-INFO: #2 [<unknown>+0x85c] . . . software: IGT-Version: 1.21-g68fb759 (x86_64) (Linux: 4.16.0-rc4-drm-intel-qa-ww10-commit-a994c52+ x86_64) Created attachment 137831 [details]
kernel log (CNL QA)
Created attachment 137832 [details]
dmesg -w (CNL QA)
Interesting, now also on 2X machine CFL-s2 https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3903/fi-cfl-s2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html (kms_cursor_legacy:1984) CRITICAL: Test assertion failure function two_screens_flip_vs_cursor, file kms_cursor_legacy.c:976: (kms_cursor_legacy:1984) CRITICAL: Failed assertion: vbl.sequence == vblank_start + 1 (kms_cursor_legacy:1984) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_cursor_legacy:1984) CRITICAL: error: 6793 != 6792 Subtest 2x-long-flip-vs-cursor-legacy failed. This tests was failing on CNL QA Test list: igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic output sample: . . . (kms_cursor_legacy:1570) CRITICAL: Test assertion failure function two_screens_flip_vs_cursor, file kms_cursor_legacy.c:976: (kms_cursor_legacy:1570) CRITICAL: Failed assertion: vbl.sequence == vblank_start + 1 (kms_cursor_legacy:1570) CRITICAL: error: 6796 != 6795 Subtest 2x-long-flip-vs-cursor-atomic failed. . . . software: IGT-Version: 1.22-g2ef96ec (x86_64) (Linux: 4.16.0-rc7-drm-tip-ww15-commit-d123888+ x86_64) https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_18/fi-cfl-s3/igt@kms_cursor_legacy@2x-flip-vs-cursor-atomic.html (kms_cursor_legacy:3181) CRITICAL: Test assertion failure function two_screens_flip_vs_cursor, file ../tests/kms_cursor_legacy.c:976: (kms_cursor_legacy:3181) CRITICAL: Failed assertion: vbl.sequence == vblank_start + 1 (kms_cursor_legacy:3181) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_cursor_legacy:3181) CRITICAL: error: 13435 != 13434 Subtest 2x-flip-vs-cursor-atomic failed. https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_42/fi-skl-6770hq/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html (kms_cursor_legacy:1796) CRITICAL: Test assertion failure function two_screens_flip_vs_cursor, file ../tests/kms_cursor_legacy.c:976: (kms_cursor_legacy:1796) CRITICAL: Failed assertion: vbl.sequence == vblank_start + 1 (kms_cursor_legacy:1796) CRITICAL: Last errno: 25, Inappropriate ioctl for device (kms_cursor_legacy:1796) CRITICAL: error: 12435 != 12434 Subtest 2x-long-flip-vs-cursor-atomic failed. A CI Bug Log filter associated to this bug has been updated: {- HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 -} {+ ILK HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_179/fi-ilk-650/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.html A CI Bug Log filter associated to this bug has been updated: {- ILK HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 -} {+ ILK, HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 +} No new failures caught with the new filter A CI Bug Log filter associated to this bug has been updated: {- ILK, HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 -} {+ ILK, HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_198/fi-icl-u2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html A CI Bug Log filter associated to this bug has been updated: {- ILK, HSW,SKL,KBL,GLK,CFL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 -} {+ ILK, HSW,SKL,KBL,GLK,CFL, ICL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 +} No new failures caught with the new filter Also seen on ICL https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_198/fi-icl-u2/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-atomic.html A CI Bug Log filter associated to this bug has been updated: {- ILK, HSW,SKL,KBL,GLK,CFL, ICL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 -} {+ BWR, ILK, HSW,SKL,KBL,GLK,CFL, ICL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_248/fi-bwr-2160/igt@kms_cursor_legacy@2x-long-flip-vs-cursor-legacy.html From Maarten: We try to make sure that when we do a page flip on a different screen, the cursor update is still simultaneous. What happens here is that we are probably too strict and sometimes miss a pageflip and it then takes 2 vblanks. This can happen in userspace too. I wouldn't say this has a high impact. It's very likely that disabling all power saving features would result in not seeing this bug, because a source of random delays is removed. A CI Bug Log filter associated to this bug has been updated: {- BWR, ILK, HSW,SKL,KBL,GLK,CFL, ICL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 -} {+ BWR, ILK, HSW,SKL,KBL,GLK,CFL, CML, ICL: igt@kms_cursor_legacy@2x-(long-)flip-vs-cursor-* - Failed assertion: vbl.sequence == vblank_start + 1 +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_328/fi-cml-u2/igt@kms_cursor_legacy@2x-flip-vs-cursor-legacy.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/72. |
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.