Le 25/03/2015 18:25, Thibaut Paumard a écrit : > > Dear Michael, > > Thanks, indeed it does look like a race condition between this script > and systemd support for binfmt. I guess the schroot service should > somehow depend on binfmt support to have terminated. > > It is not so easy for me to check though, because the boot process tends > to run smoothly when I reboot several times in a row. Any solution will > take several days at least to be confirmed. I rebooted several times > with no problem after disabling schroot, but then again with no problem > after re-enabling it.
Dear Michael,
schroot is not the culprit. Boot stalled again today with schroot init
script disabled.
Actually, I was wrongly focusing on the last failing events.
binfmt-support is the last bit of failure remaining because it happens
to have no timeout.
Let's review the symptoms:
- boot often stalls when I reboot after working for some time, but not
when rebooting several times in a row;
- systemd issues messages of several services taking unusual long time
to complete;
- boot overall feels slower than usual;
- at least on certain occasions (perhaps always), two important
services fail to start:
* systemd-logind
* network-manager.
Logind fails very early, that's usually the first message after the few
kernel messages.
Now I think the impression that boot stalls is due to logind failing to
start. This is (obviously) the reason why I never see a login prompt.
Today, using the debug shell, I manually stopped binfmt support that was
failing to start, and tried starting logind manually, which did no work.
The following command never returned, I killed it with ^C after approx.
30-60s:
systemctl start systemd-logind.service
I'm going to disable binfmt-support, just for checking, and report when
boot stalls again.
Kind regards, Thibaut.
signature.asc
Description: OpenPGP digital signature
