On 2020-05-10 19:52, Sreyan Chakravarty wrote: > > > On 5/10/20 2:25 PM, Ed Greshko wrote: >> systemd-analyze blame >> >> to see what process is taking the longest. >> >> systemd-analyze time > > Ok here is my full systemd-blame: > > https://pastebin.com/raw/ngsF5NUv > > Is it normal for init-queue service to take so long ? > > 1min 37.191s dracut-initqueue.service > > Here is the output of systemd-analyze time > > Startup finished in 6.687s (firmware) + 8.393s (loader) + 2.328s (kernel) + 1min 41.374s (initrd) + 1min 11.363s (userspace) = 3min 10.147s > graphical.target reached after 1min 11.343s in userspace > > What can cause the initqueue to take so long ? >> FWIW, I'm actually seeing quicker boot times with 5.6 kernels than 5.5. > > I tried booting with the 5.5 kernel and the same delay happened. It is probably something related to the F32 upgrade. > > Well, according the man page for dracut-initqueue.service This service runs all the main loop of dracut in the initramfs to find the real root. This runs in 522ms on my system. But I don't use LUKS. Only a guess, but it seems it would be related to that. I've zero experience with LUKS. -- The key to getting good answers is to ask good questions. _______________________________________________ users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
