<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:ramalingam.c@intel.com" title="Ramalingam C <ramalingam.c@intel.com>"> <span class="fn">Ramalingam C</span></a>
</span> changed
<a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI][BAT] igt@* - dmesg-warn / dmesg-fail - KSV list failed to become ready"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108549">bug 108549</a>
<br>
<table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>What</th>
<th>Removed</th>
<th>Added</th>
</tr>
<tr>
<td style="text-align:right;">Assignee</td>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
<td>ramalingam.c@intel.com
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>ASSIGNED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI][BAT] igt@* - dmesg-warn / dmesg-fail - KSV list failed to become ready"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108549#c1">Comment # 1</a>
on <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - [CI][BAT] igt@* - dmesg-warn / dmesg-fail - KSV list failed to become ready"
href="https://bugs.freedesktop.org/show_bug.cgi?id=108549">bug 108549</a>
from <span class="vcard"><a class="email" href="mailto:ramalingam.c@intel.com" title="Ramalingam C <ramalingam.c@intel.com>"> <span class="fn">Ramalingam C</span></a>
</span></b>
<pre>This is the first time we have the kms_content_protection run on CI
effectively. And catching a bug at IGT.
As per the HDCP design at kernel, if content protection property is left at
DESIRED, then on subsequent modesets HDCP authentication will be attempted by
the kernel on its own.
In Our IGT when we set "content protection" to DESIRED and wait for ENABLED
state, on error case assert take us out of kms_content_protection, leaving the
"content protection" at DESIRED state.
To avoid HDCP authentication and related logs in subsequent tests we need to
fix this.
And another point is even within kms_content_protection, we don't want dmesg
errors incase of failure in authentication. So we need to cleanup all errors
the authentication flow by converting them into debug/info logs.
Will work on these solutions immediately. Thanks</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
<li>You are the QA Contact for the bug.</li>
</ul>
</body>
</html>