ke 28. heinäk. 2021 klo 19.18 Dennis Filder (d.fil...@web.de) kirjoitti: > * You have tpm2-abrmd installed, and its systemd unit is the only one > defining a Requires=systemd-udev-settle.service. 2.1.0-1 under > Buster didn't do that yet, so this could be the breaking change. As > its manpage states systemd-udev-settle.service as a unit is > conceptually problematic because udev events are never really > settled; the unit is also deprecated, so tpm2-abrmd should correct > its systemd/udev definitions.
It was probably pulled in as a Recommends. At least I don't recall ever installing it. > * Another potential issue is this line: > > post-up systemctl restart micro-httpd.socket > > The call to systemctl might be blocking. Could be. That post-up is there because micro-https is launched by systemd before all network interfaces are up, which fails because the 172.16.1.2 to which I've configured it to bind does not exist that early during bootup. micro-httpd would need to launch only after all interfaces are up. I filed a bug against micro-https for that specific issue. > I wonder if that micro-httpd.socket definition amounts to a circular > dependency resulting in a deadlock. Could be. However, please note that bootup only stalls when launched using the normal mode. If I boot via recovery mode and resume from the rescue shell prrompt, it doesn't stall. > I recommend uncommenting the post-up line from /etc/network/interfaces > just to see if this solves the problem. Alternatively try disabling > tpm2-abrmd.service temporarily. I purged tpm2-abrmd and regular bootup no longer stalls. Thanks for the above. You zeroed-in on the most probable cause of the problem. :) Martin-Éric
