<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - i915:No display with Display port [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up" href="https://bugs.freedesktop.org/show_bug.cgi?id=90963#c16">Comment # 16</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - i915:No display with Display port [drm:intel_dp_start_link_train] *ERROR* too many full retries, give up" href="https://bugs.freedesktop.org/show_bug.cgi?id=90963">bug 90963</a> from <a class="email" href="mailto:eong.chen@gmail.com" title="Eong Chen <eong.chen@gmail.com>"> Eong Chen</a> <pre>(In reply to Ander Conselvan de Oliveira from <a href="show_bug.cgi?id=90963#c14">comment #14</a>) > Created <a href="attachment.cgi?id=119060" name="attach_119060" title="Fallback to lower link rate on MST link training">attachment 119060</a> <a href="attachment.cgi?id=119060&action=edit" title="Fallback to lower link rate on MST link training">[details]</a> <a href='page.cgi?id=splinter.html&bug=90963&attachment=119060'>[review]</a> [review] > Fallback to lower link rate on MST link training > > Could you run a kernel with this patch and attach dmesg with debug from boot? > > One difference between the link training in SST vs MST mode is that MST uses > the highest rate, while in SST we try the lowest rate that supports the > mode. The DP standard requires the source device to fallback to a lower rate > if link training fails, but our code doesn't do that. Tested it, please check the latest attached file.</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> <li>You are the assignee for the bug.</li> </ul> </body> </html>