Hi Josh, After the investigations made by our engineers. It was proven that nothing can be done as a software fix. The power management design of the beaglebone black/green would need a rework for this to be fixed.
We ended up using another board that can cut the power to the BBG when the problem is detected. It was easier for us as a workaround. We did not investigate if the Octavio version (like the blue) had this problem. Sylvain Lamontagne Le 8 avr. 2017 7:49 PM, <[email protected]> a écrit : > Any updates on this? > > I also have tried about a dozen brand new BeagleBone Greens with the > latest Debian 8.7 2017-03-19 > <https://debian.beagleboard.org/images/bone-debian-8.7-lxqt-4gb-armhf-2017-03-19-4gb.img.xz> > images and am still seeing the same problem - the Ethernet port > occasionally does no come up on boot and requires a power cycle to fix it. > The "davinci_mdio 4a101000.mdio: detected phy mask fffffffb" line always > appears when the PHY doesn't come up. > > Is there any recommended work around for 100% Ethernet availability on > power up? I am using these in an application they are very hard to access, > so I am getting desperate and willing to do almost anything to find a > solution. Happy to buy all new boards if there is a rev available somewhere > that resolves this. Also will to do rework on existing boards if there is a > confirmed fix, > > Thanks! > > -josh > > > On Wednesday, October 26, 2016 at 12:24:42 PM UTC-4, slamontagne wrote: >> >> Hi, >> >> I have read this thread as I'm currently having this problem happening to >> me on a BeagleBone Green. >> According to this thread, recent kernel versions should not have a >> problem as there is code that should be able to workaround the hardware >> problem. >> I am currently running: >> - U-Boot 2016.09-00002-g03e9979 >> - Kernel 4.4.26-ti-r59 >> - The image is a derivative of Debian Image 2016-09-04 >> >> When not working: >> Oct 25 00:13:13 beaglebone kernel: [ 3.008530] davinci_mdio >> 4a101000.mdio: davinci mdio revision 1.6 >> Oct 25 00:13:13 beaglebone kernel: [ 3.014688] davinci_mdio >> 4a101000.mdio: detected phy mask fffffffb >> Oct 25 00:13:13 beaglebone kernel: [ 3.021255] davinci_mdio: dt: >> updated phy_id[2] from phy_mask[fffffffb] >> Oct 25 00:13:13 beaglebone kernel: [ 3.034629] libphy: 4a101000.mdio: >> probed >> Oct 25 00:13:13 beaglebone kernel: [ 3.038771] davinci_mdio >> 4a101000.mdio: phy[2]: device 4a101000.mdio:02, driver SMSC LAN8710/LAN8720 >> Oct 25 00:13:13 beaglebone kernel: [ 3.048926] cpsw 4a100000.ethernet: >> Detected MACID = 68:9e:19:98:ab:30 >> Oct 25 00:13:13 beaglebone kernel: [ 3.055733] cpsw 4a100000.ethernet: >> cpts: overflow check period 2125 >> >> When working as expected: >> Oct 25 00:13:13 beaglebone kernel: [ 3.008520] davinci_mdio >> 4a101000.mdio: davinci mdio revision 1.6 >> Oct 25 00:13:13 beaglebone kernel: [ 3.014681] davinci_mdio >> 4a101000.mdio: detected phy mask fffffffe >> Oct 25 00:13:13 beaglebone kernel: [ 3.021252] davinci_mdio: dt: >> updated phy_id[0] from phy_mask[fffffffe] >> Oct 25 00:13:13 beaglebone kernel: [ 3.034618] libphy: 4a101000.mdio: >> probed >> Oct 25 00:13:13 beaglebone kernel: [ 3.038762] davinci_mdio >> 4a101000.mdio: phy[0]: device 4a101000.mdio:00, driver SMSC LAN8710/LAN8720 >> Oct 25 00:13:13 beaglebone kernel: [ 3.048919] cpsw 4a100000.ethernet: >> Detected MACID = 68:9e:19:98:ab:30 >> Oct 25 00:13:13 beaglebone kernel: [ 3.055724] cpsw 4a100000.ethernet: >> cpts: overflow check period 2125 >> >> When it's not working, there is no light on the ethernet port at all and >> we can see the following later in kern.log that would suggest it to be >> working: >> Oct 25 00:13:16 beaglebone kernel: [ 35.124353] net eth0: initializing >> cpsw version 1.12 (0) >> Oct 25 00:13:16 beaglebone kernel: [ 35.129740] net eth0: initialized >> cpsw ale version 1.4 >> Oct 25 00:13:16 beaglebone kernel: [ 35.134940] net eth0: ALE Table >> size 1024 >> Oct 25 00:13:16 beaglebone kernel: [ 35.309306] net eth0: phy found : >> id is : 0x7c0f1 >> >> Here is connmand logs when working: >> Oct 24 18:46:06 beaglebone connmand[1382]: Connection Manager version 1.32 >> Oct 24 18:46:08 beaglebone connmand[1382]: Checking loopback interface >> settings >> Oct 24 18:46:08 beaglebone connmand[1382]: System hostname is beaglebone >> Oct 24 18:46:08 beaglebone connmand[1382]: Failed to open RFKILL control >> device >> Oct 24 18:46:08 beaglebone connmand[1382]: lo {newlink} index 1 address >> 00:00:00:00:00:00 mtu 65536 >> Oct 24 18:46:08 beaglebone connmand[1382]: lo {newlink} index 1 operstate >> 0 <UNKNOWN> >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {create} index 2 type 1 >> <ETHER> >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {update} flags 4098 <DOWN> >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {newlink} index 2 >> operstate 2 <DOWN> >> Oct 24 18:46:08 beaglebone connmand[1382]: Adding interface eth0 [ >> ethernet ] >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {update} flags 36931 >> <UP,RUNNING> >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {newlink} index 2 >> operstate 0 <UNKNOWN> >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {update} flags 36867 <UP> >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 24 18:46:08 beaglebone connmand[1382]: eth0 {newlink} index 2 >> operstate 2 <DOWN> >> Oct 24 18:46:08 beaglebone connmand[1382]: The name net.connman.vpn was >> not provided by any .service files >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {add} route fe80:: gw :: >> scope 0 <UNIVERSE> >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {update} flags 102467 >> <UP,RUNNING,LOWER_UP> >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {newlink} index 2 >> operstate 6 <UP> >> Oct 24 18:46:11 beaglebone connmand[1382]: Skipping disconnect of >> carrier, network is connecting. >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {add} address >> 172.16.1.144/24 label eth0 family 2 >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {add} route 172.16.1.0 gw >> 0.0.0.0 scope 253 <LINK> >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {add} route 172.16.1.1 gw >> 0.0.0.0 scope 253 <LINK> >> Oct 24 18:46:11 beaglebone connmand[1382]: eth0 {add} route 0.0.0.0 gw >> 172.16.1.1 scope 0 <UNIVERSE> >> Oct 24 18:46:12 beaglebone connmand[1382]: eth0 {add} route 82.165.8.211 >> gw 172.16.1.1 scope 0 <UNIVERSE> >> Oct 24 18:46:12 beaglebone connmand[1382]: can0 {newlink} index 3 address >> 00:00:00:00:00:00 mtu 16 >> Oct 24 18:46:12 beaglebone connmand[1382]: can0 {newlink} index 3 >> operstate 2 <DOWN> >> Oct 24 18:46:12 beaglebone connmand[1382]: eth0 {del} route 82.165.8.211 >> gw 172.16.1.1 scope 0 <UNIVERSE> >> Oct 24 18:46:12 beaglebone connmand[1382]: can0 {newlink} index 3 address >> 00:00:00:00:00:00 mtu 16 >> Oct 24 18:46:12 beaglebone connmand[1382]: can0 {newlink} index 3 >> operstate 0 <UNKNOWN> >> Oct 24 18:46:12 beaglebone connmand[1382]: can0 {newlink} index 3 address >> 00:00:00:00:00:00 mtu 16 >> Oct 24 18:46:12 beaglebone connmand[1382]: can0 {newlink} index 3 >> operstate 0 <UNKNOWN> >> >> Here is connmand log when not working: >> Oct 25 00:13:15 beaglebone connmand[1388]: Connection Manager version 1.32 >> Oct 25 00:13:16 beaglebone connmand[1388]: Checking loopback interface >> settings >> Oct 25 00:13:16 beaglebone connmand[1388]: System hostname is beaglebone >> Oct 25 00:13:16 beaglebone connmand[1388]: Failed to open RFKILL control >> device >> Oct 25 00:13:16 beaglebone connmand[1388]: lo {newlink} index 1 address >> 00:00:00:00:00:00 mtu 65536 >> Oct 25 00:13:16 beaglebone connmand[1388]: lo {newlink} index 1 operstate >> 0 <UNKNOWN> >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {create} index 2 type 1 >> <ETHER> >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {update} flags 4098 <DOWN> >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {newlink} index 2 >> operstate 2 <DOWN> >> Oct 25 00:13:16 beaglebone connmand[1388]: Adding interface eth0 [ >> ethernet ] >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {update} flags 36931 >> <UP,RUNNING> >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {newlink} index 2 >> operstate 0 <UNKNOWN> >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {update} flags 36867 <UP> >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {newlink} index 2 address >> 68:9E:19:98:AB:30 mtu 1500 >> Oct 25 00:13:16 beaglebone connmand[1388]: eth0 {newlink} index 2 >> operstate 2 <DOWN> >> Oct 25 00:13:16 beaglebone connmand[1388]: The name net.connman.vpn was >> not provided by any .service files >> Oct 25 00:13:20 beaglebone connmand[1388]: can0 {newlink} index 3 address >> 00:00:00:00:00:00 mtu 16 >> Oct 25 00:13:20 beaglebone connmand[1388]: can0 {newlink} index 3 >> operstate 2 <DOWN> >> Oct 25 00:13:21 beaglebone connmand[1388]: can0 {newlink} index 3 address >> 00:00:00:00:00:00 mtu 16 >> Oct 25 00:13:21 beaglebone connmand[1388]: can0 {newlink} index 3 >> operstate 0 <UNKNOWN> >> Oct 25 00:13:21 beaglebone connmand[1388]: can0 {newlink} index 3 address >> 00:00:00:00:00:00 mtu 16 >> Oct 25 00:13:21 beaglebone connmand[1388]: can0 {newlink} index 3 >> operstate 0 <UNKNOWN> >> >> Still no lights on the eth port. >> >> So my question, is there a patch that is not applied in the kernel that >> you built and that is install when using /opt/scripts/tools/update_kernel.sh >> that should be applied ? Or am I missing something for the workaround to >> actually work ? >> >> What am I missing ? >> >> Any help would be appreciated >> >> Sylvain Lamontagne >> > -- > For more options, visit http://beagleboard.org/discuss > --- > You received this message because you are subscribed to a topic in the > Google Groups "BeagleBoard" group. > To unsubscribe from this topic, visit https://groups.google.com/d/ > topic/beagleboard/9mctrG26Mc8/unsubscribe. > To unsubscribe from this group and all its topics, send an email to > [email protected]. > To view this discussion on the web visit https://groups.google.com/d/ > msgid/beagleboard/9b968807-d5bd-408c-94b7-cfabeeca229b%40googlegroups.com > <https://groups.google.com/d/msgid/beagleboard/9b968807-d5bd-408c-94b7-cfabeeca229b%40googlegroups.com?utm_medium=email&utm_source=footer> > . > For more options, visit https://groups.google.com/d/optout. > -- 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/CACBM16%3DomMJxD8z_xE9bF_us%3Du%2B3nhkKOPuLNiYwmdU9hrgd1A%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
