After exiting weston all consoles not working anymore

[Pekka Paalanen]

On Fri, 20 Mar 2015 15:13:43 +0100
Thilo Cestonaro <thilo at cestona.ro> wrote:

> Am 20.03.2015 12:54, schrieb Thilo Cestonaro:
> > Am 20.03.2015 11:32, schrieb Thilo Cestonaro:
> >> Further debuggin.
> >> 
> >> I added some debug output to weston-launch.
> >> When the parent part (of the forks) recieves the SIGCHILD it calls the
> >> quit function.
> >> And in there I added the debug output and the ioctl to set the text
> >> mode, never returns.
> >> 
> >> So it hangs in the kernel, right?
> > 
> > The kernel's console_lock is not returning. Somehow the console_lock
> > can't be acquired, as it is already locked.
> > 
> 
> It looks like fbcon can't work together with weston. So, if I compile my 
> kernel to not include FRAMEBUFFER_CONSOLE at all,
> I can restart weston as often as I want.
> 
> What I've not tried yet is, compiling fbcon as module, but I await no 
> different behave with fbcon loaded as module.
> 
> Any ideas, comments? :)

Broken gfx kernel driver, or kernel patched with breakage, are my wild
guesses. Could be an immature DRM gfx driver.

What kernel tree, what drivers, what hardware exactly?


Thanks,
pq