igt@kms_invalid_mode@clock-too-high@.* - fail - Failed assertion: output->pending_pipe != b->pending_pipe
Starting dynamic subtest: DP-4-pipe-A
(kms_invalid_mode:2113) igt_kms-CRITICAL: Test assertion failure function igt_display_refresh, file ../lib/igt_kms.c:2810:
(kms_invalid_mode:2113) igt_kms-CRITICAL: Failed assertion: output->pending_pipe != b->pending_pipe
(kms_invalid_mode:2113) igt_kms-CRITICAL: DP-4 and DP-1 are both trying to use pipe A
Dynamic subtest DP-4-pipe-A failed.Activity
added feature: display/Other platform: DG2 labels
The CI Bug Log issue associated to this bug has been updated by .
New filters associated
- DG2 : igt@kms_invalid_mode@clock-too-high@dp-4-pipe-[ac] - fail - Failed assertion: output->pending_pipe != b->pending_pipe
similar to #6198 (closed)
-
issue is observed on RPL_S manual resume run with DRM_11862 and IGT_6563, hence adding RPL_S platform tag.
RPL_S_DRM_11862_IGT_6563_igt_kms_invalid_mode_clock-too-high_dp-4-pipe-a_-_Details.html
added platform: RPL_S label
-
A CI Bug Log filter associated to this bug has been updated by :
Description: ICL DG2 : igt@kms_invalid_mode@clock-too-high@dp-4.-pipe-[ac]* - fail - Failed assertion: output->pending_pipe != b->pending_pipe
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["fi-icl-u2", "shard-iclb", "shard-iclb1", "shard-iclb2", "shard-iclb3", "shard-iclb4", "shard-iclb5", "shard-iclb6", "fi-icl-u3", "shard-iclb7", "fi-icl-y", "shard-iclb8", "fi-icl-guc", "fi-icl-dsi", "re-icl-u", "fi-icl-u4", "bat-dg2-8", "bat-dg2-9", "re-dg2-11", "re-dg2-12", "fi-icl-1065g7", "pig-icl-1065g7", "fi-icl-u"] OR machine_tag IS IN ["ICL", "DG2"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@kms_invalid_mode@clock-too-high", "igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-a", "igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-b", "igt@kms_invalid_mode@clock-too-high@dp-2-pipe-c", "igt@kms_invalid_mode@clock-too-high@dp-2-pipe-a", "igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-c", "igt@kms_invalid_mode@clock-too-high@dp-4-pipe-c", "igt@kms_invalid_mode@clock-too-high@dp-4-pipe-a", "igt@kms_invalid_mode@clock-too-high@dp-42-pipe-cb"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: output->pending_pipe != b->pending_pipe'
New failures caught by the filter:
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1162/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-a.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1162/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@dp-2-pipe-a.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1162/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-b.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1162/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@dp-2-pipe-b.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1162/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-c.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1162/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@dp-2-pipe-c.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1165/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-a.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1165/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@dp-2-pipe-a.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1165/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-b.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1165/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@dp-2-pipe-b.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1165/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-c.html
- https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_1165/fi-icl-u2/igt@kms_invalid_mode@clock-too-high@dp-2-pipe-c.html
added platform: ICL label
-
A CI Bug Log filter associated to this bug has been updated by :
Description: ADL_P ICL DG2 : igt@kms_invalid_mode@clock-too-high@.* - fail - Failed assertion: output->pending_pipe != b->pending_pipe
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND (machine_name IS IN ["re-adlp-pub3", "re-adlp-pub2", "re-adlp-5", "fi-icl-u2", "re-adlp-11", "bat-adlp-6", "shard-iclb", "shard-iclb1", "shard-iclb2", "shard-iclb3", "shard-iclb4", "shard-iclb5", "shard-iclb6", "fi-icl-u3", "shard-iclb7", "fi-icl-y", "shard-iclb8", "fi-icl-guc", "fi-icl-dsi", "re-icl-u", "fi-icl-u4", "bat-dg2-8", "bat-dg2-9", "re-dg2-11", "re-dg2-12", "fi-icl-1065g7", "pig-icl-1065g7", "bat-adlp-4", "re-adlp-pub1", "fi-icl-u"] OR machine_tag IS IN ["ICL", "DG2", "ADL-P"]) AND ((testsuite_name = "IGT" AND test_name IS IN ["igt@kms_invalid_mode@clock-too-high", "igt@kms_invalid_mode@clock-too-high@dp-5-pipe-b", "igt@kms_invalid_mode@clock-too-high@dp-5-pipe-d", "igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-a", "igt@kms_invalid_mode@clock-too-high@dp-5-pipe-c", "igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-b", "igt@kms_invalid_mode@clock-too-high@dp-2-pipe-c", "igt@kms_invalid_mode@clock-too-high@dp-2-pipe-a", "igt@kms_invalid_mode@clock-too-high@hdmi-a-2-pipe-c", "igt@kms_invalid_mode@clock-too-high@dp-4-pipe-c", "igt@kms_invalid_mode@clock-too-high@dp-4-pipe-a", "igt@kms_invalid_mode@clock-too-high@dp-5-pipe-a", "igt@kms_invalid_mode@clock-too-high@dp-2-pipe-b"])) AND ((testsuite_name = "IGT" AND status_name IS IN ["fail"])) AND stderr ~= 'Failed assertion: output->pending_pipe != b->pending_pipe'
New failures caught by the filter:
added platform: ADL_P label
This was happening on setups which have eDP as first display and also another external display connected.
The failure was happening because on eDP this test is an expected skip and as it is skipping on eDP the clean up part was also getting skipped. This left eDP still connected to the same pipe. When the second display tries to run on this pipe, we were getting this error as both the displays are trying to access the same pipe.
Fix patch is now merged. https://patchwork.freedesktop.org/series/106345/
The test is now passing successfully on all the systems it was hitting before.
