Hmmm - I get something similar on three boards I have here (2 x A5B and 1 x A5A). I was in the process of adding more info when you posted.
If I connect via serial debug cable then I can get more info:
So I start from scratch and boot normally then unplug LAN for just a few seconds, I get this via dmesg:
[ 99.785921] libphy: 4a101000.mdio:00 - Link is Down
[ 101.324323] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[ 101.859369] libphy: 4a101000.mdio:00 - Link is Up - 100/Full
[ 101.859425] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready
and you can see it is working again - presumably after the 5 seconds restart. I can do this multiple times providing I do not exceed 5 seconds.
If however I unplug for more than a few seconds (i.e. longer than the 5 sec restart time), dmesg then gives:
[ 142.098320] libphy: 4a101000.mdio:00 - Link is Down
[ 144.529396] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
and I cannot use LAN again.
If I then do:
systemctl restart connman.service
I get a message appear as follows:
[ 212.282752] libphy: PHY 4a101000.mdio:01 not found
[ 212.287820] net eth0: phy 4a101000.mdio:01 not found on slave 1
and if I then do dmesg I get something similar to you:
[ 212.068744] Bridge firewalling registered
[ 212.279445] net eth0: initializing cpsw version 1.12 (0)
[ 212.282723] net eth0: phy found : id is : 0x7c0f1
[ 212.282752] libphy: PHY 4a101000.mdio:01 not found
[ 212.287820] net eth0: phy 4a101000.mdio:01 not found on slave 1
[ 212.303499] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
I wonder if it has got something to do with the firewalling it mentions? - I am not connecting via USB although I am powering via USB.
if I do:
systemctl status connman.service
I get:
connman.service - Connection service
\0x09 Loaded: loaded (/lib/systemd/system/connman.service; enabled)
\0x09 Active: \0x1b[1;32mactive (running)\0x1b[0m since Tue 2013-06-18 14:06:46 BST; 9min ago
\0x09Main PID: 379 (connmand)
\0x09 CGroup: name=systemd:/system/connman.service
\0x09\0x09 `-379 /usr/sbin/connmand -n
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: usb0 {update} flags…>
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: usb0 {newlink} inde…0
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: usb0 {newlink} inde…>
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: Adding interface us…]
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: eth0 {RX} 195 packe…s
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: eth0 {TX} 114 packe…s
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: eth0 {update} flags…>
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: eth0 {newlink} inde…0
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: eth0 {newlink} inde…>
Jun 18 14:06:46 beaglebone connmand[379]: connmand[379]: usb0 {add} address …2
I thought about compiling the latest connman from source but it started throwing out DBus error messages during coompilation.