Bug 107736

Summary: [CI][DRMTIP] igt@kms_cursor_legacy@basic-flip* - fail - Failed assertion: !(miss1 > 2 || miss1 + miss2 > 5)
Product: DRI Reporter: Martin Peres <martin.peres>
Component: DRM/IntelAssignee: Lakshmi <lakshminarayana.vudum>
Status: CLOSED WORKSFORME 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: CNL i915 features: display/PSR

Description Martin Peres 2018-08-29 11:40:01 UTC
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_95/fi-cnl-psr/igt@kms_cursor_legacy@basic-flip-before-cursor-atomic.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_94/fi-cnl-psr/igt@kms_cursor_legacy@basic-flip-after-cursor-varying-size.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_93/fi-cnl-psr/igt@kms_cursor_legacy@basic-flip-after-cursor-atomic.html

https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_92/fi-cnl-psr/igt@kms_cursor_legacy@basic-flip-before-cursor-varying-size.html

(kms_cursor_legacy:1583) CRITICAL: Test assertion failure function basic_flip_cursor, file ../tests/kms_cursor_legacy.c:608:
(kms_cursor_legacy:1583) CRITICAL: Failed assertion: !(miss1 > 2 || miss1 + miss2 > 5)
(kms_cursor_legacy:1583) CRITICAL: Failed to evade 0 vblanks and missed 25 page flips
Subtest basic-flip-before-cursor-varying-size failed.(km
Comment 2 Martin Peres 2019-07-02 10:07:02 UTC
Will close if we still don't get any reproduction at drmtip_338.
Comment 3 Lakshmi 2019-07-31 12:04:38 UTC
There are 4 failures seen on cnl and stopped at drmtip_95, later no new occurrences. In addition, there is one occurrence on CFL drmtip_174 (7 months, 2 weeks old). 

Closing this issue as WORKSFORME.
Comment 4 CI Bug Log 2019-07-31 12:05:01 UTC
The CI Bug Log issue associated to this bug has been archived.

New failures matching the above filters will not be associated to this bug anymore.

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.