Bug 103792 - [CI] igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions - fail - Test assertion failure function transition_nonblockingret == -EINVAL
Summary: [CI] igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions - fail...
Status: CLOSED WORKSFORME
Alias: None
Product: DRI
Classification: Unclassified
Component: DRM/Intel (show other bugs)
Version: DRI git
Hardware: Other All
: medium normal
Assignee: Intel GFX Bugs mailing list
QA Contact: Intel GFX Bugs mailing list
URL:
Whiteboard: ReadyForDev
Keywords:
Depends on:
Blocks:
 
Reported: 2017-11-17 12:19 UTC by Marta Löfstedt
Modified: 2018-03-09 10:52 UTC (History)
1 user (show)

See Also:
i915 platform: BXT, GLK
i915 features: display/Other

Attachments

Description Marta Löfstedt 2017-11-17 12:19:21 UTC 
CI_DRM_3356 APL-shards igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions

(kms_cursor_legacy:5525) CRITICAL: Test assertion failure function transition_nonblocking, file kms_cursor_legacy.c:322:
(kms_cursor_legacy:5525) CRITICAL: Failed assertion: ret == -EINVAL
(kms_cursor_legacy:5525) CRITICAL: Last errno: 16, Device or resource busy
Subtest short-flip-before-cursor-atomic-transitions failed.

https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_3356/shard-apl8/igt@kms_cursor_legacy@short-flip-before-cursor-atomic-transitions.html
Comment 1 Marta Löfstedt 2017-12-15 12:44:02 UTC 
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_4064/shard-glkb3/igt@kms_cursor_legacy@short-flip-after-cursor-atomic-transitions.html

(kms_cursor_legacy:1573) CRITICAL: Test assertion failure function transition_nonblocking, file kms_cursor_legacy.c:322:
(kms_cursor_legacy:1573) CRITICAL: Failed assertion: ret == -EINVAL
(kms_cursor_legacy:1573) CRITICAL: Last errno: 16, Device or resource busy
Subtest short-flip-after-cursor-atomic-transitions failed.
Comment 2 Marta Löfstedt 2018-03-09 10:52:36 UTC 
Last seen: CI_DRM_3736: 2018-02-08 / 253 runs ago

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.