Summary: | [CI][SHARDS] igt@kms_content_protection@* - fail - KSV list failed to become ready (-110) | ||
---|---|---|---|
Product: | DRI | Reporter: | Martin Peres <martin.peres> |
Component: | DRM/Intel | Assignee: | Ramalingam C <ramalingam.c> |
Status: | RESOLVED NOTABUG | QA Contact: | Intel GFX Bugs mailing list <intel-gfx-bugs> |
Severity: | normal | ||
Priority: | high | CC: | intel-gfx-bugs |
Version: | DRI git | ||
Hardware: | Other | ||
OS: | All | ||
Whiteboard: | ReadyForDev | ||
i915 platform: | BXT, CFL, KBL, SKL | i915 features: | display/HDCP |
Description
Martin Peres
2019-04-04 12:25:27 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * APL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) (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 debug log with failure will be observed when the connected repeater(LsPCON here) is not providing the KSV list in time. I915 can't fix this. *** Bug 110336 has been marked as a duplicate of this bug. *** This HDCP failure is caused due to the HDCP sink connected to the port. So this is not a bug in I915. Thanks The CI Bug Log issue associated to this bug has been updated. ### New filters associated * CFL: igt@kms_content_protection@atomic-dpms - incomplete - KSV list failed to become ready (-110) - https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cfl-8109u/igt@kms_content_protection@atomic-dpms.html (In reply to CI Bug Log from comment #6) > The CI Bug Log issue associated to this bug has been updated. > > ### New filters associated > > * CFL: igt@kms_content_protection@atomic-dpms - incomplete - KSV list failed > to become ready (-110) > - > https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_270/fi-cfl-8109u/ > igt@kms_content_protection@atomic-dpms.html Result here is incomplete but on CFL. A CI Bug Log filter associated to this bug has been updated: {- APL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) -} {+ APL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6431/shard-kbl2/igt@kms_content_protection@atomic.html The CI Bug Log issue associated to this bug has been updated. ### New filters associated * APL KBL: igt@kms_content_protection@(lic|srm) fail - Failed assertion: ret, Content Protection not enabled - https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13834/fi-apl-guc/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5123/shard-apl4/igt@kms_content_protection@lic.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5123/shard-apl6/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5123/shard-kbl1/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5123/shard-kbl3/igt@kms_content_protection@lic.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3263/fi-apl-guc/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3263/shard-apl7/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3263/shard-apl8/igt@kms_content_protection@lic.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3263/shard-kbl1/igt@kms_content_protection@srm.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGTPW_3263/shard-kbl4/igt@kms_content_protection@lic.html A CI Bug Log filter associated to this bug has been updated: {- APL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) -} {+ APL SKL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-skl-6770hq/igt@kms_content_protection@lic.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-skl-lmem/igt@kms_content_protection@lic.html A CI Bug Log filter associated to this bug has been updated: {- APL KBL: igt@kms_content_protection@(lic|srm) fail - Failed assertion: ret, Content Protection not enabled -} {+ APL KBL: igt@kms_content_protection@(lic|srm) fail - Failed assertion: ret, Content Protection not enabled +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-skl-gvtdvm/igt@kms_content_protection@srm.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-skl-lmem/igt@kms_content_protection@srm.html A CI Bug Log filter associated to this bug has been updated: {- APL KBL: igt@kms_content_protection@(lic|srm) fail - Failed assertion: ret, Content Protection not enabled -} {+ APL SKL KBL: igt@kms_content_protection@(lic|srm) fail - Failed assertion: ret, Content Protection not enabled +} No new failures caught with the new filter A CI Bug Log filter associated to this bug has been updated: {- APL SKL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) -} {+ APL SKL KBL: igt@kms_content_protection@* - fail - Content Protection not enabled, KSV list failed to become ready (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-cfl-8109u/igt@kms_content_protection@srm.html * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_338/fi-cfl-8109u/igt@kms_content_protection@lic.html A CI Bug Log filter associated to this bug has been updated: {- CFL: igt@kms_content_protection@atomic-dpms - incomplete - KSV list failed to become ready (-110) -} {+ SKL CFL: igt@kms_content_protection@atomic-dpms|igt@kms_content_protection@legacy - incomplete - KSV list failed to become ready (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/drmtip_387/fi-skl-6770hq/igt@kms_content_protection@legacy.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.