Thank you for the Reply lkoziarz
systemd-analyze blame
5.745s systemd-logind.service
4.722s ofono.service
4.187s systemd-udev-trigger.service
1.695s user@0.service
1.279s iptables.service
5.745s systemd-logind.service
4.722s ofono.service
4.187s systemd-udev-trigger.service
1.695s user@0.service
1.279s iptables.service
1.274s systemd-journald.service
898ms systemd-backlight@backlight:backlight.service
897ms sys-kernel-debug.mount
889ms kmod-static-nodes.service
874ms tmp.mount
861ms dev-mqueue.mount
785ms systemd-udevd.service
720ms systemd-update-utmp.service
703ms systemd-remount-fs.service
703ms systemd-modules-load.service
647ms systemd-networkd.service
647ms connman.service
531ms rpcbind.service
441ms wpa_supplicant.service
388ms systemd-tmpfiles-setup.service
374ms sys-fs-fuse-connections.mount
342ms sys-kernel-config.mount
339ms systemd-update-utmp-runlevel.service
313ms user-runtime-dir@0.service
303ms systemd-sysctl.service
301ms systemd-tmpfiles-setup-dev.service
276ms systemd-journal-flush.service
192ms systemd-random-seed.service
161ms var-volatile.mount
156ms systemd-user-sessions.service
103ms systemd-tmpfiles-clean.service
And we tried with turn off console logging during boot it will reduce 3 seconds.And we want to know where are the bootup information messages will store?
we checked with var/log/ but there is no such file to store the bootup information.
