<html>
<head>
<base href="https://bugs.freedesktop.org/">
</head>
<body><table border="1" cellspacing="0" cellpadding="8">
<tr>
<th>Bug ID</th>
<td><a class="bz_bug_link
bz_status_NEW "
title="NEW - [drm:intel_dp_link_training_clock_recovery] *ERROR* too many voltage retries, give up / failure to train DP"
href="https://bugs.freedesktop.org/show_bug.cgi?id=96436">96436</a>
</td>
</tr>
<tr>
<th>Summary</th>
<td>[drm:intel_dp_link_training_clock_recovery] *ERROR* too many voltage retries, give up / failure to train DP
</td>
</tr>
<tr>
<th>Product</th>
<td>DRI
</td>
</tr>
<tr>
<th>Version</th>
<td>unspecified
</td>
</tr>
<tr>
<th>Hardware</th>
<td>Other
</td>
</tr>
<tr>
<th>OS</th>
<td>All
</td>
</tr>
<tr>
<th>Status</th>
<td>NEW
</td>
</tr>
<tr>
<th>Severity</th>
<td>normal
</td>
</tr>
<tr>
<th>Priority</th>
<td>medium
</td>
</tr>
<tr>
<th>Component</th>
<td>DRM/Intel
</td>
</tr>
<tr>
<th>Assignee</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>Reporter</th>
<td>Martin@Lichtvoll.de
</td>
</tr>
<tr>
<th>QA Contact</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr>
<tr>
<th>CC</th>
<td>intel-gfx-bugs@lists.freedesktop.org
</td>
</tr></table>
<p>
<div>
<pre>I know there is <a class="bz_bug_link
bz_status_NEEDINFO "
title="NEEDINFO - [ivb cpu edp] clock recovery fails with too many full/voltage retries, channel equalization succeeds"
href="show_bug.cgi?id=70117">bug #70117</a>, yet, it is about issues with older kernels. This
issue started to happen with about kernel 4.5 (maybe 4.4, but I think it was
4.5), currently running 4.6 kernel. Also it seems to fail training the DP
completely in my case. Also <a class="bz_bug_link
bz_status_NEW "
title="NEW - [SNB/HSW] *ERROR* too many voltage retries, give up"
href="show_bug.cgi?id=83516">bug #83516</a>, <a class="bz_bug_link
bz_status_REOPENED "
title="REOPENED - i915: "too many retries" error when using an external monitor with HP EliteBook 820 G1"
href="show_bug.cgi?id=88919">bug #88919</a> <a class="bz_bug_link
bz_status_ASSIGNED "
title="ASSIGNED - eDP link clock recovery fails with *ERROR* too many full retries, give up"
href="show_bug.cgi?id=92878">bug #92878</a> and other
possibly related bugs are way older.
I basically get this:
[70574.696129] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.703576] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.711020] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.718444] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.725864] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.733275] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.740657] [drm:intel_dp_link_training_clock_recovery] *ERROR* too many
voltage retries, give up
[70574.740845] [drm:intel_dp_start_link_train] *ERROR* failed to train DP,
aborting
repeatedly.
This happens on a ThinkPad T520 with Sandybridge i5-2520M with one external
display at my home office, yet I never saw this with the display in my office
so far. It happens often on hibernating to disk with in kernel software
suspend, there it displays this message between every 10% progress upgrade on
saving the image to disk.
Now it happened also after resuming from hibernation. The external display was
not active and I found these messages looping in dmesg and the mousepointer
jerky in regular intervals.
I understand you may be interested in drm.debug=0xe, but it might take some
time till I can catch such an output, as its mostly happening on hibernation
the message and it doesn´t log this to disk at this stage. How much of an
performance impact does it have to run the kernel with that debug enabled for a
longer time during usual work?</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 the assignee for the bug.</li>
<li>You are on the CC list for the bug.</li>
</ul>
</body>
</html>