<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><span class="vcard"><a class="email" href="mailto:paul.kocialkowski@linux.intel.com" title="Paul Kocialkowski <paul.kocialkowski@linux.intel.com>"> <span class="fn">Paul Kocialkowski</span></a>
</span> changed
<a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [IGT][SKL] Failed to enable DP link training on resume when testing with Chamelium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101815">bug 101815</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;">Resolution</td>
<td>---
</td>
<td>NOTABUG
</td>
</tr>
<tr>
<td style="text-align:right;">Status</td>
<td>NEW
</td>
<td>RESOLVED
</td>
</tr></table>
<p>
<div>
<b><a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [IGT][SKL] Failed to enable DP link training on resume when testing with Chamelium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101815#c2">Comment # 2</a>
on <a class="bz_bug_link
bz_status_RESOLVED bz_closed"
title="RESOLVED NOTABUG - [IGT][SKL] Failed to enable DP link training on resume when testing with Chamelium"
href="https://bugs.freedesktop.org/show_bug.cgi?id=101815">bug 101815</a>
from <span class="vcard"><a class="email" href="mailto:paul.kocialkowski@linux.intel.com" title="Paul Kocialkowski <paul.kocialkowski@linux.intel.com>"> <span class="fn">Paul Kocialkowski</span></a>
</span></b>
<pre>This issue is actually not related to the DP connector that is connected to the
Chamelium but to another DP connector that has a DP-VGA bridge attached. The
bridge is taking a while to get back up after resume and thus causes the AUX
channel timeouts. After a while (a second or two), it gets back up and i915
properly handles it, so I don't think there's an issue here.
The reason why I reported this was that the link training failure generates a
uevent that is mistakenly taken as the one resulting from the thing we want to
test (either hpd or edid change). There's no problem affecting end users aside
of that.
However, I noticed that the connector name is not printed on the
link-training-failure-related messages, so I will craft a simple patch adding
the connector name to the messages, to avoid similar confusion in the future.
Closing the issue for now since the issue is on the bridge's side and i915
already handles it like a champ'.</pre>
</div>
</p>
<hr>
<span>You are receiving this mail because:</span>
<ul>
<li>You are the QA Contact for the bug.</li>
<li>You are on the CC list for the bug.</li>
<li>You are the assignee for the bug.</li>
</ul>
</body>
</html>