https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_315/fi-icl-u3/igt@kms_content_protection@atomic.html Starting subtest: atomic (kms_content_protection:1893) CRITICAL: Test assertion failure function test_cp_enable_with_retry, file ../tests/kms_content_protection.c:219: (kms_content_protection:1893) CRITICAL: Failed assertion: ret (kms_content_protection:1893) CRITICAL: Content Protection not enabled Subtest atomic failed.
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_content_protection@* - fail - Failed assertion: ret, Content Protection not enabled - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_313/fi-icl-u3/igt@kms_content_protection@legacy.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_313/fi-icl-u3/igt@kms_content_protection@atomic.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_313/fi-icl-u3/igt@kms_content_protection@atomic-dpms.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_314/fi-icl-u3/igt@kms_content_protection@legacy.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_314/fi-icl-u3/igt@kms_content_protection@atomic.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_314/fi-icl-u3/igt@kms_content_protection@atomic-dpms.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_315/fi-icl-u3/igt@kms_content_protection@legacy.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_315/fi-icl-u3/igt@kms_content_protection@atomic.html - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_315/fi-icl-u3/igt@kms_content_protection@atomic-dpms.html
As per https://patchwork.freedesktop.org/series/63023/ this issue is caused because device connected at DP port declared itself as a repeater with zero HDCP sinks connected to it. So I915 is reacting as it supposed to be by failing the HDCP authentication. So not an I915 Bug. To capture this root cause in the debug log new change is submitted at https://patchwork.freedesktop.org/series/63217/. Will be merged when the review is completed.
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.