You are not logged in.
Could you try disabling read-ahead without a nonpersistent journal? It might be interesting to know which of them causes this. Maybe you could also report this upstream and see if they have any debug-ideas. They might be able to fix this (for everyone to enjoy)
Thanks, the journald.conf's persistent mod was the problem. That was the "pause" in my plot file.
With readahead I won 1~2 sec so I disabled totally.
Why systemd says 13 seconds boottime(5 kernel + 8 user) and the realtime is ~25 seconds?
The kernel line's logs are disappears (I think this is the end of userspace) and I have ~10 sec black screen.
Startup finished in 4.613s (kernel) + 7.813s (userspace) = 12.427s
5.335s lightdm.service
3.517s systemd-logind.service
1.460s systemd-vconsole-setup.service
885ms systemd-udev-trigger.service
719ms systemd-sysctl.service
718ms sys-kernel-debug.mount
538ms colord.service
524ms alsa-restore.service
504ms udisks2.service
480ms kmod-static-nodes.service
347ms dhcpcd.service
317ms run-media-i\x2dsty-Egyeb.mount
299ms dev-mqueue.mount
299ms sys-kernel-config.mount
297ms dev-hugepages.mount
296ms systemd-remount-fs.service
231ms systemd-tmpfiles-setup.service
218ms polkit.service
180ms systemd-user-sessions.service
114ms user@1000.service
99ms systemd-journal-flush.service
89ms systemd-tmpfiles-setup-dev.service
63ms systemd-random-seed.service
58ms bluetooth.service
53ms systemd-update-utmp.service
19ms systemd-udevd.service
15ms rtkit-daemon.service
12ms sys-fs-fuse-connections.mount
2ms systemd-tmpfiles-clean.service
2ms tmp.mount
2ms var-tmp.mount
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 @7.812s
└─lightdm.service @2.476s +5.335s
└─systemd-user-sessions.service @2.293s +180ms
└─basic.target @2.283s
└─timers.target @2.281s
└─systemd-tmpfiles-clean.timer @2.281s
└─sysinit.target @2.247s
└─systemd-vconsole-setup.service @785ms +1.460s
└─systemd-journald.socket @783ms
└─-.mount @782ms
└─system.slice @1.502s
└─-.slice @1.501s
Last edited by I-sty (2014-02-23 18:27:50)
Offline
Beside the hints depending systemd: if you are using ext4 with a hdd, I suggest to have a look at e4rat. You can greatly decrease your boot time with this. Before I've got an ssd it worked very well for me.
Thanks for sharing. I never heard of this before!
However, does this only work if your /boot partition is formatted with ext4?
What if you are using ext2? Is there any similar program for ext2?
Offline