https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@lic.html <3> [337.615696] [drm:_intel_hdcp_enable [i915]] *ERROR* Could not load HDCP keys, (-6)
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * TGL: igt@kms_content_protection@* - dmesg-fail - *ERROR* Could not load HDCP keys - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@lic.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@uevent.html
A CI Bug Log filter associated to this bug has been updated: {- TGL: igt@kms_content_protection@* - dmesg-fail - *ERROR* Could not load HDCP keys -} {+ TGL: igt@kms_content_protection@* - dmesg-fail - Failed assertion: ret, Content Protection not enabled +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@mei_interface.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@type1.html
https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_7058/re-tgl1-display/igt@kms_content_protection@type1.html Starting subtest: type1 (kms_content_protection:1081) CRITICAL: Test assertion failure function test_cp_enable_with_retry, file ../tests/kms_content_protection.c:404: (kms_content_protection:1081) CRITICAL: Failed assertion: ret (kms_content_protection:1081) CRITICAL: Content Protection not enabled Subtest type1 failed.
Could it be now HDCP supported monitors ?
-- 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/514.
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.