<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEW " title="NEW - [NV86] nouveau/kernel 3.18.0-rc1: nouveau deadlocks on 2nd Xorg start or reboot" href="https://bugs.freedesktop.org/show_bug.cgi?id=85471#c6">Comment # 6</a> on <a class="bz_bug_link bz_status_NEW " title="NEW - [NV86] nouveau/kernel 3.18.0-rc1: nouveau deadlocks on 2nd Xorg start or reboot" href="https://bugs.freedesktop.org/show_bug.cgi?id=85471">bug 85471</a> from <a class="email" href="mailto:vogelchr@vogel.cx" title="Christian Vogel <vogelchr@vogel.cx>"> Christian Vogel</a> <pre>(In reply to Ilia Mirkin from <a href="show_bug.cgi?id=85471#c5">comment #5</a>) > nouveau.runpm=0 This fixes the issue with the hung X-Server, I can terminate and re-start X-servers as expected when logged in via ssh. But parts of the bug remain, namely that the X-console will freeze as soon as the VT on which the X-server was active is selected: - system boots, X-server works, I can login, use applications - stop lightdm -> X-server turns off, screen goes black, keyboard does not work - via ssh: start lightdm -> X-server restarts, everything looks ok again A funny variation of that theme: - system works, running X - switch to VT2 (Ctrl-Alt-F2), I get the linux vt #2, everything ok - on the console (or via ssh): stop lightdm -> nothing visible changes, X terminates in the background - switch to VT3 (Ctrl-Alt-F3), I get the linux vt #3, all ok - switch to VT1 (Ctrl-Alt-F1) where the X-server was active before: -> cursor stops blinking, keyboard no longer responsive, screen content frozen - via ssh: start lightdm -> X server starts up, I can login into X and use applications, keyboard works (actually, that's how I write this text now...) - switch to VT2, VT3, ... works now. ---> Why does the framebuffer-console hang when I change into the VT previously occupied by nouveau/xorg?</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the assignee for the bug.</li> </ul> </body> </html>