<html> <head> <base href="https://bugs.freedesktop.org/"> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [bisected] GDM Login screen doesn't show up on kernel 5.3 or later" href="https://bugs.freedesktop.org/show_bug.cgi?id=111966#c7">Comment # 7</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [bisected] GDM Login screen doesn't show up on kernel 5.3 or later" href="https://bugs.freedesktop.org/show_bug.cgi?id=111966">bug 111966</a> from <a class="email" href="mailto:freedesktop201910@liggy.de" title="Torsten <freedesktop201910@liggy.de>"> Torsten</a> <pre>I'm having a similar issue as Masami and git bisect pointed to the same commit 36a0f92020dc8794d3aa69b7fb4c5d2bf99b0099, so I thought I just add my comment here instead of raising a new bug. My situation is a bit different as my server does not start GDM but stays on the console, but starting with the commit that Masami mentioned, my console always stays blank so I'm assuming the actual root cause for both our problems is the same. My board is an Asrock B250M-HDV with Pentium Gold G4560 CPU (HD Graphics 610), running Debian 10.1 with stock x86_64 kernel and I noticed that the bug only occurs with the board's VGA output, DVI was fine but is usually not available to the server, HDMI could not be tested. Testing with the latest available drm-tip (commit 0204e2b48f2a9ae8aff60393755f8164f2fa1038) the console stayed blank. The patch from Masami worked successfully both on drm-tip and official 5.3.5. For comparison I'm attaching dmesg debug output once with and once without fix. The interesting part starts at [3.062539] on the broken dmesg and [3.071882] on the dmesg with fix. Maybe the debug output makes more sense to someone else than it does to me.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are on the CC list for the bug.</li> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>