Due to an influx of spam, we have had to impose restrictions on new accounts. Please see this wiki page for instructions on how to get full permissions. Sorry for the inconvenience.
Few KMS Testcases - dmesg-warn/dmesg-fail/incomplete - *ERROR* Step 2 of creating MST payload for ffff888.* failed: -5
The error probably means that the monitor disconnected itself and the corresponding MST port was removed from the MST topology, hence the MST communication during the modesetting of this monitor will fail (MST port is not found). One thing to check if the whole modeset should fail already earlier, similarly to modesets trying to enable an already removed MST connector.
A CI Bug Log filter associated to this bug has been updated by Gundlakarthik.
Description: TGL ADL_P: Few KMS Testcases - dmesg-warn/dmesg-fail/incomplete - *ERROR* Step 2 of creating MST payload for ffff888.* failed: -5
Equivalent query: runconfig_tag IS IN ["DRM-TIP"] AND machine_tag IS IN ["TGL", "ADL-P"] AND ((testsuite_name = "IGT" AND status_name IS IN ["incomplete", "abort", "dmesg-warn", "dmesg-fail"])) AND dmesg ~= '\*ERROR\* Step 2 of creating MST payload for ffff888.* failed: -5'
This issue is one year old, we should be tracking issues with displays connection actively using new bug for any new issue. Yesterday #9824 (closed) was closed and board was checked and issues resolved. Let's close this bug and submit new one for any new attempt of failure.