wynik systemd-analyze:
Kod: Zaznacz cały
kszyhu@kszyhu-H270-HD3:~$ systemd-analyze
Startup finished in 2.101s (kernel) + 21.958s (userspace) = 24.060s
graphical.target reached after 21.939s in userspace
Kod: Zaznacz cały
kszyhu@kszyhu-H270-HD3:~$ systemd-analyze blame
20.849s plymouth-quit-wait.service
7.383s NetworkManager-wait-online.service
760ms fwupd.service
528ms snapd.service
400ms vboxdrv.service
369ms motd-news.service
361ms dev-nvme0n1p1.device
302ms keyboard-setup.service
290ms snapd.seeded.service
276ms apparmor.service
267ms systemd-logind.service
223ms plymouth-read-write.service
221ms NetworkManager.service
214ms snap-gnome\x2dlogs-45.mount
192ms snap-core-6350.mount
179ms snap-core-6259.mount
Kod: Zaznacz cały
kszyhu@kszyhu-H270-HD3:~$ systemd-analyze critical-chain
The time after the unit is active or started is printed after the "@" character.
The time after the unit is active or started is printed after the "@" character.
The time the unit takes to start is printed after the "+" character.
graphical.target @21.939s
└─multi-user.target @21.939s
└─smbd.service @8.521s +48ms
└─nmbd.service @8.470s +50ms
└─network-online.target @8.469s
└─NetworkManager-wait-online.service @1.085s +7.383s
└─NetworkManager.service @863ms +221ms
└─dbus.service @837ms
└─basic.target @819ms
└─sockets.target @819ms
└─snapd.socket @818ms +1ms
└─sysinit.target @816ms
└─apparmor.service @540ms +276ms
└─local-fs.target @535ms
└─run-user-1000-gvfs.mount @1.879s
└─run-user-1000.mount @1.181s
└─local-fs-pre.target @420ms
└─keyboard-setup.service @118ms +302ms
└─systemd-journald.socket @117ms
└─system.slice @116ms
└─-.slice @115ms
Ostatnio aktualizowałem system z 18.04.1 do 18.04.2
Kernel 4.15.0-46. Dysk SSD M.2 Nvme.
Proszę o jakieś podpowiedzi.