Forum

Startup finished in 3.231s (firmware) + 6.010s (loader) + 18.349s (kernel) + 1min 47.357s (userspace) = 2min 14.949s
graphical.target reached after 1min 38.910s in userspace.

$ systemd-analyze blame
5.604s NetworkManager.service
5.567s NetworkManager-wait-online.service
3.053s shorewall.service
2.931s systemd-udev-settle.service
2.329s mandriva-everytime.service
2.073s dev-sda2.device
1.081s upower.service
968ms user@0.service
933ms systemd-udev-trigger.service
899ms udisks2.service
836ms user@1000.service
801ms cups.service
715ms polkit.service
686ms mga-bg-res.service
675ms shorewall6.service
516ms lm_sensors.service
485ms systemd-logind.service
466ms rtkit-daemon.service
435ms systemd-journald.service
393ms systemd-udevd.service
381ms avahi-daemon.service
316ms bluetooth.service
270ms systemd-rfkill.service
262ms systemd-tmpfiles-setup.service
261ms acpid.service
251ms ModemManager.service
250ms systemd-journal-flush.service
235ms gpm.service
231ms colord.service
231ms dracut-shutdown.service
229ms switcheroo-control.service
229ms power-profiles-daemon.service
201ms systemd-tmpfiles-setup-dev-early.service
199ms dbus.service
183ms systemd-hostnamed.service
172ms systemd-tmpfiles-setup-dev.service
166ms systemd-fsck-root.service
162ms dev-hugepages.mount
161ms lvm2-monitor.service
160ms mdmonitor-takeover.service
159ms dev-mqueue.mount
157ms sys-kernel-debug.mount
155ms sys-kernel-tracing.mount
154ms kmod-static-nodes.service
148ms modprobe@configfs.service
144ms modprobe@dm_mod.service
142ms modprobe@fuse.service
142ms sensord.service
141ms systemd-modules-load.service
135ms systemd-vconsole-setup.service
133ms modprobe@loop.service
130ms plymouth-quit-wait.service
124ms systemd-udev-load-credentials.service
115ms dmraid-activation.service
115ms plymouth-quit.service
112ms systemd-random-seed.service
106ms systemd-remount-fs.service
97ms plymouth-start.service
95ms dev-disk-byx2duuid-045b880cx2d9446x2d4ad6x2db47bx2d6313da50789f.swap
80ms systemd-sysctl.service
78ms sys-fs-fuse-connections.mount
78ms boot-EFI.mount
78ms systemd-fsck@dev-disk-byx2duuid-ce246f8cx2d11fex2d40b2x2db93ex2db27a8a4c56b1.service
73ms sys-kernel-config.mount
62ms wpa_supplicant.service
58ms tmp.mount
57ms systemd-update-utmp.service
56ms systemd-user-sessions.service
54ms user-runtime-dir@1000.service
54ms plymouth-read-write.service
48ms drakx-installer-xsetup.service
48ms user-runtime-dir@0.service
45ms home.mount
4ms systemd-ask-password.socket
4ms systemd-factory-reset.socket
4ms systemd-coredump.socket
3ms systemd-bootctl.socket
2ms systemd-sysext.socket
2ms systemd-creds.socket
1ms systemd-importd.socket
237us systemd-machined.socket
212us avahi-daemon.socket
176us systemd-journald-dev-log.socket
145us systemd-journald.socket
116us dm-event.socket
103us cups.socket
102us systemd-hostnamed.socket
98us dbus.socket
96us systemd-udevd-control.socket
96us systemd-logind-varlink.socket
89us systemd-udevd-kernel.socket
83us systemd-udevd-varlink.socket
55us systemd-rfkill.socket

$ 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 38.862s
└─multi-user.target @1min 38.862s
└─cups.service @1min 37.986s +874ms
└─network.target @1min 37.980s
└<span class="emoji-tag">─wpa_supplicant.service @1min 37.916s +61ms
└─dbus.service @1min 31.892s +177ms </span>
└─basic.target @1min 31.871s
└─sockets.target @1min 31.870s
└─systemd-machined.socket @1min 31.870s +223us
└─sysinit.target @1min 31.862s
└─tpm2.target @1min 31.861s