<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS" href="https://bugs.freedesktop.org/show_bug.cgi?id=63135#c18">Comment # 18</a> on <a class="bz_bug_link bz_status_NEW " title="NEW --- - [bisected] G69/nv50 DisplayPort dual-head fails to switch to KMS" href="https://bugs.freedesktop.org/show_bug.cgi?id=63135">bug 63135</a> from <a class="email" href="mailto:djpohly+freedesktop@gmail.com" title="Devin J. Pohly <djpohly+freedesktop@gmail.com>"> Devin J. Pohly</a> <pre>No, the original problem was not 100% reproducible. It always felt (this is only a guess) like it had something to do with how long the KMS switch took... if it took too long, the monitors went into powersave, and the system would almost certainly hang. There seem to be three possibilities for a boot on a bugged revision: 1. Everything works. 2. Displays go into powersave, system hangs, and you can't ssh or use SysRq. 3. (Rare.) Displays go into powersave but you can still use SysRq. For the latest attachments, I used a serial console to reliably get logs from cases 1 and 2. The original logs (from a 3.9-series kernel) relied on getting case 3 so I could REISUB and read the logs on next boot, but this may not show the bug properly. Would you like me to get logs from a recent kernel using the serial console so you can compare?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>