[systemd-devel] Running a x86_64 kernel on Fedora 15 x86 userland

[Lennart Poettering]

On Mon, 02.05.11 21:49, Thomas Meyer (thomas at m3y3r.de) wrote:

> Hi,
> 
> I try to run a x86_64 kernel on x86 Fedora 15 userland. But systemd get's somehow stuck in the boot process. Any ideas how to debug the problem? What is systemd waiting for?
> 
> I need to boot with selinux=0 as I get some selinux errors (file not found or something like this, strangley these lines doesn't show up in the netconsole log).
> 
> Here is what I could catch via netconsole and systemd.log_level=debug:

> [   27.640330] <31>systemd[1]: Received SIGCHLD from PID 189 (plymouthd).
> [   27.640358] <31>systemd[1]: Got SIGCHLD for process 189 (plymouthd)
> [   27.640382] <31>systemd[1]: Child 189 died (code=killed, status=6/ABRT)

plymouthd dies with SIGABRT, i.e. hits an assert().

> [  208.596279] <29>systemd-cryptsetup[702]: Timed out
> [  208.596329] <27>systemd-cryptsetup[702]: Failed to query password: Timer expired

And subsequently the password query times out, presumably because no
Plymouth was there where you could have entered your LUKS password.

Try tracking down the assert in Plymouth.

If you run systemd 26 you can also try "plymouth.enable=0 rd.plymouth=0"
on the kernel cmdline. This will disable plymouth both in systemd and in
dracut, and should cause systemd to query the password with a normal
password prompt on the console instead.

Lennart

-- 
Lennart Poettering - Red Hat, Inc.