You are not logged in.
Pages: 1
I have a new installation. It has a fairly long boot time that seems to be caused by a lag in getting upower.service up and running.
This may not be relevant, but I should mention that I have my root on a LUKs encrypted partition (dm-crypt).
Following is output from systemd-analyze blame:
20.908s upower.service
1.528s NetworkManager.service
535ms mariadb.service
216ms systemd-hostnamed.service
145ms systemd-journal-flush.service
109ms user@1000.service
99ms plymouth-start.service
93ms dev-mapper-vault.device
76ms ufw.service
68ms power-profiles-daemon.service
62ms systemd-udev-trigger.service
54ms polkit.service
51ms udisks2.service
44ms lvm2-monitor.service
31ms efi.mount
30ms systemd-journald.service
24ms tmp.mount
24ms wpa_supplicant.service
23ms systemd-tmpfiles-setup.service
23ms systemd-tmpfiles-setup-dev-early.service
22ms systemd-udevd.service
22ms systemd-fsck@dev-disk-by\x2duuid-A083\x2d06D3.service
22ms plymouth-quit-wait.service
22ms plymouth-quit.service
19ms systemd-boot-update.service
19ms systemd-boot-random-seed.service
17ms dev-zram0.swap
17ms user-runtime-dir@1000.service
16ms systemd-modules-load.service
14ms accounts-daemon.service
14ms systemd-logind.service
14ms systemd-remount-fs.service
13ms systemd-timesyncd.service
11ms plymouth-read-write.service
11ms dbus-broker.service
11ms systemd-rfkill.service
11ms cups.service
10ms bluetooth.service
9ms systemd-tmpfiles-setup-dev.service
9ms systemd-userdbd.service
7ms systemd-random-seed.service
5ms dev-hugepages.mount
5ms dev-mqueue.mount
5ms sys-kernel-debug.mount
5ms sys-kernel-tracing.mount
4ms systemd-sysctl.service
4ms kmod-static-nodes.service
4ms modprobe@configfs.service
4ms modprobe@drm.service
3ms modprobe@fuse.service
3ms systemd-udev-load-credentials.service
3ms systemd-update-utmp.service
3ms rtkit-daemon.service
2ms systemd-vconsole-setup.service
2ms systemd-user-sessions.service
2ms modprobe@loop.service
1ms modprobe@dm_mod.service
1ms sys-fs-fuse-connections.mount
1ms boot.mount
1ms sys-kernel-config.mount
Following is output from journalctl -u upower.service -x, which shows that the service loads just fine. But why so long?
-- Boot 0cf1e4fcb72348d7960d93c8352c25ae --
Mar 23 13:08:47 archlinux systemd[1]: Starting Daemon for power management...
Subject: A start job for unit upower.service has begun execution
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/l … temd-develA start job for unit upower.service has begun execution.
The job identifier is 1566.
Mar 23 13:09:08 archlinux systemd[1]: Started Daemon for power management.
Subject: A start job for unit upower.service has finished successfully
Defined-By: systemd
Support: https://lists.freedesktop.org/mailman/l … temd-develA start job for unit upower.service has finished successfully.
The job identifier is 1566.
Last edited by johnny.honu (2025-03-24 12:01:23)
Offline
Pages: 1