[systemd-devel] Question: systemd-binfmt.service delayed almost 90s start

[Alien Kong]

Hi, Lennart

The attachment is the log of journalctl, but it is not the
systemd-binfmt.service delayed almost 90 seconds.

The systemd-resolved.service is executed, but it takes almost 90 seconds to
reached nss-lookup.target.

[ 3.647424] ubuntu systemd[1]: Started systemd-resolved.service - Network
> Name Resolution.
> //delayed 89.08s
> [ 92.733117] ubuntu systemd[1]: Reached target nss-lookup.target - Host
> and Network Name Lookups.


Any insight would be appreciated.Thanks~

Best regards,
Alien Kong

Lennart Poettering <lennart at poettering.net> 于2025年5月12日周一 17:58写道：

> On So, 11.05.25 15:07, Alien Kong (kqleno at gmail.com) wrote:
>
> > Hello,
> >
> > I'm currently investigating a long boot delay on our embedded Linux
> system
> > (systemd 255.4-1ubuntu8.4, custom embedded board) as a sporadic issue.
> > We noticed that `systemd-binfmt.service` takes almost 90 seconds to
> > start.
>
> You cannot really use the status output to determine that. Please look
> at the proper logs, i.e. journalctl output, and please ideally even
> turn on debug output, so you see in detail what is going
> on. (i.e. systemd.log_level=debug) on the kernel cmdline.
>
> Lennart
>
> --
> Lennart Poettering, Berlin
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20250529/be4d47bd/attachment-0001.htm>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: journalctl.log
Type: text/x-log
Size: 352945 bytes
Desc: not available
URL: <https://lists.freedesktop.org/archives/systemd-devel/attachments/20250529/be4d47bd/attachment-0001.bin>