[beagleboard] boot time on image that ships on the Beaglebone AI

GoogleGroups
1

That is on the second boot.

2

My BBAI takes a minute and a half to boot as well. The times look similar to what John Allwine posted.

BB Blue is pretty pokey as well, but not as bad, I don’t think (I’ll have to double check).

3

Still taking about a minute and a half. Any ideas what happened since August last year?

debian@beaglebone:~$ systemd-analyze
Startup finished in 3.901s (kernel) + 1min 30.548s (userspace) = 1min 34.449s
debian@beaglebone:~$ systemd-analyze blame
1min 28.412s generic-board-startup.service
46.345s bb-bbai-tether.service
42.818s dev-mmcblk1p1.device
14.048s systemd-rfkill.service
927ms loadcpufreq.service
861ms systemd-udev-trigger.service

4

Quick comparison, between teh kernel from last august and today:

debian@beaglebone:~$ uname -r ; systemd-analyze
4.14.108-ti-r132
Startup finished in 6.013s (kernel) + 1min 30.734s (userspace) = 1min 36.747s

debian@beaglebone:~$ uname -r ; systemd-analyze
4.14.108-ti-r113
Startup finished in 4.517s (kernel) + 1min 30.544s (userspace) = 1min 35.062s

So that isn't it..

Regards,

5

It's taking 40+ seconds for the brcmfmac driver to load:

Apr 27 14:50:27 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:32 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:37 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:42 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:48 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:52 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:50:57 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:51:02 beaglebone bb-bbai-tether[1610]: bbai:tether waiting
for /sys/class/net/wlan0
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:wlan0:Power Management:off
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [iw phy
phy0 interface add SoftAp0 type __ap]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [phy0 created]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [ip link
set dev SoftAp0 down]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [ip link
set dev SoftAp0 address 28:EC:9A:4C:63:D8]
Apr 27 14:51:07 beaglebone bb-bbai-tether[1610]: bbai:tether [ip link
set dev SoftAp0 up]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [ip addr
add 192.168.8.1/24 broadcast 192.168.8.255 dev SoftAp0]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [iptables
-w -t nat -A POSTROUTING -o wlan0 -j MASQUERADE]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [iptables
-w -A FORWARD -i wlan0 -o SoftAp0 -m state --state RELATED,ESTABLISHE
D -j ACCEPT]
Apr 27 14:51:08 beaglebone bb-bbai-tether[1610]: bbai:tether [iptables
-w -A FORWARD -i SoftAp0 -o wlan0 -j ACCEPT]
Apr 27 14:51:10 beaglebone bb-bbai-tether[1610]: Configuration file:
/tmp/hostapd-bbai.conf
Apr 27 14:51:10 beaglebone bb-bbai-tether[1610]: SoftAp0: Could not
connect to kernel driver
Apr 27 14:51:10 beaglebone bb-bbai-tether[1610]: Using interface
SoftAp0 with hwaddr 28:ec:9a:4c:63:d8 and ssid "BeagleBone-63D8"
Apr 27 14:51:11 beaglebone bb-bbai-tether[1610]: SoftAp0: interface
state UNINITIALIZED->ENABLED
Apr 27 14:51:11 beaglebone bb-bbai-tether[1610]: SoftAp0: AP-ENABLED

Regards,

6

You must be in error! Take a BBB! The webside says: “Boot Linux in under 10 seconds …”:

http://beagleboard.org/black

7

No, that was 10 years ago... Now we are running so much random
application on bootup, and every kernel module enabled...

Regards,

8

How can I disable that driver?

9

The driver is: brcmfmac

That was just an outlier, i moved it to be force loaded on startup
via: /etc/modules-load.d/modules.conf

Which removed the 40second delay, but something else was still slowing
things down. So it didn't change anything.

Anywho, i stopped for today, as day job was getting busy..

Regards,

10

Thanks for looking into it, Robert!

11

I’m pretty much shooting in the dark here, but could this have anything to do with it? I don’t see a /dev/ttyGS0

debian@beaglebone:/etc$ systemctl status serial-getty@ttyGS0.service
● serial-getty@ttyGS0.service - Serial Getty on ttyGS0
Loaded: loaded (/lib/systemd/system/serial-getty@.service; enabled; vendor preset: enabled)
Active: inactive (dead)
Docs: man:agetty(8)
man:systemd-getty-generator(8)
http://0pointer.de/blog/projects/serial-console.html

Apr 27 18:16:17 beaglebone systemd[1]: Dependency failed for Serial Getty on ttyGS0.
Apr 27 18:16:17 beaglebone systemd[1]: serial-getty@ttyGS0.service: Job serial-getty@ttyGS0.service/start failed with result ‘dependency’.

12

I tried just removing that today, no change..

https://github.com/RobertCNelson/boot-scripts/commits/master

Regards,