[CI][SHARDS] igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic - fail - Test assertion failure function igt_display_commit_atomic, Failed assertion: ret == 0, Last errno: 16, Device or resource busy
Submitted by Martin Peres @mupuf
Assigned to Intel GFX Bugs mailing list
Link to original bug (#107409)
Description
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4555/shard-glk9/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4554/shard-glk9/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html
(kms_cursor_legacy:2302) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3325:
(kms_cursor_legacy:2302) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_cursor_legacy:2302) igt_kms-CRITICAL: Last errno: 16, Device or resource busy
(kms_cursor_legacy:2302) igt_kms-CRITICAL: error: -16 != 0
Subtest 2x-nonblocking-modeset-vs-cursor-atomic failed.(km
Activity
added CI feature: display/atomic platform: GLK platform: KBL priority::low severity::normal + 1 deleted label
@mupufsaid:https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_4624/shard-glk9/igt@kms_atomic_transition@1x-modeset-transitions-nonblocking-fencing.html
(kms_atomic_transition:1240) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3325:
(kms_atomic_transition:1240) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_atomic_transition:1240) igt_kms-CRITICAL: Last errno: 16, Device or resource busy
(kms_atomic_transition:1240) igt_kms-CRITICAL: error: -16 != 0
Subtest 1x-modeset-transitions-nonblocking-fencing failed.@l4kshmisaid:Also seen on ICL
https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_158/fi-icl-u2/igt@kms_cursor_legacy@2x-nonblocking-modeset-vs-cursor-atomic.html
Starting subtest: 2x-nonblocking-modeset-vs-cursor-atomic
(kms_cursor_legacy:1066) igt_kms-CRITICAL: Test assertion failure function igt_display_commit_atomic, file ../lib/igt_kms.c:3395:
(kms_cursor_legacy:1066) igt_kms-CRITICAL: Failed assertion: ret == 0
(kms_cursor_legacy:1066) igt_kms-CRITICAL: Last errno: 16, Device or resource busy
(kms_cursor_legacy:1066) igt_kms-CRITICAL: error: -16 != 0
Subtest 2x-nonblocking-modeset-vs-cursor-atomic failed.A CI Bug Log filter associated to this bug has been updated:
{- GLK ICL: igt@nonblocking-modeset - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy -}
{+ GLK: igt@nonblocking-modeset - fail - Failed assertion: ret == 0, Last errno: 16, Device or resource busy +}
No new failures caught with the new filter@mupufsaid:(In reply to CI Bug Log from comment 4)
A CI Bug Log filter associated to this bug has been updated:
{- GLK ICL: igt@nonblocking-modeset - fail - Failed assertion: ret == 0,
Last errno: 16, Device or resource busy -}
{+ GLK: igt@nonblocking-modeset - fail - Failed assertion: ret == 0, Last
errno: 16, Device or resource busy +}
No new failures caught with the new filter
Dropping ICL since it was seen only once, 4 months ago, and the hardware and firmware versions have significantly changed since then.
As for the reproduction rate on GLK, this is only seen on shards, and multiple times per week (on average once every 12-15 runs) except for 2 weeks where it was not seen. The two affected tests are equally impacted, so nothing too interesting here.@adrinaelsaid:What the test is doing is nonblocking modesets on one crtc and nonblocking page flips on the cursor plane on another crtc. This can happen when we're moving the mouse around the screen and changing the image to react to the mouse context (text selection etc), and at the same time changing the resolution of another screen, hotplugging another monitor, ....
The failure here is getting EBUSY from the atomic commit, meaning the kernel had an earlier update pending.@mupufsaid:(In reply to Petri Latvala from comment 6)
What the test is doing is nonblocking modesets on one crtc and nonblocking
page flips on the cursor plane on another crtc. This can happen when we're
moving the mouse around the screen and changing the image to react to the
mouse context (text selection etc), and at the same time changing the
resolution of another screen, hotplugging another monitor, ....
The failure here is getting EBUSY from the atomic commit, meaning the kernel
had an earlier update pending.
Thanks, based on this and Maarten's assessment, I think we can agree that this is a low priority, especially since this is happening ONLY on GLK which is a low power device usually used only by tablets, IVI systems, ... which do not use a cursor :D
NUCs are the exception, but one does not usually change resolutions in a desktop PC.A CI Bug Log filter associated to this bug has been updated:
GLK igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic fail - Test assertion failure Last errno: 16, Device or resource busy
GLK KBL: igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic fail - Test assertion failure Last errno: 16, Device or resource busy
New failures caught by the filter:
Issue is not reproducing on GLK ,KBL and BSW .Last seen issue on drmtip_678 (1 month, 1 week old)
Hence closing the issue #133 (closed)
Edited by Tejasree Illipilli
A CI Bug Log filter associated to this bug has been updated by :
Description: GLK KBL: igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic fail - Test assertion failure Last errno: 16, Device or resource busy
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["fi-kbl-soraka", "shard-kbl3", "fi-glk-1", "shard-kbl5", "shard-kbl4", "shard-kbl7", "fi-bsw-n3050", "fi-glk-dsi", "fi-kbl-7500u", "shard-kbl6", "shard-kbl1", "fi-kbl-7560u", "fi-kbl-r", "fi-kbl-7567u", "shard-kbl2", "fi-glk-j4005", "shard-glk", "shard-kbl", "shard-glk1", "shard-glk3", "shard-glk4", "shard-glk5", "shard-glk2", "shard-glk8", "shard-glk6", "shard-glk7", "fi-kbl-guc", "fi-kbl-x1275", "shard-glk9", "fi-kbl-8809g"] OR machine_tag IS IN ["KBL", "GLK"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions", "igt@kms_cursor_legacy@2x-long-nonblocking-modeset-vs-cursor-atomic", "igt@kms_cursor_legacy@cursor-vs-flip-atomic-transitions-varying-size"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Test assertion failure function igt_display_commit_atomic.*\n.* Failed assertion: ret == 0'
New failures caught by the filter:
