On 2021-07-17 1:18 p.m., Joe Zeff wrote:
On 7/17/21 8:35 AM, John Mellor wrote:
> What's wrong here? This is a fully up-to-date and stock F34 machine
> with a good i5 processor, lots of RAM and a fast SSD, with a very
> long and inexplicable time delay during boot. It appears to be idle
> for 2 minutes during every startup, with no known cause. This
> machine used to boot in 8 seconds, but now takes over 2 minutes every
> time.
Run systemd-analyze blame
and post the part of the output that shows times of one second or more.
Here is the top of the current systemd-analyse blame output:
$ systemd-analyze blame
27.625s plymouth-quit-wait.service
21.726s udisks2.service
13.932s libvirtd.service
13.711s systemd-journal-flush.service
12.946s abrtd.service
10.635s polkit.service
10.256s upower.service
9.109s NetworkManager-wait-online.service
9.030s lvm2-monitor.service
8.490s firewalld.service
8.208s sssd.service
7.309s accounts-daemon.service
6.730s initrd-switch-root.service
6.071s ModemManager.service
6.070s avahi-daemon.service
5.765s lm_sensors.service
5.761s rtkit-daemon.service
5.760s switcheroo-control.service
5.759s systemd-machined.service
5.758s thermald.service
5.757s systemd-homed.service
5.745s dbus-broker.service
4.511s fwupd.service
4.347s packagekit.service
4.107s chronyd.service
3.696s cups.service
2.850s systemd-udevd.service
2.661s geoclue.service
2.587s NetworkManager.service
2.040s wpa_supplicant.service
1.589s systemd-tmpfiles-setup-dev.service
1.516s systemd-resolved.service
1.207s gdm.service
1.105s systemd-logind.service
1.077s dracut-initqueue.service
904ms auditd.service
844ms
systemd-fsck@dev-disk-by\x2duuid-bd603b31\x2d7ca0\x2d483e\x2daa91\x2d202c876783f2.service
669ms colord.service
649ms
systemd-fsck@dev-disk-by\x2duuid-b572a339\x2d50fe\x2d4574\x2da299\x2d8d3fa9f3efa0.service
528ms systemd-zram-setup(a)zram0.service
494ms
systemd-fsck@dev-disk-by\x2duuid-691af7ca\x2d5f30\x2d454b\x2d832f\x2d6ef37b60060a.service