Автозагрузка в linux Mint Cinnamon

#21

slant писал(а): ↑
27 апр 2021, 21:43
Вопрос здесь в том, с какого перепугу сервис который по всем канонам должен быть фоновым, стал блокирующим(загрузку)?

На мой взгляд не совсем так, глядя на график fstrim стартует как раз спустя 90+ секунд и не лочит graphical.target

hellonet писал(а): ↑
27 апр 2021, 16:00
graphical.target reached after 1min 31.166s in userspace

Работает он долго, да, почти пять минут но как минимум не выглядит как корневая причина.

Может там еще что подключено из носителей или других устройств? кто виноват пока не видно

#22

Whowka писал(а): ↑
27 апр 2021, 21:28
Почти 5 минут,при запуске, отрабатывает fstrim.service.

На этом же диске стоит ещё одна точно такая же система, которая грузится 12 секунд до окна с паролем и 12 секунд после

#23

hellonet, а та что за система, и под каким ядром? я б пожалуй проверил с ядра сначала

#24

demonlibra писал(а): ↑
27 апр 2021, 22:11
а не включали ли Вы fstrim.service самостоятельно?

Не знаю. А как его выключить?

#25

Chocobo писал(а): ↑
28 апр 2021, 10:44
а та что за система, и под каким ядром? я б пожалуй проверил с ядра сначала

Втроая система(с быстрым запуском) тоже Linux Mint 20.1 Ulissa Mate

System: Kernel: 5.4.0-72-generic x86_64 bits: 64 compiler: gcc v: 9.3.0 Desktop: MATE 1.24.0
wm: marco dm: LightDM Distro: Linux Mint 20.1 Ulyssa base: Ubuntu 20.04 focal
Machine: Type: Desktop Mobo: ASUSTeK model: P8H77-V v: Rev X.0x serial: <filter>
UEFI: American Megatrends v: 1905 date: 10/27/2014
CPU: Topology: Quad Core model: Intel Core i7-3770 bits: 64 type: MT MCP arch: Ivy Bridge
rev: 9 L2 cache: 8192 KiB
flags: avx lm nx pae sse sse2 sse3 sse4_1 sse4_2 ssse3 vmx bogomips: 54399
Speed: 3895 MHz min/max: 1600/3900 MHz Core speeds (MHz): 1: 3870 2: 3881 3: 3803
4: 3872 5: 3803 6: 3882 7: 3805 8: 3861
Graphics: Device-1: NVIDIA GM206 [GeForce GTX 960] vendor: Micro-Star MSI driver: nvidia
v: 460.73.01 bus ID: 01:00.0 chip ID: 10de:1401
Display: x11 server: X.Org 1.20.9 driver: nvidia
unloaded: fbdev,modesetting,nouveau,vesa compositor: marco
resolution: 1920x1200~60Hz, 1920x1080~60Hz
OpenGL: renderer: GeForce GTX 960/PCIe/SSE2 v: 4.6.0 NVIDIA 460.73.01
direct render: Yes
Audio: Device-1: Intel 7 Series/C216 Family High Definition Audio vendor: ASUSTeK
driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:1e20
Device-2: NVIDIA GM206 High Definition Audio vendor: Micro-Star MSI
driver: snd_hda_intel v: kernel bus ID: 01:00.1 chip ID: 10de:0fba
Sound Server: ALSA v: k5.4.0-72-generic
Network: Device-1: Qualcomm Atheros AR8161 Gigabit Ethernet vendor: ASUSTeK driver: alx
v: kernel port: d000 bus ID: 03:00.0 chip ID: 1969:1091
IF: enp3s0 state: up speed: 100 Mbps duplex: full mac: <filter>
Drives: Local Storage: total: 5.80 TiB used: 39.90 GiB (0.7%)
ID-1: /dev/sda vendor: A-Data model: SU800 size: 238.47 GiB speed: 6.0 Gb/s
serial: <filter>
ID-2: /dev/sdb vendor: OCZ model: VERTEX3 size: 111.79 GiB speed: 6.0 Gb/s
serial: <filter>
ID-3: /dev/sdc vendor: Seagate model: ST6000DM003-2CY186 size: 5.46 TiB speed: 3.0 Gb/s
serial: <filter>
RAID: Hardware-1: VIA VT6421 IDE/SATA Controller driver: sata_via v: 2.6 bus ID: 05:02.0
chip ID: 1106.3249
Partition: ID-1: / size: 36.62 GiB used: 12.50 GiB (34.1%) fs: ext4 dev: /dev/sdb3
ID-2: /home size: 36.31 GiB used: 27.35 GiB (75.3%) fs: ext4 dev: /dev/sdb2
USB: Hub: 1-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
Hub: 1-1:2 info: Intel Integrated Rate Matching Hub ports: 6 rev: 2.0
chip ID: 8087:0024
Hub: 2-0:1 info: Full speed (or root) Hub ports: 2 rev: 2.0 chip ID: 1d6b:0002
Hub: 2-1:2 info: Intel Integrated Rate Matching Hub ports: 8 rev: 2.0
chip ID: 8087:0024
Device-1: 2-1.5:3 info: SHARKOON type: Mouse driver: hid-generic,usbhid rev: 1.1
chip ID: 1ea7:0064
Device-2: 2-1.7:4 info: Cypress Keyboard/Hub type: Keyboard,Mouse
driver: hid-generic,usbhid rev: 1.1 chip ID: 04b4:0101
Device-3: 2-1.8:5 info: Sunplus Innovation Optical Mouse type: Mouse
driver: hid-generic,usbhid rev: 2.0 chip ID: 1bcf:0005
Hub: 3-0:1 info: Full speed (or root) Hub ports: 4 rev: 2.0 chip ID: 1d6b:0002
Hub: 3-4:2 info: Microchip (formerly SMSC) USB 2.0 Hub ports: 3 rev: 2.0
chip ID: 0424:2514
Hub: 3-4.1:3 info: Microchip (formerly SMSC) USB 2.0 Hub ports: 3 rev: 2.0
chip ID: 0424:2640
Device-4: 3-4.1.1:4 info: Microchip (formerly SMSC) Ultra Fast Media Reader
type: Mass Storage driver: usb-storage rev: 2.0 chip ID: 0424:4060
Hub: 4-0:1 info: Full speed (or root) Hub ports: 4 rev: 3.0 chip ID: 1d6b:0003
Sensors: System Temperatures: cpu: 57.0 C mobo: 27.8 C gpu: nvidia temp: 46 C
Fan Speeds (RPM): N/A gpu: nvidia fan: 0%
Repos: No active apt repos in: /etc/apt/sources.list
Active apt repos in: /etc/apt/sources.list.d/google-chrome.list
1: deb [arch=amd64] http: //dl.google.com/linux/chrome/deb/ stable main
Active apt repos in: /etc/apt/sources.list.d/official-package-repositories.list
1: deb http: //packages.linuxmint.com ulyssa main upstream import backport #id:linuxmint_main
2: deb http: //archive.ubuntu.com/ubuntu focal main restricted universe multiverse
3: deb http: //archive.ubuntu.com/ubuntu focal-updates main restricted universe multiverse
4: deb http: //archive.ubuntu.com/ubuntu focal-backports main restricted universe multiverse
5: deb http: //security.ubuntu.com/ubuntu/ focal-security main restricted universe multiverse
6: deb http: //archive.canonical.com/ubuntu/ focal partner
Info: Processes: 259 Uptime: 2m Memory: 15.58 GiB used: 737.5 MiB (4.6%) Init: systemd v: 245
runlevel: 5 Compilers: gcc: 9.3.0 alt: 9 Client: Unknown python3.8 client inxi: 3.0.38

sudo systemd-analyze blame

q@q:~$ sudo systemd-analyze blame
[sudo] пароль для q:
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
lines 1-23...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
lines 1-24...skipping...

609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
lines 1-25...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
lines 1-27...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
lines 1-30...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
lines 1-33...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
lines 1-36...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
lines 1-38...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
lines 1-40...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
lines 1-41...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
lines 1-42...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
lines 1-43...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
lines 1-44...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
lines 1-45...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
lines 1-46...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
lines 1-47...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
lines 1-48...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >

#26

Добавка

156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
lines 1-49...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >

55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
lines 1-50...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
lines 1-51...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
lines 1-52...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
lines 1-53...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
lines 1-54...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
lines 1-55...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
lines 1-56...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
lines 1-57...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
11ms systemd-remount-fs.service >
lines 1-58...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
11ms systemd-remount-fs.service >
11ms kmod-static-nodes.service >
lines 1-59...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
11ms systemd-remount-fs.service >
11ms kmod-static-nodes.service >
9ms systemd-update-utmp.service >
lines 1-60...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
11ms systemd-remount-fs.service >
11ms kmod-static-nodes.service >
9ms systemd-update-utmp.service >
9ms grub-initrd-fallback.service >
lines 1-61...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
11ms systemd-remount-fs.service >
11ms kmod-static-nodes.service >
9ms systemd-update-utmp.service >
9ms grub-initrd-fallback.service >
8ms systemd-random-seed.service >
lines 1-62...skipping...
609ms dev-sdb3.device >
359ms udisks2.service >
318ms networkd-dispatcher.service >
247ms systemd-logind.service >
230ms accounts-daemon.service >
192ms ubuntu-system-adjustments.service >
188ms gpu-manager.service >
185ms systemd-resolved.service >
181ms upower.service >
156ms boot-efi.mount >
151ms avahi-daemon.service >
147ms NetworkManager.service >
144ms plymouth-quit-wait.service >
137ms polkit.service >
122ms networking.service >
118ms lvm2-monitor.service >
115ms thermald.service >
115ms lightdm.service >
112ms e2scrub_reap.service >
110ms wpa_supplicant.service >
110ms ModemManager.service >
103ms user@1000.service >
95ms systemd-udevd.service >
92ms systemd-journald.service >
82ms systemd-udev-trigger.service >
80ms swapfile.swap >
70ms grub-common.service >
63ms apparmor.service >
61ms keyboard-setup.service >
55ms systemd-journal-flush.service >
53ms systemd-fsck@dev-disk-by\x2duuid-A2EA\x2d93DF.service >
52ms hddtemp.service >
43ms rsyslog.service >
34ms systemd-fsck@dev-disk-by\x2duuid-f745350e\x2dcdba\x2d4905\x2da182\x2d3884>
33ms systemd-modules-load.service >
33ms dns-clean.service >
31ms systemd-update-utmp-runlevel.service >
30ms alsa-restore.service >
29ms ntp.service >
27ms lm-sensors.service >
26ms systemd-tmpfiles-setup.service >
20ms systemd-tmpfiles-clean.service >
18ms modprobe@drm.service >
18ms plymouth-start.service >
17ms kerneloops.service >
16ms pppd-dns.service >
15ms dev-hugepages.mount >
15ms systemd-sysusers.service >
15ms dev-mqueue.mount >
14ms sys-kernel-debug.mount >
14ms systemd-tmpfiles-setup-dev.service >
14ms systemd-sysctl.service >
13ms sys-kernel-tracing.mount >
13ms console-setup.service >
13ms plymouth-read-write.service >
11ms blk-availability.service >
11ms user-runtime-dir@1000.service >
11ms systemd-remount-fs.service >
11ms kmod-static-nodes.service >
9ms systemd-update-utmp.service >
9ms grub-initrd-fallback.service >
8ms systemd-random-seed.service >
8ms nvidia-persistenced.service >
lines 1-63

sudo systemd-analyze time

q@q:~$ sudo systemd-analyze time
[sudo] пароль для q:
Startup finished in 8.086s (firmware) + 12.866s (loader) + 3.382s (kernel) + 1.591s (userspace) = 25.927s
graphical.target reached after 1.538s in userspace
q@q:~$

sudo systemd-analyze plot > plot.svg

Ссылка на изображение (чат, мгновенное сообщение, электронная почта)
https://svgshare.com/s/Wi6
Прямая ссылка (чат, IM, электронная почта)
https://svgshare.com/i/Wi6.svg
HTML (сайт, блог)
<a href='https://svgshare.com/s/Wi6' ><img src='https://svgshare.com/i/Wi6.svg' title='Syst2' /></a>
HTML iframe (сайт, блог)
<iframe src='https://svgshare.com/f/Wi6' width=100% height=100% ></iframe>
Преобразователь хэша
https://svgshare.com/getbyhash/sha1-8+P ... 1cJbsyyw4=

#27

hellonet писал(а): ↑
28 апр 2021, 13:54

demonlibra писал(а): ↑
27 апр 2021, 22:11
а не включали ли Вы fstrim.service самостоятельно?
Не знаю. А как его выключить?

Я только предположил, так как в LinuxMint по умолчанию используется fstrim.time вместо fstrim.service.

Скорее всего причина не в этом, но для проверки можно:

Выключить сервис fstrim sudo systemctl disable fstrim.service
Перезагрузить ПК
Создать новый график загрузки и сравнить с предыдущим: systemd-analyze plot > plot.svg
Включить сервис fstrim sudo systemctl enable fstrim.service

#28

Обращаюсь ко всем.
Вот выложены были оба графика загрузки с первой системы (медленной) и второй (быстрой). Пытаюсь понять в чём разница и что нужно выключить. ( сообщения #25 и #26 быстрая) и (#8 #10 #13 медленная)

#29

demonlibra писал(а): ↑
28 апр 2021, 14:13
Скорее всего причина не в этом, но для проверки можно:
Выключить сервис fstrim sudo systemctl disable fstrim.service
Перезагрузить ПК
Создать новый график загрузки и сравнить с предыдущим: systemd-analyze plot > plot.svg
Включить сервис fstrim sudo systemctl enable fstrim.service

Сейчас перейду на медленную систему и попробую сделать

#30

hellonet писал(а): ↑
28 апр 2021, 14:35
Вот выложены были оба графика загрузки с первой системы (медленной) и второй (быстрой)

В чём смысл нескольких систем?
И почему в них ядра разных версий?

#31

demonlibra писал(а): ↑
28 апр 2021, 15:15
В чём смысл нескольких систем?

Когда первая система стала долго загружаться, то установил вторую. А с первой пытаюсь разобраться. Если не получится разобраться, то когда полностью настрою под себя вторую систему, первую систему снесу. Ядра разных версий наверное потому, что первая система идёт ещё с LM 17 путём постепенных обновлений до 20.1, а вторую систему сразу с нуля ставил 20.1

#32

Первая система раньше работала быстро?

#33

У меня fstrim.service выключен

Код: Выделить всё

nick ~                                                                                                                                            
▶ sudo systemctl status fstrim.service 
[sudo] пароль для nick: 
● fstrim.service - Discard unused blocks on filesystems from /etc/fstab
     Loaded: loaded (/lib/systemd/system/fstrim.service; static; vendor preset: enabled)
     Active: inactive (dead)
TriggeredBy: ● fstrim.timer
       Docs: man:fstrim(8)

nick ~                                                                                                                                           ⍉
▶ sudo systemctl status fstrim.timer  
● fstrim.timer - Discard unused blocks once a week
     Loaded: loaded (/lib/systemd/system/fstrim.timer; enabled; vendor preset: enabled)
     Active: active (waiting) since Wed 2021-04-28 11:09:44 +05; 6h ago
    Trigger: Mon 2021-05-03 00:00:00 +05; 4 days left
   Triggers: ● fstrim.service
       Docs: man:fstrim

апр 28 11:09:44 nick-pc systemd[1]: Started Discard unused blocks once a week.

Система

Код: Выделить всё

System:    Kernel: 5.11.16-051116-generic x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: KDE Plasma 5.21.4 
           Distro: KDE neon 20.04 5.21 base: Ubuntu 20.04 LTS Focal

#34

hellonet писал(а): ↑
28 апр 2021, 14:36
Создать новый график загрузки и сравнить с предыдущим: systemd-analyze plot > plot.svg

fstrim.service убил.Быстрее загружаться не стала

Ссылка на изображение (чат, мгновенное сообщение, электронная почта)
https://svgshare.com/s/WiT
Прямая ссылка (чат, IM, электронная почта)
https://svgshare.com/i/WiT.svg
HTML (сайт, блог)
<a href='https://svgshare.com/s/WiT' ><img src='https://svgshare.com/i/WiT.svg' title='sys1' /></a>
HTML iframe (сайт, блог)
<iframe src='https://svgshare.com/f/WiT' width=100% height=100% ></iframe>
Преобразователь хэша
https://svgshare.com/getbyhash/sha1-EU9 ... SrR6hERTs=

Я правильно понял, что процессы, выделенные красным занимают при загрузке многовато времени? Но откуда набегает почти 2 минуты? Из которых большую часть времени ничего не происходит - просто круглая зелёная эмблемка висит на чёрном экране

#35

hellonet писал(а): ↑
28 апр 2021, 15:26
Я правильно понял, что процессы, выделенные красным занимают при загрузке многовато времени?

Красный цвет на графике - это время загрузки

#36

hellonet писал(а): ↑
28 апр 2021, 15:26
просто круглая зелёная эмблемка висит на чёрном экране

Как я понимаю, это plymouth-start.service. Может его тоже отключить?

hellonet писал(а): ↑
28 апр 2021, 15:26
Быстрее загружаться не стала

Ну 1-й график 386 с, а 2-й 94 с

#37

hellonet писал(а): ↑
28 апр 2021, 15:26
выделенные красным занимают при загрузке многовато времени

У всех есть красная область, просто у некоторых она слишком короткая.
Длительная загрузка какого-то процесса не обязательно тормозит загрузку других.

hellonet писал(а): ↑
28 апр 2021, 15:26
просто круглая зелёная эмблемка висит на чёрном экране

Если нажать ESC, что отобразится?

#38

Whowka писал(а): ↑
28 апр 2021, 15:46
это plymouth-start.service. Может его тоже отключить?

Зачем, если он существует только 15 мс?

#39

demonlibra писал(а): ↑
28 апр 2021, 15:55
если он существует только 15 мс?

Но после него пауза почти минута

demonlibra писал(а): ↑
28 апр 2021, 15:55
Зачем

Посмотреть, шо получитца

#40

demonlibra писал(а): ↑
28 апр 2021, 15:21
Первая система раньше работала быстро?

Да

Кто сейчас на конференции