<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Regression - system fails to boot with Link Rate Fallback" href="https://bugs.freedesktop.org/show_bug.cgi?id=105338#c14">Comment # 14</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Regression - system fails to boot with Link Rate Fallback" href="https://bugs.freedesktop.org/show_bug.cgi?id=105338">bug 105338</a> from <a class="email" href="mailto:manasi.d.navare@intel.com" title="Manasi <manasi.d.navare@intel.com>"> Manasi</a> <pre>Looking at the logs, it looks like on boot the optimum values of link parameters are link rate = 27000 and lane count = 2 but with these it fails in clock recovery phase after 5 retries. That is why you see the debug message "Link training failed" but then it still recovers and brings up the display after enabling the pipe. It is probably one of those panels that do not handle the voltage swing values according to the spec and link training fails but we still have the display. Jani, looks like the hack of retrying clock recovery 5 times and then giving up needs to be added back which was removed during the compliance efforts. I can give a test patch that adds these retries before declaring Link failure. What are your thoughts here? Manasi</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are on the CC list for the bug.</li> </ul> </body> </html>