The first big gap is likely due to an initrd image.   For my apps, we do a 
"rm -rf /boot/initrd.img*" after creating the image which easily cuts 10 
seconds or so off of boot time.

After boot, you can run "systemd-analyze plot > plot.svg" and view the svg 
to see what's going on.   I definitely found a few of our own scripts were 
taking a LONG time but splitting them into separate services that can be 
run in parallel helped a lot.

On Tuesday, March 3, 2020 at 2:46:13 PM UTC-5, Hans Leeuw wrote:
>
> Hi all,
>
> I am following this discussion with great interest. I am using the 
> PocketBeagle on a musical instrument and it should not take too long to 
> start it up or I miss that all important firsts note!! I am using a 
> PocketBeagle with Linux beaglebone 4.14.108-ti-r127 #1 SMP PREEMPT Wed 
> Jan 29 04:10:14 UTC 2020 armv7l GNU/Linux. I used the console image from e
> linux.org.
> I see a few big gaps in the start up as well. Apart from the filesystem 
> mount which takes a long time (in my case 16+ seconds), there is also a 
> huge gap before the PRU comes online (a gap of 28 seconds!!!). I am 
> suspecting the Edimax USB Wifi driver since I see the same even larger gap 
> on my other (standard) image around the startup of that device. Is this 
> normal, is this something to report or does anyone know a solution or 
> direction in which to look?
>
> dmesg
>
> ......
>
> [    1.438453] usb 2-1: new high-speed USB device number 2 using musb-hdrc
>
> [    1.586756] usb 2-1: New USB device found, idVendor=1a40, 
> idProduct=0101
>
> [    1.586773] usb 2-1: New USB device strings: Mfr=0, Product=1, 
> SerialNumber=0
>
> [    1.586781] usb 2-1: Product: USB 2.0 Hub
>
> [    1.587979] hub 2-1:1.0: USB hub found
>
> [    1.588121] hub 2-1:1.0: 4 ports detected
>
> [    1.590052] PM*: bootloader does not support rtc-only!*
>
> [   18.885434] EXT4-fs (mmcblk0p1): mounted filesystem with ordered data 
> mode. Opts: (null)
>
> [   19.524350] systemd[1]: System time before build time, advancing clock.
>
> [   19.629059] ip_tables: (C) 2000-2006 Netfilter Core Team
>
> [   19.670063] systemd[1]: systemd 232 running in system mode. (+PAM 
> +AUDIT +SELINUX +IMA +APPARMOR +SMACK +SYSVINIT +UTMP +LIBCRYPTSETUP 
> +GCRYPT +GNUTLS +ACL +XZ +LZ4 +SECCOMP +BLKID +ELFUTILS +KMOD +IDN)
>
> [   19.671004] systemd[1]: Detected architecture arm.
>
> [   19.673162] systemd[1]: Set hostname to <beaglebone>.
>
> [   20.251318] systemd[1]: Listening on fsck to fsckd communication 
> Socket.
>
> [   20.252772] systemd[1]: Listening on Journal Audit Socket.
>
> [   20.253398] systemd[1]: Started Forward Password Requests to Wall 
> Directory Watch.
>
> [   20.253851] systemd[1]: Listening on udev Control Socket.
>
> [   20.255661] systemd[1]: Created slice System Slice.
>
> [   20.260328] systemd[1]: Mounting /sys/kernel/debug...
>
> [   20.262000] systemd[1]: Created slice system-getty.slice.
>
> [   21.187890] EXT4-fs (mmcblk0p1): re-mounted. Opts: errors=remount-ro
>
> [   21.782096] systemd-journald[1387]: Received request to flush runtime 
> journal from PID 1
>
> [   25.913687] nf_conntrack version 0.5.0 (8192 buckets, 32768 max)
>
> [   27.173192] *using random self ethernet address*
>
> [   27.173212] *using random host ethernet address*
>
> [   27.387371] *using random self ethernet address*
>
> [   27.387390] *using random host ethernet address*
>
> [   27.491447] usb0: HOST MAC 5a:4e:7b:a0:01:c1
>
> [   27.495152] usb0: MAC 52:08:20:37:1b:cf
>
> [   27.502656] usb1: HOST MAC 0e:0d:48:41:f9:e3
>
> [   27.502828] usb1: MAC ea:2d:e9:92:95:d8
>
> [   27.823542] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
>
> [   27.928126] IPv6: ADDRCONF(NETDEV_UP): usb1: link is not ready
>
> [   29.902568] usb 1-1: new high-speed USB device number 2 using musb-hdrc
>
> [   30.051126] usb 1-1: New USB device found, idVendor=7392, 
> idProduct=b822
>
> [   30.051147] usb 1-1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
>
> [   30.051156] usb 1-1: Product: AC1200 MU-MIMO USB2.0 Adapter
>
> [   30.051164] usb 1-1: Manufacturer: Realtek
>
> [   30.051171] usb 1-1: SerialNumber: 123456
>
> [   58.475688] pruss 4a300000.pruss: creating PRU cores and other child 
> platform devices
>
> [   59.117552] remoteproc remoteproc1: 4a334000.pru is available
>
> [   59.117694] pru-rproc 4a334000.pru: PRU rproc node 
> /ocp/pruss_soc_bus@4a326004/pruss@0/pru@34000 probed successfully
>
> [   59.147747] remoteproc remoteproc2: 4a338000.pru is available
>
> [   59.147890] pru-rproc 4a338000.pru: PRU rproc node 
> /ocp/pruss_soc_bus@4a326004/pruss@0/pru@38000 probed successfully
>
> [   59.868881] 88x2bu*: loading out-of-tree module taints kernel.*
>
> [   60.536781] RTW*: module init start*
>
> [   60.536803] RTW*: rtl88x2bu v5.3.1_27678.20180430_COEX20180427-5959*
>
> [   60.536808] RTW*: rtl88x2bu BT-Coex version = COEX20180427-5959*
>
> [   60.536887] RTW*: rtw_inetaddr_notifier_register*
>
>
> On standard image
>
>
> [   39.810511] usb 1-1: new high-speed USB device number 2 using musb-hdrc
>
> [   39.979050] usb 1-1: New USB device found, idVendor=7392, idProduct=b822
>
> [   40.010480] usb 1-1: New USB device strings: Mfr=1, Product=2, 
> SerialNumber=3
>
> [   40.039314] usb 1-1: Product: AC1200 MU-MIMO USB2.0 Adapter
>
> [   40.066515] usb 1-1: Manufacturer: Realtek
>
> [   40.078152] usb 1-1: SerialNumber: 123456
>
> [   74.239144] [drm] Initialized pvr 1.14.3699939 20110701 for 
> 56000000.sgx on minor 1
>
> [   78.924470] RTW: module init start
>
> [   78.934546] RTW: rtl88x2bu v5.3.1_27678.20180430_COEX20180427-5959
>
> [   78.946541] RTW: rtl88x2bu BT-Coex version = COEX20180427-5959
>
> [   78.960099] RTW: rtw_inetaddr_notifier_register
>
>
>
> Best,
>
> Hans Leeuw
>
>

-- 
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 [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/beagleboard/9649b553-f5f6-4351-8f6c-8b062d45b009%40googlegroups.com.

Reply via email to