Submission type

• Bug report
• Request for enhancement (RFE)

NOTE: Do not submit anything other than bug reports or RFEs via the issue tracker!

systemd version the issue has been seen with

231

NOTE: Do not submit bug reports about anything but the two most recently released systemd versions upstream!

Used distribution

Debian Stretch

In case of bug report: Expected behaviour you didn't see

System should boot quickly

In case of bug report: Unexpected behaviour you saw

NetworkManager cannot start for 1 min 30 sec.

In case of bug report: Steps to reproduce the problem

Install Debian Testing into qemu. Make sure that network is managed with NetworkManager (it is sufficient to select the default GNOME desktop environment during installation). Boot, and reboot again, and see how 90 seconds of systemd's patience on NetworkManager run out.

This has been traced in https://bugs.debian.org/837597 to the fact that NetworkManager calls getrandom(), but the non-blocking random pool is not initialized yet. I.e. not enough entropy, even though systemd-rannom-seed has completed successfully.

See also https://lwn.net/Articles/694434/ for some insight - namely, the result is that just writing to /dev/urandom does not credit any entropy to the system (even though there is, in fact, entropy - carried over from the previous boot), and that an ioctl (RNDADDENTROPY) is necessary for the kernel to take the new entropy into account.