Hello, I am experiencing a slow boot speed on my laptop running Fedora. I have provided the specifications of my laptop, the version of Fedora, the boot time, and the running services at the time of boot.
Startup finished in 6.215s (firmware) + 7.096s (loader) + 1.532s (kernel) + 3.375s (initrd) + 1min 10.828s (userspace) = 1min 29.048s
graphical.target reached after 1min 10.809s in userspace.
On certain days, I experience a prolonged boot time. Usually, it takes 7 to 8 seconds, but it takes 1 minute and 30 seconds now. Why is that, and how can it be resolved?
sauradipghosh
(Sauradip Ghosh)
Category updated
May 29, 2024, 1:49pm
2
barryascott
(Barry A Scott)
Category updated
May 29, 2024, 6:08pm
4
Please edit your posts so that the output is using the pre-formatted text style that preserves spaces. Its the </>
button, select the text and click the button.
I chaged this to be a ask fedora topic.
1 Like
What is the output of systemd-analyze critical-chain
?
I think from the blame output the dkms.service seems to be the problem.
This is the output
systemd-analyze critical-chain
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 8.370s
The time when unit became active or started is printed after the "@" character.
The time the unit took to start is printed after the "+" character.
graphical.target @1min 8.370s
└─multi-user.target @1min 8.370s
└─plymouth-quit-wait.service @1min 5.278s +3.088s
└─systemd-user-sessions.service @1min 5.250s +10ms
└─remote-fs.target @1min 5.210s
└─remote-fs-pre.target @1min 140ms
└─nfs-client.target @1min 139ms
└─gssproxy.service @1min 114ms +24ms
└─network.target @1min 106ms
└─wpa_supplicant.service @1min 97ms +7ms
└─basic.target @2.670s
└─dbus-broker.service @2.640s +28ms
└─dbus.socket @2.622s
└─sysinit.target @2.617s
└─systemd-resolved.service @2.467s +149ms
└─systemd-tmpfiles-setup.service @2.330s +112ms
└─import-state.service @2.241s +67ms
└─local-fs.target @2.221s
└─run-snapd-ns-ufw.mnt.mount @1min 588ms
└─run-snapd-ns.mount @1min 173ms
└─swap.target @1.599s
└─dev-zram0.swap @1.529s +69ms
└─systemd-zram-setup@zram0.service @1.472s>
└─dev-zram0.device @1.470s
Yes dkms.service takes too long , I don’t know why
systemd-analyze blame output :
systemd-analyze blame
56.112s dkms.service
48.038s dnf-makecache.service
5.087s NetworkManager-wait-online.service
4.070s sys-module-fuse.device
4.020s dev-ttyS15.device
4.020s sys-devices-platform-serial8250-serial8250:0-serial8250:0.15-tty-ttyS15.devi>
4.019s dev-ttyS12.device
4.019s sys-devices-platform-serial8250-serial8250:0-serial8250:0.12-tty-ttyS12.devi>
4.018s sys-devices-platform-serial8250-serial8250:0-serial8250:0.10-tty-ttyS10.devi>
4.018s dev-ttyS10.device
4.015s sys-devices-platform-serial8250-serial8250:0-serial8250:0.1-tty-ttyS1.device
4.015s dev-ttyS1.device
4.011s sys-devices-platform-serial8250-serial8250:0-serial8250:0.19-tty-ttyS19.devi>
4.011s dev-ttyS19.device
4.009s sys-devices-platform-serial8250-serial8250:0-serial8250:0.0-tty-ttyS0.device
4.009s dev-ttyS0.device
4.005s sys-devices-platform-serial8250-serial8250:0-serial8250:0.16-tty-ttyS16.devi>
4.005s dev-ttyS16.device
4.003s dev-ttyS11.device
4.003s sys-devices-platform-serial8250-serial8250:0-serial8250:0.11-tty-ttyS11.devi>
4.003s sys-devices-platform-serial8250-serial8250:0-serial8250:0.14-tty-ttyS14.devi>
4.003s dev-ttyS14.device
4.003s sys-devices-platform-serial8250-serial8250:0-serial8250:0.23-tty-ttyS23.devi>
4.003s dev-ttyS23.device
3.998s sys-devices-platform-serial8250-serial8250:0-serial8250:0.6-tty-ttyS6.device
3.998s dev-ttyS6.device
3.996s dev-ttyS13.device
3.996s sys-devices-platform-serial8250-serial8250:0-serial8250:0.13-tty-ttyS13.devi>
3.994s sys-devices-platform-serial8250-serial8250:0-serial8250:0.8-tty-ttyS8.device
3.994s dev-ttyS8.device
3.991s dev-ttyS20.device
3.991s sys-devices-platform-serial8250-serial8250:0-serial8250:0.20-tty-ttyS20.devi>
3.991s sys-devices-platform-serial8250-serial8250:0-serial8250:0.18-tty-ttyS18.devi>
3.991s dev-ttyS18.device
3.990s sys-devices-platform-serial8250-serial8250:0-serial8250:0.2-tty-ttyS2.device
3.990s dev-ttyS2.device
3.987s dev-ttyS21.device
3.987s sys-devices-platform-serial8250-serial8250:0-serial8250:0.21-tty-ttyS21.devi>
3.985s dev-ttyS22.device
3.985s sys-devices-platform-serial8250-serial8250:0-serial8250:0.22-tty-ttyS22.devi>
3.984s sys-devices-platform-serial8250-serial8250:0-serial8250:0.24-tty-ttyS24.devi>
3.984s dev-ttyS24.device
3.983s dev-ttyS27.device
3.983s sys-devices-platform-serial8250-serial8250:0-serial8250:0.27-tty-ttyS27.devi>
3.983s sys-devices-platform-serial8250-serial8250:0-serial8250:0.17-tty-ttyS17.devi>
3.983s dev-ttyS17.device
3.981s dev-ttyS28.device
3.981s sys-devices-platform-serial8250-serial8250:0-serial8250:0.28-tty-ttyS28.devi>
3.980s sys-devices-platform-serial8250-serial8250:0-serial8250:0.29-tty-ttyS29.devi>
3.980s dev-ttyS29.device
3.978s dev-ttyS7.device
3.978s sys-devices-platform-serial8250-serial8250:0-serial8250:0.7-tty-ttyS7.device
3.976s dev-ttyS25.device
3.976s sys-devices-platform-serial8250-serial8250:0-serial8250:0.25-tty-ttyS25.devi>
3.974s dev-ttyS30.device
3.974s sys-devices-platform-serial8250-serial8250:0-serial8250:0.30-tty-ttyS30.devi>
3.973s dev-ttyS3.device
3.973s sys-devices-platform-serial8250-serial8250:0-serial8250:0.3-tty-ttyS3.device
3.971s dev-ttyS31.device
3.971s sys-devices-platform-serial8250-serial8250:0-serial8250:0.31-tty-ttyS31.devi>
3.969s dev-ttyS26.device
3.969s sys-devices-platform-serial8250-serial8250:0-serial8250:0.26-tty-ttyS26.devi>
3.957s dev-ttyS5.device
3.957s sys-devices-platform-serial8250-serial8250:0-serial8250:0.5-tty-ttyS5.device
3.955s dev-ttyS9.device
3.955s sys-devices-platform-serial8250-serial8250:0-serial8250:0.9-tty-ttyS9.device
3.955s sys-devices-platform-serial8250-serial8250:0-serial8250:0.4-tty-ttyS4.device
3.955s dev-ttyS4.device
3.927s sys-module-configfs.device
3.922s dev-disk-by\x2did-ata\x2dWDC_WD10SPZX\x2d60Z10T0_WD\x2dWX91AA83Y9UF.device
3.922s dev-disk-by\x2ddiskseq-1.device
3.922s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.device
3.922s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda>
3.922s dev-disk-by\x2did-wwn\x2d0x50014ee65e747149.device
3.922s dev-sda.device
3.922s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0.device
3.903s sys-subsystem-net-devices-eno1.device
3.903s sys-devices-pci0000:00-0000:00:1d.5-0000:03:00.0-net-eno1.device
3.887s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p>
3.887s dev-disk-by\x2dlabel-fedora_localhost\x2dlive.device
3.887s dev-disk-by\x2duuid-ef7cbad4\x2dbf7b\x2d4032\x2d8f45\x2da21f814b51c6.device
3.887s dev-disk-by\x2ddiskseq-2\x2dpart3.device
3.887s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart3.device
3.887s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L_1\x2dpart3.d>
3.887s dev-disk-by\x2dpartuuid-60dde35e\x2d5174\x2d4365\x2da146\x2da65d4ba38f31.dev>
3.887s dev-disk-by\x2did-nvme\x2deui.002538d421d1febf\x2dpart3.device
3.887s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L\x2dpart3.dev>
3.887s dev-nvme0n1p3.device
3.821s dev-disk-by\x2did-nvme\x2deui.002538d421d1febf\x2dpart1.device
3.821s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L_1\x2dpart1.d>
3.821s dev-nvme0n1p1.device
3.821s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p>
3.821s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart1.device
3.821s dev-disk-by\x2duuid-13BD\x2dAB98.device
3.821s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L\x2dpart1.dev>
3.821s dev-disk-by\x2dpartlabel-EFI\x5cx20System\x5cx20Partition.device
3.821s dev-disk-by\x2ddiskseq-2\x2dpart1.device
3.821s dev-disk-by\x2dpartuuid-11badb63\x2d9c0e\x2d405e\x2db593\x2d22407982d534.dev>
3.809s dev-disk-by\x2did-nvme\x2deui.002538d421d1febf\x2dpart2.device
3.809s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L\x2dpart2.dev>
3.809s dev-nvme0n1p2.device
3.809s dev-disk-by\x2duuid-32b11fa1\x2d4911\x2d4012\x2d8074\x2d8296374bec9d.device
3.809s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1\x2dpart2.device
3.809s dev-disk-by\x2dpartuuid-b45da48d\x2d8356\x2d46d8\x2db6ef\x2d208497e8264e.dev>
3.809s dev-disk-by\x2ddiskseq-2\x2dpart2.device
3.809s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L_1\x2dpart2.d>
3.809s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1-nvme0n1p>
3.803s dev-disk-by\x2dpath-pci\x2d0000:02:00.0\x2dnvme\x2d1.device
3.803s dev-disk-by\x2did-nvme\x2deui.002538d421d1febf.device
3.803s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L_1.device
3.803s sys-devices-pci0000:00-0000:00:1d.0-0000:02:00.0-nvme-nvme0-nvme0n1.device
3.803s dev-disk-by\x2did-nvme\x2dSamsung_SSD_980_500GB_S64DNX0T458648L.device
3.803s dev-nvme0n1.device
3.803s dev-disk-by\x2ddiskseq-2.device
3.596s dev-disk-by\x2dpartuuid-6bb91a3d\x2d68ec\x2d4162\x2db8d5\x2d39e4e8fd43c0.dev>
3.596s dev-disk-by\x2duuid-1A4858E24858BDE7.device
3.596s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0\x2dpart4.device
3.596s dev-sda4.device
3.596s dev-disk-by\x2did-ata\x2dWDC_WD10SPZX\x2d60Z10T0_WD\x2dWX91AA83Y9UF\x2dpart4>
3.596s dev-disk-by\x2did-wwn\x2d0x50014ee65e747149\x2dpart4.device
3.596s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda>
3.596s dev-disk-by\x2ddiskseq-1\x2dpart4.device
3.596s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5\x2dpart4.device
3.563s dev-disk-by\x2dpartuuid-9b62592a\x2d2d52\x2d49d8\x2db2ed\x2dd7b084af4b7c.dev>
3.563s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda>
3.563s dev-disk-by\x2duuid-BAFC866FFC86262B.device
3.563s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5\x2dpart3.device
3.563s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0\x2dpart3.device
3.563s dev-sda3.device
3.563s dev-disk-by\x2ddiskseq-1\x2dpart3.device
3.563s dev-disk-by\x2did-wwn\x2d0x50014ee65e747149\x2dpart3.device
3.563s dev-disk-by\x2did-ata\x2dWDC_WD10SPZX\x2d60Z10T0_WD\x2dWX91AA83Y9UF\x2dpart3>
3.562s dev-disk-by\x2dlabel-New\x5cx20Volume.device
3.562s dev-disk-by\x2dpartlabel-Basic\x5cx20data\x5cx20partition.device
3.533s dev-sda5.device
3.533s dev-disk-by\x2ddiskseq-1\x2dpart5.device
3.533s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5.0\x2dpart5.device
3.533s sys-devices-pci0000:00-0000:00:17.0-ata5-host4-target4:0:0-4:0:0:0-block-sda>
3.533s dev-disk-by\x2did-wwn\x2d0x50014ee65e747149\x2dpart5.device
3.533s dev-disk-by\x2did-ata\x2dWDC_WD10SPZX\x2d60Z10T0_WD\x2dWX91AA83Y9UF\x2dpart5>
3.533s dev-disk-by\x2dpath-pci\x2d0000:00:17.0\x2data\x2d5\x2dpart5.device
3.533s dev-disk-by\x2duuid-50A260BCA260A864.device
3.533s dev-disk-by\x2dpartuuid-ddfcbf77\x2df637\x2d452f\x2d8d8c\x2d68ac2cd53524.dev>
3.304s sys-devices-pci0000:00-0000:00:02.0-drm-card0-card0\x2deDP\x2d1-intel_backli>
3.088s plymouth-quit-wait.service
1.701s akmods.service
1.403s docker.service
1.256s NetworkManager.service
1.181s initrd-switch-root.service
1.125s plymouth-switch-root.service
1.080s mongod.service
822ms dracut-initqueue.service
700ms snap.ufw.srv.service
600ms firewalld.service
578ms systemd-journal-flush.service
538ms thermald.service
513ms udisks2.service
505ms upower.service
452ms iio-sensor-proxy.service
427ms power-profiles-daemon.service
415ms accounts-daemon.service
413ms polkit.service
411ms fwupd.service
381ms dev-loop12.device
369ms dev-loop9.device
360ms dev-loop11.device
354ms systemd-udev-trigger.service
343ms dev-loop10.device
322ms systemd-logind.service
318ms chronyd.service
298ms dev-loop7.device
274ms user@1000.service
255ms systemd-udevd.service
230ms jexec.service
201ms systemd-vconsole-setup.service
190ms bluetooth.service
180ms ModemManager.service
178ms switcheroo-control.service
173ms lvm2-monitor.service
165ms var-lib-snapd-snap-bare-5.mount
149ms systemd-resolved.service
149ms abrtd.service
148ms var-lib-snapd-snap-core-16202.mount
147ms rtkit-daemon.service
145ms dev-loop4.device
143ms dev-loop1.device
142ms dev-loop6.device
138ms var-lib-snapd-snap-core-16928.mount
129ms postgresql.service
118ms systemd-oomd.service
114ms dev-loop3.device
114ms dev-loop5.device
112ms systemd-tmpfiles-setup.service
110ms dev-loop8.device
110ms dev-loop2.device
108ms avahi-daemon.service
106ms var-lib-snapd-snap-core18-2812.mount
104ms dev-loop0.device
97ms containerd.service
93ms var-lib-snapd-snap-core18-2823.mount
90ms var-lib-nfs-rpc_pipefs.mount
86ms var-lib-snapd-snap-core22-1033.mount
78ms var-lib-snapd-snap-core22-1122.mount
73ms dracut-shutdown.service
72ms var-lib-snapd-snap-gnome\x2d3\x2d28\x2d1804-198.mount
72ms auditd.service
71ms home.mount
71ms systemd-journald.service
69ms dev-zram0.swap
67ms import-state.service
65ms livesys.service
60ms var-lib-snapd-snap-gnome\x2d42\x2d2204-141.mount
60ms var-lib-snapd-snap-hello\x2dworld-29.mount
54ms systemd-tmpfiles-setup-dev-early.service
52ms var-lib-snapd-snap-gtk\x2dcommon\x2dthemes-1535.mount
51ms virtqemud.service
48ms redis.service
47ms systemd-machined.service
47ms var-lib-snapd-snap-ufw-653.mount
47ms systemd-backlight@backlight:intel_backlight.service
45ms boot-efi.mount
43ms systemd-fsck@dev-disk-by\x2duuid-13BD\x2dAB98.service
43ms dracut-cmdline.service
43ms systemd-tmpfiles-setup-dev.service
43ms systemd-tmpfiles-clean.service
41ms systemd-binfmt.service
40ms systemd-zram-setup@zram0.service
40ms systemd-fsck@dev-disk-by\x2duuid-32b11fa1\x2d4911\x2d4012\x2d8074\x2d8296374>
37ms systemd-sysctl.service
36ms systemd-userdbd.service
36ms dracut-pre-pivot.service
35ms dev-hugepages.mount
34ms systemd-boot-update.service
33ms dev-mqueue.mount
33ms var-lib-snapd-snap-heroku-4092.mount
32ms systemd-random-seed.service
32ms sys-kernel-debug.mount
32ms boot.mount
31ms sys-kernel-tracing.mount
29ms kmod-static-nodes.service
28ms dbus-broker.service
28ms plymouth-read-write.service
26ms sssd-kcm.service
26ms systemd-fsck-root.service
25ms initrd-cleanup.service
25ms cups.service
24ms uresourced.service
24ms gssproxy.service
22ms livesys-late.service
21ms initrd-udevadm-cleanup-db.service
21ms tmp.mount
19ms dracut-pre-udev.service
18ms plymouth-start.service
17ms docker.socket
16ms systemd-modules-load.service
15ms systemd-rfkill.service
15ms colord.service
15ms systemd-network-generator.service
14ms flatpak-system-helper.service
14ms proc-sys-fs-binfmt_misc.mount
13ms rpc-statd-notify.service
13ms sys-fs-fuse-connections.mount
12ms systemd-remount-fs.service
12ms gdm.service
12ms modprobe@configfs.service
11ms user-runtime-dir@1000.service
10ms initrd-parse-etc.service
10ms systemd-user-sessions.service
10ms systemd-sysusers.service
9ms systemd-update-utmp-runlevel.service
8ms snapd.socket
8ms systemd-update-utmp.service
8ms preload.service
8ms modprobe@fuse.service
7ms wpa_supplicant.service
6ms modprobe@drm.service
4ms modprobe@dm_mod.service
3ms modprobe@loop.service
You need to review what dkms is doing for you.
What are you using that needs it?
Also check how long snapd services are taking.
2 Likes