Hi Robert,
Thanks for reminding me of systemd-analyze. Completely forgot about that.
Here is the output of the command
=====================================================================
62389ms networking.service
2819ms bootlogs.service
2533ms loadcpufreq.service
2402ms ssh.service
2271ms xrdp.service
2203ms cron.service
2059ms console-kit-daemon.service
1236ms avahi-daemon.service
1205ms connman.service
1181ms wpa_supplicant.service
1120ms systemd-logind.service
1086ms connman-vpn.service
1027ms boot_scripts.service
961ms rc.local.service
958ms capemgr.service
862ms udev-trigger.service
689ms motd.service
677ms udhcpd.service
576ms udev.service
469ms cpufrequtils.service
442ms console-kit-log-system-start.service
412ms alsa-utils.service
408ms systemd-modules-load.service
356ms screen-cleanup.service
314ms systemd-user-sessions.service
293ms hostapd.service
282ms sys-kernel-debug.mount
256ms sys-kernel-security.mount
254ms dev-mqueue.mount
243ms systemd-sysctl.service
240ms hdparm.service
231ms run-lock.mount
230ms systemd-tmpfiles-setup.service
219ms run-user.mount
193ms pppd-dns.service
128ms systemd-remount-api-vfs.service
113ms boot-uboot.mount
66ms remount-rootfs.service
48ms console-setup.service
38ms sys-fs-fuse-connections.mount
37ms keyboard-setup.service
==========================================================================
So it looks like networking.service is eating up all the time. Is it safe
to disable this service with connman installed?
On Thursday, April 10, 2014 1:34:02 AM UTC+5:30, RobertCNelson wrote:
>
> On Wed, Apr 9, 2014 at 2:44 PM, <vira...@gmail.com <javascript:>> wrote:
> > Hi Robert,
> >
> > Here is the pastebin of one of my custom built image's dmesg output.
> > http://paste.debian.net/92787/
> >
> > As you can see in the log, there is no log from around 6 second in the
> boot
> > process to 70 second of the boot process. For this time, the BBB just
> > doesn't respond and after that it resumes booting.
> >
> > For this image I have removed connman, wicd at image creation time but
> have
> > added them back after booting for the first time. The image still takes
> > around a minute to boot. http://paste.debian.net/92791/ is the pastebin
> url
> > with connman
> >
> > Please help me in optimizing boot timing.
>
> Two things come to mind... openssh-server key regeneration: (this
> only occurs on the first boot)
>
> root@beaglebone:~# rm -rf /etc/ssh/ssh_host_*
> root@beaglebone:~# time dpkg-reconfigure openssh-server
> Creating SSH2 RSA key; this may take some time ...
> Creating SSH2 DSA key; this may take some time ...
> Creating SSH2 ECDSA key; this may take some time ...
> [ ok ] Restarting ssh (via systemctl): ssh.service.
>
> real 0m13.760s
> user 0m10.813s
> sys 0m0.893s
>
> but the other 50 some seconds..
>
> So factory image: (wicd)
> http://paste.debian.net/92793/
>
> btw, systemd provides a nice tool to help debug this:
>
> systemd-analyze
>
> Using:
> systemd-analyze blame
>
> http://paste.debian.net/92798/
>
> Regards,
>
> --
> Robert Nelson
> http://www.rcn-ee.com/
>
--
For more options, visit http://beagleboard.org/discuss
---
You received this message because you are subscribed to the Google Groups
"BeagleBoard" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to beagleboard+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
