AnsweredAssumed Answered

Between bootarg and systemd service

Question asked by vinothkumar s on Feb 23, 2019
Latest reply on Feb 27, 2019 by Victor Linnik

Hi All,

 

I am working on imx6solo + Orion Linux. I got some observation when setting boot argument.

 

i> ii> bootarg with ip parameter

 

if "setenv bootargs 'console=ttymxc0,115200  ip=dhcp  nosmp root=/dev/mmcblk2p1 rootwait'"

 

systemd-analyze blame

54.909s systemd-journald.service
48.501s dev-mmcblk0p1.device
16.426s systemd-journal-flush.service
10.382s udev-trigger.service
9.470s systemd-tmpfiles-setup.service
9.398s systemd-timesyncd.service
8.495s systemd-udevd.service
6.603s systemd-update-utmp.service
3.911s systemd-logind.service
3.527s remount-rfs-rw.service
3.448s systemd-tmpfiles-setup-dev.service
3.303s sys-fs-fuse-connections.mount
3.139s systemd-sysctl.service
2.358s systemd-remount-fs.service
2.175s udev.service
1.590s sys-kernel-debug.mount
1.369s systemd-random-seed.service
1.210s tmp.mount
1.113s systemd-update-utmp-runlevel.service
193ms systemd-networkd.service
191ms systemd-resolved.service

 

ii> bootarg without ip parameter

 

if "setenv bootargs 'console=ttymxc0,115200 nosmp root=/dev/mmcblk2p1 rootwait'"

 

systemd-analyze blame

5.306s systemd-udev-trigger.service
5.293s dev-mmcblk0p1.device
3.332s systemd-journald.service
3.258s systemd-timesyncd.service
3.208s systemd-journal-flush.service
2.226s systemd-tmpfiles-setup.service
2.002s systemd-update-utmp.service
1.440s systemd-udevd.service
1.321s systemd-sysusers.service
1.065s udev-trigger.service
867ms sys-fs-fuse-connections.mount
864ms systemd-update-utmp-runlevel.service
769ms systemd-remount-fs.service
768ms sys-kernel-debug.mount
742ms systemd-sysctl.service
738ms remount-rfs-rw.service
708ms systemd-tmpfiles-setup-dev.service
641ms systemd-update-done.service
353ms udev.service
258ms systemd-journal-catalog-update.service
231ms ldconfig.service
117ms systemd-random-seed.service

 

 

What could be the reason ?

 

 

Regards,

VinothS

Outcomes