Hi, systemd-243-2.gitfab6f01.fc31.x86_64 systemd-analyze reports very high firmware times, seemingly related to uptime since last cold boot. That is, if I poweroff then boot, the time for firmware seems reasonable; whereas reboots appear to show cumulative time for only the firmware value. This is in a qemu-kvm VM, using edk2-ovmf-20190501stable-4.fc31.noarch reboot (warm boot) $ systemd-analyze Startup finished in 8min 2.506s (firmware) + 12ms (loader) + 1.414s (kernel) + 1.383s (initrd) + 8.962s (userspace) = 8min 14.278s graphical.target reached after 8.946s in userspace [chris@localhost-live ~]$ # systemd-analyze Startup finished in 18min 13.786s (firmware) + 11ms (loader) + 1.420s (kernel) + 1.361s (initrd) + 8.855s (userspace) = 18min 25.434s graphical.target reached after 8.840s in userspace [root@localhost-live ~]# # systemd-analyze Startup finished in 20min 22.976s (firmware) + 11ms (loader) + 1.410s (kernel) + 1.360s (initrd) + 8.801s (userspace) = 20min 34.560s graphical.target reached after 8.790s in userspace [root@localhost-live ~]# # systemd-analyze Startup finished in 51min 8.018s (firmware) + 12ms (loader) + 1.415s (kernel) + 1.370s (initrd) + 8.836s (userspace) = 51min 19.653s graphical.target reached after 8.821s in userspace [root@localhost-live ~]# poweroff+boot (cold boot) # systemd-analyze Startup finished in 2.402s (firmware) + 15ms (loader) + 1.498s (kernel) + 1.358s (initrd) + 8.723s (userspace) = 13.998s graphical.target reached after 8.709s in userspace [root@localhost-live ~]# -- Chris Murphy _______________________________________________ systemd-devel mailing list systemd-devel@xxxxxxxxxxxxxxxxxxxxx https://lists.freedesktop.org/mailman/listinfo/systemd-devel