From: bugzilla-daemon@freedesktop.org
To: dri-devel@lists.freedesktop.org
Subject: [Bug 111390] [CI][SHARDS] igt@kms_* - dmesg-warn - KSV list failed to become ready (-110)
Date: Tue, 13 Aug 2019 07:09:18 +0000 [thread overview]
Message-ID: <bug-111390-502@http.bugs.freedesktop.org/> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1222 bytes --]
https://bugs.freedesktop.org/show_bug.cgi?id=111390
Bug ID: 111390
Summary: [CI][SHARDS] igt@kms_* - dmesg-warn - KSV list failed
to become ready (-110)
Product: DRI
Version: XOrg git
Hardware: Other
OS: All
Status: NEW
Severity: normal
Priority: medium
Component: IGT
Assignee: dri-devel@lists.freedesktop.org
Reporter: martin.peres@free.fr
It seems like we are attempting to use HDCP in tests that do not need content
protection:
https://intel-gfx-ci.01.org/tree/drm-tip/IGT_5128/shard-apl7/igt@kms_plane@plane-position-hole-dpms-pipe-b-planes.html
<7> [1747.235381] [drm:intel_hdcp_auth [i915]] KSV list failed to become ready
(-110)
<7> [1747.235601] [drm:_intel_hdcp_enable [i915]] HDCP Auth failure (-110)
<7> [1747.235754] [drm:_intel_hdcp_disable [i915]] [DP-1:100] HDCP is being
disabled...
<7> [1747.238782] [drm:_intel_hdcp_disable [i915]] HDCP is disabled
Please make sure HDCP is disabled in KMS tests which are not content-protection
related.
--
You are receiving this mail because:
You are the assignee for the bug.
[-- Attachment #1.2: Type: text/html, Size: 2706 bytes --]
[-- Attachment #2: Type: text/plain, Size: 159 bytes --]
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
reply other threads:[~2019-08-13 7:09 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=bug-111390-502@http.bugs.freedesktop.org/ \
--to=bugzilla-daemon@freedesktop.org \
--cc=dri-devel@lists.freedesktop.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox