You are not logged in.
My system seems to have a strange delay during boot that I don't know how to account for. In the SVG plot, there is a long delay before `sysinit.target` comes on, but it doesn't seem that anything is blocking it.
Also, systemd-blame shows everything starting prety quickly.
1.332s lightdm.service
1.255s systemd-logind.service
1.254s avahi-daemon.service
1.150s systemd-update-utmp.service
539ms NetworkManager.service
437ms user@620.service
393ms accounts-daemon.service
360ms systemd-udev-trigger.service
323ms systemd-tmpfiles-setup.service
316ms systemd-vconsole-setup.service
316ms dev-hugepages.mount
316ms dev-mqueue.mount
316ms sys-kernel-debug.mount
295ms kmod-static-nodes.service
276ms ntpd.service
231ms systemd-sysctl.service
224ms user@1000.service
216ms systemd-user-sessions.service
176ms polkit.service
170ms systemd-journal-flush.service
127ms systemd-random-seed.service
127ms rtkit-daemon.service
111ms upower.service
98ms colord.service
90ms sys-kernel-config.mount
82ms systemd-backlight@acpi_video0.service
67ms sys-fs-fuse-connections.mount
66ms systemd-tmpfiles-setup-dev.service
55ms wpa_supplicant.service
53ms dev-sda2.swap
33ms alsa-restore.service
30ms udisks2.service
3ms systemd-remount-fs.service
2ms tmp.mount
2ms systemd-udevd.service
2ms systemd-tmpfiles-clean.service
And here is what the journal says in that time gap (nothing):
Dec 26 07:39:51 yvne systemd[1]: Starting Swap.
Dec 26 07:39:51 yvne systemd[1]: Reached target Swap.
Dec 26 07:40:26 yvne systemd[1]: Starting System Initialization.
Dec 26 07:40:26 yvne systemd[1]: Reached target System Initialization.
Last edited by shawnjgoff (2013-12-26 13:13:19)
Offline