Summary: | [CI][SHARDS] igt@gem_tiled_swapping@non-threaded - dmesg-warn - *ERROR* Failed to enable hdcp (-110) | ||
---|---|---|---|
Product: | DRI | Reporter: | Lakshmi <lakshminarayana.vudum> |
Component: | DRM/Intel | Assignee: | Anshuman Gupta <anshuman.gupta> |
Status: | RESOLVED MOVED | 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: | |||
i915 platform: | BXT, KBL | i915 features: | display/Other |
Description
Lakshmi
2019-08-07 12:36:49 UTC
The CI Bug Log issue associated to this bug has been updated. ### New filters associated * APL KBL: igt@gem_tiled_swapping@non-threaded - dmesg-warn - *ERROR* Failed to enable hdcp (-110) - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5124/shard-apl3/igt@gem_tiled_swapping@non-threaded.html - https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5124/shard-kbl7/igt@gem_tiled_swapping@non-threaded.html A CI Bug Log filter associated to this bug has been updated: {- APL KBL: igt@gem_tiled_swapping@non-threaded - dmesg-warn - *ERROR* Failed to enable hdcp (-110) -} {+ APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6643/shard-apl6/igt@kms_cursor_crc@pipe-b-cursor-suspend.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6643/shard-kbl7/igt@kms_sequence@get-forked-busy.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6643/shard-kbl7/igt@kms_cursor_edge_walk@pipe-b-64x64-top-edge.html Another instance: https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13923/shard-apl7/igt@prime_busy@wait-hang-blt.html Seems to happen on MC2800 LSPCON outputs (both on KBL and APL). Lakshmi, could you update the bug filter to catch this error regardless of the test (I suspect it's not related to GEM). A CI Bug Log filter associated to this bug has been updated: {- APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) -} {+ APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6651/shard-apl7/igt@kms_flip@basic-flip-vs-wf_vblank.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6655/shard-apl6/igt@prime_busy@wait-hang-blt.html * https://intel-gfx-ci.01.org/tree/drm-tip/CI_DRM_6657/shard-apl4/igt@kms_flip@basic-flip-vs-wf_vblank.html (In reply to Imre Deak from comment #3) > Another instance: > https://intel-gfx-ci.01.org/tree/drm-tip/Patchwork_13923/shard-apl7/ > igt@prime_busy@wait-hang-blt.html > > Seems to happen on MC2800 LSPCON outputs (both on KBL and APL). > > Lakshmi, could you update the bug filter to catch this error regardless of > the test (I suspect it's not related to GEM) Yes, filter is updated. A CI Bug Log filter associated to this bug has been updated: {- APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) -} {+ APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5150/shard-apl7/igt@kms_busy@basic-flip-b.html * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5150/shard-kbl2/igt@kms_busy@basic-flip-b.html A CI Bug Log filter associated to this bug has been updated: {- APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) -} {+ APL KBL: random tests - dmesg-warn - *ERROR* Failed to enable hdcp (-110) +} New failures caught by the filter: * https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5165/shard-apl8/igt@kms_frontbuffer_tracking@fbc-1p-primscrn-spr-indfb-draw-pwrite.html Seems like we still have situations where hdcp remains enabled despite. Assigning Ramaling to have a look into it since he has been working on this already :) Better to have an exit handler on any igt_assert to reset the HDCP state on all connectors. Anshuman is working on it. Thanks. -- 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/359. |
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.