Starting subtest: dp-crc-multiple (kms_chamelium:1203) igt_chamelium-CRITICAL: Test assertion failure function chamelium_rpc, file ../lib/igt_chamelium.c:306: (kms_chamelium:1203) igt_chamelium-CRITICAL: Failed assertion: !chamelium->env.fault_occurred (kms_chamelium:1203) igt_chamelium-CRITICAL: Chamelium RPC call failed: RPC failed at server. <class 'chameleond.devices.input_flow.InputFlowError'>:DP FSM failed
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_chamelium@dp-crc-multiple - dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5891/re-icl-u/igt@kms_chamelium@dp-crc-multiple.html
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_chamelium@dp-crc-multiple - dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed -} {+ ICL: igt@kms_chamelium@dp-crc-(fast|multiple) - fail / dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_5960/re-icl-u/igt@kms_chamelium@dp-crc-fast.html
This is quite likely test's fault. When the DP receiver on the chamelium side needs its Finite State Machine handling due to mode/configuration changes it signals that to us by sending hot-plug events. Then we need to do DPMS cycle. Current implementations spawns a thread monitoring for those events, but that seems to be prone to race conditions, and if we make XMLRPC call to chamelium before it is done we can get this error. We have to re-implement FSM handling at the call site, so whenever we get this error we force the handling (or wait till the handling is done). I have seen similar behavior on my local SKL too.
A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_chamelium@dp-crc-(fast|multiple) - fail / dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed -} {+ CML ICL: igt@kms_chamelium@dp-crc-(fast|multiple|single) - fail / dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_276/fi-cml-u2/igt@kms_chamelium@dp-crc-single.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_277/fi-cml-u2/igt@kms_chamelium@dp-crc-multiple.html
Hasn't been seen on ICL in 285 runs. Removing ICL from the affected platform list. CML hasn't seen this in 123 runs, will keep this open for CML to monitor for re-occurence
A CI Bug Log filter associated to this bug has been updated: {- CML ICL: igt@kms_chamelium@dp-crc-(fast|multiple|single) - fail / dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed -} {+ KBL CML ICL: igt@kms_chamelium@dp-crc-(fast|multiple|single) - fail / dmesg-fail - Chamelium RPC call failed: RPC failed at server.*:DP FSM failed +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_369/fi-kbl-7500u/igt@kms_chamelium@dp-audio.html
-- GitLab Migration Automatic Message -- This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/drm/intel/issues/262.
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.