Acabei de instalar o ubuntu mate 15.04 no meu notebook hp e leva muito tempo para inicializar (como 5 minutos). Depois disso tudo corre muito bem. Como posso verificar qual é o problema que causa isso? Eu usei o comando dmesg e obtive este . Eu posso ver que há vários atrasos, mas não está claro para mim como posso lidar com eles. Talvez alguém esteja familiarizado com esse problema e possa me ajudar? Eu ficaria grato.
Resultado de systemd-analyze blame command :
3min 42ms systemd-udev-settle.service
8.846s plymouth-quit-wait.service
6.496s mysql.service
5.949s gpu-manager.service
5.687s NetworkManager-wait-online.service
4.577s ModemManager.service
4.252s dev-disk-by\x2duuid-51885ac5\x2daf27\x2d4d13\x2db5bd\x2d9eb591337c94.device
4.069s NetworkManager.service
3.977s udisks2.service
3.490s accounts-daemon.service
3.232s systemd-tmpfiles-setup.service
2.368s bluetooth.service
2.352s systemd-logind.service
2.348s rsyslog.service
2.348s irqbalance.service
2.347s grub-common.service
2.346s loadcpufreq.service
2.344s avahi-daemon.service
2.344s apport.service
2.342s pppd-dns.service
2.341s console-kit-log-system-start.service
2.074s apparmor.service
1.862s console-kit-daemon.service
1.532s [email protected]
992ms systemd-tmpfiles-setup-dev.service
933ms polkitd.service
892ms lightdm.service
653ms systemd-journald.service
613ms systemd-modules-load.service
598ms virtualbox.service
520ms systemd-udevd.service
515ms resolvconf.service
405ms upower.service
393ms systemd-udev-trigger.service
389ms dbus.service
388ms ufw.service
346ms ondemand.service
342ms systemd-sysctl.service
337ms console-setup.service
335ms networking.service
319ms ifup-wait-all-auto.service
281ms systemd-backlight@backlight:acpi_video0.service
274ms kerneloops.service
260ms sys-kernel-debug.mount
259ms dev-mqueue.mount
259ms systemd-setup-dgram-qlen.service
259ms dev-hugepages.mount
222ms rtkit-daemon.service
187ms plymouth-read-write.service
184ms systemd-journal-flush.service
178ms [email protected]
177ms systemd-random-seed.service
170ms systemd-fsck-root.service
164ms systemd-vconsole-setup.service
145ms kmod-static-nodes.service
87ms rc-local.service
86ms [email protected]
86ms dev-mapper-cryptswap1.swap
47ms systemd-tmpfiles-clean.service
47ms systemd-update-utmp.service
31ms alsa-restore.service
29ms dns-clean.service
28ms udev-finish.service
22ms systemd-user-sessions.service
20ms systemd-remount-fs.service
17ms systemd-update-utmp-runlevel.service
15ms speech-dispatcher.service
13ms systemd-fsck@dev-disk-by\x2duuid-2efe9f37\x2d4717\x2d4dcb\x2da28f\x2d9d9a05cfa657.service
12ms plymouth-start.service
7ms ntp.service
3ms media-data.mount
3ms cpufrequtils.service
2ms ureadahead-stop.service
1ms sys-fs-fuse-connections.mount
1ms [email protected]
Após systemctl mask systemd-udev-settle :
11.658s systemd-tmpfiles-setup.service
10.468s apparmor.service
5.950s plymouth-quit-wait.service
5.927s dev-disk-by\x2duuid-51885ac5\x2daf27\x2d4d13\x2db5bd\x2d9eb591337c94.device
5.549s NetworkManager-wait-online.service
5.458s dev-mapper-cryptswap1.swap
4.057s mysql.service
3.766s gpu-manager.service
3.083s [email protected]
2.572s ModemManager.service
2.519s NetworkManager.service
2.341s systemd-udevd.service
2.066s accounts-daemon.service
1.873s console-setup.service
1.638s systemd-logind.service
1.631s grub-common.service
1.631s rsyslog.service
1.627s avahi-daemon.service
1.442s systemd-fsck-root.service
1.303s bluetooth.service
1.303s loadcpufreq.service
1.301s pppd-dns.service
1.196s systemd-tmpfiles-setup-dev.service
696ms systemd-modules-load.service
656ms ifup-wait-all-auto.service
599ms resolvconf.service
552ms console-kit-daemon.service
505ms systemd-setup-dgram-qlen.service
504ms dev-hugepages.mount
432ms apport.service
428ms polkitd.service
422ms console-kit-log-system-start.service
395ms systemd-udev-trigger.service
351ms [email protected]
342ms alsa-restore.service
332ms systemd-user-sessions.service
332ms irqbalance.service
330ms ufw.service
329ms kmod-static-nodes.service
329ms systemd-vconsole-setup.service
267ms udisks2.service
264ms systemd-journald.service
257ms systemd-sysctl.service
222ms virtualbox.service
190ms lightdm.service
189ms systemd-backlight@backlight:acpi_video0.service
174ms sys-kernel-debug.mount
174ms dev-mqueue.mount
160ms [email protected]
160ms networking.service
152ms systemd-journal-flush.service
145ms systemd-random-seed.service
144ms dbus.service
109ms kerneloops.service
63ms dns-clean.service
44ms systemd-update-utmp.service
39ms systemd-remount-fs.service
38ms systemd-tmpfiles-clean.service
30ms [email protected]
13ms systemd-update-utmp-runlevel.service
12ms plymouth-start.service
11ms plymouth-read-write.service
11ms systemd-fsck@dev-disk-by\x2duuid-2efe9f37\x2d4717\x2d4dcb\x2da28f\x2d9d9a05cfa657.service
6ms ntp.service
5ms speech-dispatcher.service
4ms upower.service
3ms cpufrequtils.service
3ms ondemand.service
3ms media-data.mount
2ms ureadahead-stop.service
2ms rtkit-daemon.service
1ms udev-finish.service
1ms sys-fs-fuse-connections.mount
1ms rc-local.service
Use ...
systemd-analyze blame
e verifique se há um serviço que demore muito para começar.
Em relação a este serviço, encontrei isso na web. 3 pessoas afirmam que o mascaramento funciona para reduzir o tempo de inicialização a meros segundos:
sudo systemctl mask systemd-udev-settle
Tags boot