<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][SKL] WARNING: no modes for connector 48 when running igt@kms_setmode@basic-clone-single-crtc" href="https://bugs.freedesktop.org/show_bug.cgi?id=101518#c9">Comment # 9</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [BAT][SKL] WARNING: no modes for connector 48 when running igt@kms_setmode@basic-clone-single-crtc" href="https://bugs.freedesktop.org/show_bug.cgi?id=101518">bug 101518</a> from <a class="email" href="mailto:martin.peres@free.fr" title="Martin Peres <martin.peres@free.fr>"> Martin Peres</a> <pre>(In reply to Manasi from <a href="show_bug.cgi?id=101518#c8">comment #8</a>) > I see the old logs, do you have the dmesg logs for the most recent testing > after the T12 delay fix patch went in. > Do we still see AUX timeouts? Like I mentioned, the problem here is those > aux timeouts. We should not have those since for an eDP panel we should > never fail link training. These aux timeouts are putting the system in an > unexpected state. Sure, it should not happen, but the failure mode taken is also wrong. Why are we pruning the mode when we are failing the enable the link training? It should only prune a mode if it failed to perform the actual link training. You still need to send the hotplug even though, to ask the userspace to re-do the modeset. And also, we should NEVER prune the last mode. It is not a problem on DP, but it is on eDP. The quickest fix would be to never prune modes on eDP since there is only one mode anyway.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> </ul> </body> </html>