Am 20.03.2015 15:24, schrieb Pekka Paalanen:
On Fri, 20 Mar 2015 15:13:43 +0100
Thilo Cestonaro <[email protected]> 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?
It's our own hardware and kernel tree and the DRM driver is the tilcdc,
mostly like that one from beaglebone black.
I'll get the latest version and try to figure out whats going on.
But going without fbcon isn't the worst thing for me :).
Cheers,
Thilo
_______________________________________________
wayland-devel mailing list
[email protected]
http://lists.freedesktop.org/mailman/listinfo/wayland-devel
