You are not logged in.
Systemd boot got really slow at some point.
It prints all the messages with all the green OK status. It is extremely slow, in fact, slower that any sequential boot 20 years ago. No errors though.
Kernel parameters are as per silent boot article with quiet and log level set appropriately.
Any help is appreciated. Maybe I can fiddle with some other systemd parameters? It does not look it parallelised at all.
Offline
What is in the journal? Blame? etc...
Not a Sysadmin issue, moving to NC.
Offline
Post the output of
cat /proc/cmdline
Offline
What is in the journal? Blame? etc...
Not a Sysadmin issue, moving to NC.
If this is not sys admin issue then I don't know what is....
I am sorry but I posted it in sys admin to avoid the exact questions: "What's in the journal?" Lots of output is in the journal as usual.
If there was anything significant to the issue I'd deferentially mentioned it. Nothing special there as far as I can see. No errors if that's what your are asking?
Is there anything specific do you want me to look at?
The same goes for blame. Nothing unusual, at least to my eye. 'NetworkManager-wait-online.service' takes 4 secs. This is the longest. Everything else in ms.
Regardless of the time per service spend, isn't it supposed to be in parallel and non-blocking fashion?
Every service is run sequentially. And the output is displayed on the screen. I suppose this is my problem.
Offline
Post the output of
cat /proc/cmdline
As I mentioned in my original post, everything is as per silent boot article.
"quiet loglevel=3 vga=current rd.udev.log-priority=3"
Everything else is irrelevant.
Offline
Everything else is irrelevant.
Since you are asking why your boot is slow even if you think something is "irrelevant" you should post it all. Unexpected combinations of settings may not be visible to you and will definitely be invisible to everyone else without full details.
EDIT
Also, from earlier in your thread:
What is in the journal? Blame? etc...
Post your: Blame.
Last edited by headkase (2015-04-30 08:46:23)
Offline
Stitch wrote:Everything else is irrelevant.
Since you are asking why your boot is slow even if you think something is "irrelevant" you should post it all. Unexpected combinations of settings may not be visible to you and will definitely be invisible to everyone else without full details.
initrd=\initramfs-linux root=PARTUUID=d82ddae4-66bb-48db-9328-8c8e14a4346d rootfstype=btrfs rootflags=subvol=system ro quiet loglevel=3 vga=current rd.udev.log-priority=3 modprobe.blacklist=nouveau
Offline
See my edit to my above post, I edited at the same time as you posted, post your blame.
Offline
I have to rephrase the original post.
Although booting is slow but it is not the most accented part of the question. Which is my fault not putting it correctly.
The major points are: Why is it sequential even for unrelated services when it should be parallel? Why is it spitting everything out on the screen when kernel parameter 'quiet' is present.
Solving the first might as well help the speed issue a bit.
Offline
For getting messages, try:
systemd.show_status=0
As a kernel line parameter.
For the rest of it still post your Blame as a starting point.
Edit: and try it with and without "quiet".
Last edited by headkase (2015-04-30 09:00:02)
Offline
For getting messages, try:
systemd.show_status=0
As a kernel line parameter.
For the rest of it still post your Blame as a starting point.
Edit: and try it with and without "quiet".
That did the trick with the messages. Thanks. I am wondering why quiet does not produce this effect?
As for the blame I will post it as soon as I am in front of the machine.
Offline
You're welcome. Do post your Blame when you can.
Offline
I am wondering why quiet does not produce this effect?
Offline
You're welcome. Do post your Blame when you can.
Here you go...
5.339s NetworkManager-wait-online.service
1.432s man-db.service
345ms dev-sda2.device
298ms NetworkManager.service
207ms systemd-journald.service
131ms systemd-modules-load.service
129ms proc-fs-nfsd.mount
114ms logrotate.service
113ms shadow.service
109ms polkit.service
103ms upower.service
85ms systemd-journal-flush.service
83ms user@1000.service
82ms systemd-random-seed.service
76ms gssproxy.service
76ms wpa_supplicant.service
73ms rpc-statd-notify.service
70ms systemd-tmpfiles-clean.service
62ms home.mount
58ms nfs-config.service
52ms systemd-udevd.service
48ms accounts-daemon.service
41ms boot.mount
36ms var-lib-nfs-rpc_pipefs.mount
31ms systemd-udev-trigger.service
29ms colord.service
28ms udisks2.service
25ms systemd-sysctl.service
25ms gdm.service
20ms systemd-tmpfiles-setup.service
20ms systemd-logind.service
19ms systemd-update-utmp.service
17ms systemd-remount-fs.service
15ms sys-kernel-debug.mount
15ms user@120.service
12ms tmp.mount
10ms dev-hugepages.mount
9ms dev-mqueue.mount
8ms systemd-tmpfiles-setup-dev.service
8ms systemd-vconsole-setup.service
6ms kmod-static-nodes.service
5ms sys-fs-fuse-connections.mount
5ms rtkit-daemon.service
4ms systemd-user-sessions.service
4ms systemd-backlight@backlight:acpi_video0.service
2ms systemd-rfkill@rfkill6.service
2ms systemd-rfkill@rfkill1.service
1ms systemd-backlight@backlight:intel_backlight.service
1ms sys-kernel-config.mount
Please use code text when posting snippets -- Inxsible
Last edited by Inxsible (2015-05-01 14:26:02)
Offline
Please use code tags when pasting to the boards: https://wiki.archlinux.org/index.php/Fo … s_and_code
Offline
It looks like a network issue, try disabling the networkmanager service, reboot and see if that fixes your problem. If it does, investigate why networkmanager hangs
Offline