BeagleBone Debian boot time (IPV6, ethernet..)

[Boris Ostrovskiy]

It takes my beaglebone ~70seconds to fully boot. Looking at "dmesg" it seems like most of that time is spent setting up / loading network functionality. I do need the ethernet connection but is there a way to speed up the process...?

root@beaglebone:~# dmesg
[    0.000000] Booting Linux on physical CPU 0x0
[    0.000000] Initializing cgroup subsys cpu
[    0.000000] Linux version 3.8.13-bone50 (root@imx6q-wandboard-2gb-0) (gcc version 4.6.3 (Debian 4.6.3-14) ) #1 SMP Tue May 13 13:24:52 UTC 2014
[    0.000000] CPU: ARMv7 Processor [413fc082] revision 2 (ARMv7), cr=50c5387d
[    0.000000] CPU: PIPT / VIPT nonaliasing data cache, VIPT aliasing instruction cache
[    0.000000] Machine: Generic AM33XX (Flattened Device Tree), model: TI AM335x BeagleBone
[    0.000000] Memory policy: ECC disabled, Data cache writeback
[    0.000000] On node 0 totalpages: 130816
..........................
[   12.266913] usb usb2: bus auto-suspend, wakeup 1
[   20.098980] IPv6: ADDRCONF(NETDEV_UP): usb0: link is not ready
[   47.160094] net eth0: initializing cpsw version 1.12 (0)
[   47.164737] net eth0: phy found : id is : 0x7c0f1
[   47.164794] libphy: PHY 4a101000.mdio:01 not found
[   47.170095] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   47.185951] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   50.239902] libphy: 4a101000.mdio:00 - Link is Up - 100/Half
[   50.240024] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
[   66.874349] net eth0: initializing cpsw version 1.12 (0)
[   66.878716] net eth0: phy found : id is : 0x7c0f1
[   66.878776] libphy: PHY 4a101000.mdio:01 not found
[   66.884045] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   66.896224] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   67.442350] net eth0: initializing cpsw version 1.12 (0)
[   67.448162] net eth0: phy found : id is : 0x7c0f1
[   67.448194] libphy: PHY 4a101000.mdio:01 not found
[   67.453288] net eth0: phy 4a101000.mdio:01 not found on slave 1
[   67.463303] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[   69.454875] libphy: 4a101000.mdio:00 - Link is Up - 100/Half
[   69.454992] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

[Robert Nelson]

On Thu, Jan 22, 2015 at 4:18 PM, Boris Ostrovskiy <bori...@gmail.com> wrote:
> It takes my beaglebone ~70seconds to fully boot. Looking at "dmesg" it seems
> like most of that time is spent setting up / loading network functionality.
> I do need the ethernet connection but is there a way to speed up the
> process...?

Yeap... cpsw/eth0 is a dog on bootup with 3.8.13... it's faster
anywhere else, v3.14.x-ti & mainline..

>
> root@beaglebone:~# dmesg
> [ 0.000000] Booting Linux on physical CPU 0x0
> [ 0.000000] Initializing cgroup subsys cpu
> [ 0.000000] Linux version 3.8.13-bone50 (root@imx6q-wandboard-2gb-0) (gcc

Well in 'bone51' we got 1.6 second reduction with lzo:

https://github.com/RobertCNelson/bb-kernel/commit/4e5e3d4ec6cb3b80361ab1d69a463ec71e87ddad

anywho... current release is "bone69" with "bone70" just hitting the
build farm..

Regards,

--
Robert Nelson
http://www.rcn-ee.com/

[fta...@gmail.com]

On Thursday, January 22, 2015 at 5:18:09 PM UTC-5, Boris Ostrovskiy wrote:

It takes my beaglebone ~70seconds to fully boot. Looking at "dmesg" it seems like most of that time is spent setting up / loading network functionality. I do need the ethernet connection but is there a way to speed up the process...?

For numbers I list below, I define boot time as the time from when power is applied to when I get to a login prompt on a serial console.  I'm running 3.8.13-bone69 on a beaglebone black rev c.   With eth0 setup for auto and dhcp in the interfaces file, it takes my board about 77 seconds to boot.  I can reduce that time to 11 seconds by making the following changes:

1) disable auto for eth0. ie change in /etc/network/interfaces "auto eth0" to "#auto eth0"
2) add the line "ifup eth0;"  to /etc/rc.local. 
 
With these changes, I consistently get boot times in the 10 to 11 second range and eth0 gets its ip address from a dhcp server. 

frank agius
 

[richfd...@gmail.com]

My ISP in the US runs IP4 and releases every 2 mins,  and IPv6 runs fine with out issue. 

At first the printer did not work and other things but it is all good now.

Except for the Beagle Board Blue. I load the SD, and the light shows up,  and repeats it self in the middle of the blue led array for ever.

Is there a way to fix this.  or hard code an IP4 and  IP6 at once.