Summary: | [CI][DRMTIP] igt@kms_content_protection@* - fail - Content Protection not enabled, Bksv is invalid | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Ramalingam C <ramalingam.c> |
Status: | RESOLVED NOTOURBUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | medium | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | ICL | i915 features: | display/HDCP |
Description
Martin Peres
2019-04-04 12:34:44 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * ICL: igt@kms_content_protection@* - fail - Content Protection not enabled, Bksv is invalid (No new failures associated) + Ram. Can you check if this is platform- or machine-specific? I'll update the filter based on your feedback. Martin, This is error log corresponding to an attached panel with invalid BKSV. We can't fix this from I915. HDCP sink connected to teh port provides the invalid BKSV. Hence HDCP authentication is expected to fail. This is not a bug in I915. Thanks. A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_content_protection@* - fail - Content Protection not enabled, Bksv is invalid -} {+ ICL: igt@kms_content_protection@* - fail - Content Protection not enabled, Bksv is invalid +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-icl-u3/igt@kms_content_protection@srm.html A CI Bug Log filter associated to this bug has been updated: {- ICL: igt@kms_content_protection@* - fail - Content Protection not enabled, Bksv is invalid -} {+ ICL: igt@kms_content_protection@* - fail - Content Protection not enabled, Bksv is invalid +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-icl-u3/igt@kms_content_protection@lic.html |
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.