[Nouveau] [Bug 85471] [NV86] nouveau/kernel 3.18.0-rc1: nouveau deadlocks on 2nd Xorg start or reboot

[bugzilla-daemon at freedesktop.org]

https://bugs.freedesktop.org/show_bug.cgi?id=85471

--- Comment #6 from Christian Vogel <vogelchr at vogel.cx> ---
(In reply to Ilia Mirkin from comment #5)
> 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?

-- 
You are receiving this mail because:
You are the assignee for the bug.
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.freedesktop.org/archives/nouveau/attachments/20141026/ee523e9a/attachment.html>