<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - system freezes during boot, [drm:intel_dp_start_link_train [i915]] and [drm:intel_psr_work [i915]] ERROR" href="https://bugs.freedesktop.org/show_bug.cgi?id=96569#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_ASSIGNED " title="ASSIGNED - system freezes during boot, [drm:intel_dp_start_link_train [i915]] and [drm:intel_psr_work [i915]] ERROR" href="https://bugs.freedesktop.org/show_bug.cgi?id=96569">bug 96569</a> from <a class="email" href="mailto:conselvan2@gmail.com" title="Ander Conselvan de Oliveira <conselvan2@gmail.com>"> Ander Conselvan de Oliveira</a> <pre>(In reply to Robin Krahl from <a href="show_bug.cgi?id=96569#c3">comment #3</a>) > (In reply to Ander Conselvan de Oliveira from <a href="show_bug.cgi?id=96569#c2">comment #2</a>) > > Created <a href="attachment.cgi?id=125056" name="attach_125056" title="Workaround: don't retrain the link from long pulse">attachment 125056</a> <a href="attachment.cgi?id=125056&action=edit" title="Workaround: don't retrain the link from long pulse">[details]</a> <a href='page.cgi?id=splinter.html&bug=96569&attachment=125056'>[review]</a> [review] [review] > > Workaround: don't retrain the link from long pulse > > > > […] > > > > I'm not sure what the proper fix would be, but the attached patch would > > confirm that's the issue. > > Thanks! Unfortunately the patch (applied against v4.7-rc1) does not solve > the problem in the original setup. > > But I found out by accident that apparently the system does not actually > freeze, it’s just the internal monitor that is not updated. If I connect an > external monitor, I can login and work (though the tty is flooded with the > time out errors). > > Should I provide logs from the patched kernel, or test whether the external > monitor also works with the unpatched kernel? Please provide the logs for the patched kernel. There were two different error messages in the log, and the patch would fix the first one: "*ERROR* failed to train DP, aborting". This may or may not be related to the second error message and the frozen screen.</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>