Userspace needs 90 seconds to boot

Excubia · 2016-08-20 23:07:00

$ systemd-analyze
Startup finished in 1.400s (kernel) + 1min 30.804s (userspace) = 1min 32.204s

This seems to be a known bug. The new version of systemd does not solve the problem. What shall I do?

jasonwryan · 2016-08-21 00:40:36

Read your journal and see what is taking time to come up...

Moving to NC.

cra1g321 · 2016-08-21 03:04:09

using

systemd-analyze blame

will show you what services are taking up the most time during boot.

Head_on_a_Stick · 2016-08-21 16:20:21

I prefer:

systemd-analyze plot > boot.svg

However, the time displayed by `systemd-analyze` is the time taken for all of the enabled units to complete their startup and this may occur some time after a fully "usable" desktop is reached, at least from the perspective of the end-user.

@OP: does it really take a minute and a half before you can do anything with your desktop?

I sometimes see long times reported by that command whilst experiencing absolutely no apparent delay in startup.

Excubia · 2016-08-25 01:16:42

Yes, it really takes that long.

Here is the svg : https://paste.ee/p/tr8TK

Head_on_a_Stick · 2016-08-25 08:01:20

Excubia wrote:

Here is the svg : https://paste.ee/p/tr8TK

A picture is worth a thousand words:

https://cdn.scrot.moe/images/2016/08/25/boot.svg.png

I will look into this in more detail tonight.

Last edited by Head_on_a_Stick (2016-08-25 08:02:27)

Head_on_a_Stick · 2016-08-27 23:25:32

Ooops, I forgot about this...

Looking at the graph, there seems to be a big delay after all the bluetooth stuff starts -- does the speed improve if you blacklist those?

zerophase · 2016-08-27 23:42:34

I suggest try unplugging USB devices. I've had that happen since a device is dying. If that's the case it impacts Windows start up as well.

Excubia · 2016-08-27 23:58:33

This bug is on a Macbook Air. It has no USB devices. MacOS boots very fast.

promarbler14 · 2016-08-28 00:57:02

Are there any failed units after startup? What do systemctl --failed (and systemctl status) report?

A delay of 90 seconds suggests a timeout is being reached. (It seems to be network-related.) Does systemd log anything into the system journal? What is the output of journalctl SYSLOG_IDENTIFIER=systemd -b?

It could be dependencies which prevents tasks from running outside a certain order... Does systemctl list-dependencies reveal anything notable?

Aside from anything possibly network-related, have you made sure that you aren't waiting for some nonexistent drive to mount? You can also check /etc/fstab for this.

Try booting into emergency/rescue mode, and starting services up manually. For example, after reaching the console, try starting the services NetworkManager and/or gdm individually. If you are waiting on a blank screen, switching to tty1 (ctrl-alt-1) may help reveal the culprit.

Excubia · 2016-08-28 20:56:26

$ systemctl --failed
0 loaded units listed. Pass --all to see loaded but inactive units, too.
To show all installed unit files use 'systemctl list-unit-files'.

$ journalctl SYSLOG_IDENTIFIER=systemd -b
Hint: You are currently not seeing messages from other users and the system.
      Users in groups 'adm', 'systemd-journal', 'wheel' can see all messages.
      Pass -q to turn off this notice.
-- Logs begin at ven. 2016-04-29 04:32:31 CEST, end at dim. 2016-08-28 22:49:57 
août 28 01:53:33 pomme systemd[684]: Reached target Paths.
août 28 01:53:33 pomme systemd[684]: Starting D-Bus User Message Bus Socket.
août 28 01:53:33 pomme systemd[684]: Listening on Sound System.
août 28 01:53:33 pomme systemd[684]: Reached target Timers.
août 28 01:53:33 pomme systemd[684]: Listening on D-Bus User Message Bus Socket.
août 28 01:53:33 pomme systemd[684]: Reached target Sockets.
août 28 01:53:33 pomme systemd[684]: Reached target Basic System.
août 28 01:53:33 pomme systemd[684]: Starting Update XDG user dir configuration.
août 28 01:53:33 pomme systemd[684]: Started Update XDG user dir configuration.
août 28 01:53:33 pomme systemd[684]: Reached target Default.
août 28 01:53:33 pomme systemd[684]: Startup finished in 16ms.
août 28 01:53:34 pomme systemd[684]: Started D-Bus User Message Bus.
août 28 01:53:34 pomme systemd[684]: Starting Accessibility services bus...
août 28 01:53:34 pomme systemd[684]: Started Accessibility services bus.
août 28 01:53:34 pomme systemd[684]: Starting Virtual filesystem service...
août 28 01:53:34 pomme systemd[684]: Started Virtual filesystem service.
août 28 01:53:35 pomme systemd[684]: Starting Sound Service...
août 28 01:53:35 pomme systemd[684]: Started Sound Service.
août 28 01:53:35 pomme systemd[684]: Starting Evolution source registry...
août 28 01:53:35 pomme systemd[684]: Starting Virtual filesystem metadata servic
août 28 01:53:35 pomme systemd[684]: Started Virtual filesystem metadata service
août 28 01:53:35 pomme systemd[684]: Started Evolution source registry.

$ systemctl list-dependencies
default.target
● ├─gdm.service
● └─multi-user.target
●   ├─cpupower.service
●   ├─dbus.service
●   ├─dhcpcd@ens9.service
●   ├─lm_sensors.service
●   ├─logrotate.timer
●   ├─man-db.timer
●   ├─netctl-auto@wlp3s0-NEUF_CAC8.service
●   ├─NetworkManager.service
●   ├─org.cups.cupsd.path
●   ├─shadow.timer
●   ├─suppress-gpe4E.service
●   ├─suppress-gpe66.service
●   ├─systemd-ask-password-wall.path
●   ├─systemd-logind.service
●   ├─systemd-user-sessions.service
●   ├─tlp.service
●   ├─basic.target
●   │ ├─-.mount
●   │ ├─alsa-restore.service
●   │ ├─alsa-state.service

$ cat /etc/fstab
# 
# /etc/fstab: static file system information
#
# <file system>	<dir>	<type>	<options>	<dump>	<pass>
# /dev/sda4
UUID=f5ccdfb8-7c61-4763-9f4f-590181f4a158	/         	ext4      	rw,relatime,data=ordered	0 1

Arch Linux

#1 2016-08-20 23:07:00

Userspace needs 90 seconds to boot

#2 2016-08-21 00:40:36

Re: Userspace needs 90 seconds to boot

#3 2016-08-21 03:04:09

Re: Userspace needs 90 seconds to boot

#4 2016-08-21 16:20:21

Re: Userspace needs 90 seconds to boot

#5 2016-08-25 01:16:42

Re: Userspace needs 90 seconds to boot

#6 2016-08-25 08:01:20

Re: Userspace needs 90 seconds to boot

#7 2016-08-27 23:25:32

Re: Userspace needs 90 seconds to boot

#8 2016-08-27 23:42:34

Re: Userspace needs 90 seconds to boot

#9 2016-08-27 23:58:33

Re: Userspace needs 90 seconds to boot

#10 2016-08-28 00:57:02

Re: Userspace needs 90 seconds to boot

#11 2016-08-28 20:56:26

Re: Userspace needs 90 seconds to boot

Board footer