NaTaLoR
15-07-2017, 07:03
Ho appena installato Lubuntu 17.04 su un laptop Asus A53B. Il sistema ci mette diverse ore ad avviarsi (più di 5-6 ore), una volta avviato funziona bene. Come posso risolvere?
Questo è l'output di systemd-analyze:
Startup finished in 18.909s (kernel) + 5h 49min 41.051s (userspace) = 5h 49min 59.960s
Questo è l'output di systemd-analyze blame:
5h 49min 20.226s networking.service
5h 49min 20.126s apport.service
5h 49min 20.100s gpu-manager.service
5h 49min 17.559s grub-common.service
5h 49min 17.405s irqbalance.service
14.845s dev-sda1.device
9.801s keyboard-setup.service
7.959s systemd-udevd.service
6.233s lightdm.service
6.231s plymouth-quit-wait.service
4.964s systemd-resolved.service
4.394s accounts-daemon.service
4.343s ModemManager.service
2.803s snapd.autoimport.service
2.696s avahi-daemon.service
1.998s resolvconf.service
1.806s NetworkManager.service
1.546s dev-mqueue.mount
1.545s dev-hugepages.mount
1.540s sys-kernel-debug.mount
1.274s systemd-tmpfiles-setup-dev.service
984ms polkit.service
966ms upower.service
946ms systemd-modules-load.service
660ms rsyslog.service
608ms systemd-udev-trigger.service
524ms apparmor.service
513ms sys-fs-fuse-connections.mount
408ms systemd-journald.service
373ms udisks2.service
369ms motd-news.service
342ms ufw.service
291ms swapfile.swap
248ms systemd-logind.service
207ms systemd-sysctl.service
190ms systemd-tmpfiles-clean.service
179ms systemd-timesyncd.service
165ms kmod-static-nodes.service
154ms user@1000.service
130ms systemd-update-utmp.service
129ms systemd-user-sessions.service
121ms systemd-tmpfiles-setup.service
85ms plymouth-start.service
84ms ureadahead-stop.service
74ms proc-sys-fs-binfmt_misc.mount
72ms systemd-journal-flush.service
71ms setvtrgb.service
58ms console-setup.service
52ms systemd-remount-fs.service
46ms systemd-backlight@backlight:acpi_video1.service
42ms plymouth-read-write.service
37ms systemd-backlight@backlight:radeon_bl0.service
35ms pppd-dns.service
34ms systemd-random-seed.service
34ms systemd-update-utmp-runlevel.service
33ms wpa_supplicant.service
29ms systemd-backlight@backlight:acpi_video0.service
12ms systemd-rfkill.service
6ms snapd.socket
e l'output di systemd-analyze critical-chain:
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 @5h 49min 39.421s
└─accounts-daemon.service @12.625s +4.394s
└─basic.target @12.583s
└─sockets.target @12.583s
└─snapd.socket @12.576s +6ms
└─sysinit.target @12.546s
└─systemd-backlight@backlight:acpi_video1.service @15.523s +46ms
└─system-systemd\x2dbacklight.slice @12.403s
└─system.slice @2.014s
└─-.slice @1.878s
Questo è l'output di systemd-analyze:
Startup finished in 18.909s (kernel) + 5h 49min 41.051s (userspace) = 5h 49min 59.960s
Questo è l'output di systemd-analyze blame:
5h 49min 20.226s networking.service
5h 49min 20.126s apport.service
5h 49min 20.100s gpu-manager.service
5h 49min 17.559s grub-common.service
5h 49min 17.405s irqbalance.service
14.845s dev-sda1.device
9.801s keyboard-setup.service
7.959s systemd-udevd.service
6.233s lightdm.service
6.231s plymouth-quit-wait.service
4.964s systemd-resolved.service
4.394s accounts-daemon.service
4.343s ModemManager.service
2.803s snapd.autoimport.service
2.696s avahi-daemon.service
1.998s resolvconf.service
1.806s NetworkManager.service
1.546s dev-mqueue.mount
1.545s dev-hugepages.mount
1.540s sys-kernel-debug.mount
1.274s systemd-tmpfiles-setup-dev.service
984ms polkit.service
966ms upower.service
946ms systemd-modules-load.service
660ms rsyslog.service
608ms systemd-udev-trigger.service
524ms apparmor.service
513ms sys-fs-fuse-connections.mount
408ms systemd-journald.service
373ms udisks2.service
369ms motd-news.service
342ms ufw.service
291ms swapfile.swap
248ms systemd-logind.service
207ms systemd-sysctl.service
190ms systemd-tmpfiles-clean.service
179ms systemd-timesyncd.service
165ms kmod-static-nodes.service
154ms user@1000.service
130ms systemd-update-utmp.service
129ms systemd-user-sessions.service
121ms systemd-tmpfiles-setup.service
85ms plymouth-start.service
84ms ureadahead-stop.service
74ms proc-sys-fs-binfmt_misc.mount
72ms systemd-journal-flush.service
71ms setvtrgb.service
58ms console-setup.service
52ms systemd-remount-fs.service
46ms systemd-backlight@backlight:acpi_video1.service
42ms plymouth-read-write.service
37ms systemd-backlight@backlight:radeon_bl0.service
35ms pppd-dns.service
34ms systemd-random-seed.service
34ms systemd-update-utmp-runlevel.service
33ms wpa_supplicant.service
29ms systemd-backlight@backlight:acpi_video0.service
12ms systemd-rfkill.service
6ms snapd.socket
e l'output di systemd-analyze critical-chain:
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 @5h 49min 39.421s
└─accounts-daemon.service @12.625s +4.394s
└─basic.target @12.583s
└─sockets.target @12.583s
└─snapd.socket @12.576s +6ms
└─sysinit.target @12.546s
└─systemd-backlight@backlight:acpi_video1.service @15.523s +46ms
└─system-systemd\x2dbacklight.slice @12.403s
└─system.slice @2.014s
└─-.slice @1.878s