0
Wrzucam:
Udało mi się załączyć tylko spakowane, plik .svg nie jest obsługiwany przez forum.
Kod:
systemd-analyze blameKod:
# systemd-analyze blame
6.664s apt-daily.service
6.553s upower.service
2.783s NetworkManager-wait-online.service
2.399s udisks2.service
1.575s fwupd-refresh.service
1.520s smartmontools.service
762ms systemd-logind.service
674ms apt-daily-upgrade.service
652ms dev-sda1.device
569ms lightdm.service
564ms plymouth-quit-wait.service
533ms lvm2-monitor.service
462ms vmware-USBArbitrator.service
447ms networkd-dispatcher.service
441ms accounts-daemon.service
331ms systemd-journald.service
292ms [email protected]
250ms systemd-modules-load.service
245ms systemd-resolved.service
236ms systemd-sysusers.service
234ms systemd-random-seed.service
232ms ubuntu-system-adjustments.service
228ms bluetooth.service
225ms avahi-daemon.service
223ms NetworkManager.service
218ms polkit.service
211ms systemd-journal-flush.service
197ms libvirt-guests.service
191ms gpu-manager.service
167ms thermald.service
163ms systemd-machined.service
159ms ModemManager.service
157ms libvirtd.service
155ms wpa_supplicant.service
153ms systemd-fsck@dev-disk-by\x2duuid-aabdd86e\x2d0da8\x2d4bee\x2da75a\x2d97ee17f647a5.service
152ms e2scrub_reap.service
138ms networking.service
127ms systemd-rfkill.service
127ms grub-common.service
109ms virtualbox.service
96ms keyboard-setup.service
94ms alsa-restore.service
93ms systemd-udev-trigger.service
92ms systemd-udevd.service
85ms motion.service
85ms secureboot-db.service
78ms apparmor.service
76ms geoclue.service
65ms colord.service
62ms dev-disk-by\x2duuid-4f1b0309\x2dd9d3\x2d43dc\x2d9ab6\x2ddf9aee554172.swap
62ms ftscanhv.service
61ms dev-disk-by\x2duuid-f23927de\x2dce04\x2d43e4\x2dab13\x2dacb6b1c89723.swap
58ms ftsprhv.service
56ms lm-sensors.service
54ms rsyslog.service
48ms systemd-tmpfiles-clean.service
47ms qemu-kvm.service
45ms home.mount
43ms systemd-tmpfiles-setup.service
36ms pppd-dns.service
35ms binfmt-support.service
32ms grub-initrd-fallback.service
31ms hddtemp.service
31ms ntp.service
29ms systemd-user-sessions.service
20ms kerneloops.service
20ms [email protected]
19ms vboxweb.service
19ms dev-hugepages.mount
18ms dev-mqueue.mount
18ms systemd-remount-fs.service
17ms systemd-sysctl.service
17ms console-setup.service
17ms sys-kernel-debug.mount
17ms plymouth-start.service
16ms sys-kernel-tracing.mount
15ms plymouth-read-write.service
14ms blk-availability.service
14ms ifupdown-pre.service
13ms systemd-tmpfiles-setup-dev.service
12ms systemd-update-utmp.service
12ms kmod-static-nodes.service
12ms proc-sys-fs-binfmt_misc.mount
11ms openvpn.service
10ms systemd-update-utmp-runlevel.service
9ms rtkit-daemon.service
9ms finalrd.service
6ms sys-fs-fuse-connections.mount
5ms ufw.service
4ms sys-kernel-config.mount
3ms setvtrgb.service
3ms libvirtd.socket Kod:
systemd-analyze critical-chainKod:
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 33.595s
└─multi-user.target @1min 33.595s
└─virtualbox.service @1min 33.486s +109ms
└─network-online.target @1min 33.475s
└─NetworkManager-wait-online.service @1min 30.691s +2.783s
└─NetworkManager.service @1min 30.464s +223ms
└─dbus.service @1min 30.459s
└─basic.target @1min 30.439s
└─sockets.target @1min 30.439s
└─libvirtd-ro.socket @1min 30.439s
└─libvirtd.socket @1min 30.435s +3ms
└─sysinit.target @1min 30.429s
└─apparmor.service @1min 30.350s +78ms
└─systemd-journald.socket @254ms
└─-.mount @248ms
└─system.slice @248ms
└─-.slice @248msKod:
systemd-analyze plot >bootup.svgUdało mi się załączyć tylko spakowane, plik .svg nie jest obsługiwany przez forum.