[systemd-devel] Waiting udev jobs

Lennart Poettering lennart at poettering.net
Sat Mar 27 12:38:40 UTC 2021


On Fr, 26.03.21 23:24, Alan Perry (alanp at snowmoose.com) wrote:

> I occasionally see a problem where systemd-analyze reports that boot
> did not complete and it is suggested that I use systemctl list-jobs
> to find out more. That shows a .device service job and some sub-jobs
> (associated with udev rules) all waiting. They will wait for literal
> days in this state. When I accessed the system, it wasn’t apparent
> what the jobs were waiting on since all of the device symlinks and
> such were there and working. The systemctl status of the .device
> service was alive.
>
> Any suggestions on what is going on and/or how to figure out what is
> going on?
>
> If you have followed my posts here previously, it should come as no
> surprise that the device that I observed this happen with was one of
> the emmc boot devices.

This is not enough information. Please provide "systemctl status" info
on the relevant units and jobs, please provide a dump of the output.

And most importantly, always start with the systemd version number you
are using, and whether you have any weird udev rules or so, or just
plain upstream stuff.

Lennart

--
Lennart Poettering, Berlin


More information about the systemd-devel mailing list