0
jhcarter

CuBox i4 Pro Ethernet Failure with MDIO read timeout

Recommended Posts

I am running Armbian_4.5_Cubox-i_Ubuntu_trusty_3.14.54 on a CuBox i4 Pro.  The application is a security camera server and the current test environment consists of the server and two IP cameras set to 320x240 and running at 5 fps.  The server is receiving these two streams over the Ethernet interface constantly but the data rate is pretty low.  I am seeing the Ethernet interface fail after 24 to 48 hours with the syslog entries shown below.  After the failure I can restart the link with ifdown/ifup and it works fine.

 

Has anyone else seen a similar issue?

Oct 29 11:56:09 localhost kernel: [    0.505433] libphy: fec_enet_mii_bus: probed
Oct 29 11:56:09 localhost kernel: [    0.505892] fec 2188000.ethernet eth0: registered PHC device 0
Oct 29 11:56:09 localhost kernel: [    3.832211] fec 2188000.ethernet eth0: Freescale FEC PHY driver [Atheros 8035 ethernet] (mii_bus:phy_addr=2188000.ethernet:04, irq=-1)
Oct 29 11:56:11 localhost kernel: [    6.837655] libphy: 2188000.ethernet:04 - Link is Up - 100/Full
Oct 30 03:17:01 localhost kernel: [55253.929843] fec 2188000.ethernet eth0: MDIO read timeout
Oct 30 03:17:03 localhost kernel: [55255.940256] libphy: 2188000.ethernet:04 - Link is Down

Share this post


Link to post
Share on other sites

This happened two times over a few days just prior to my initial post.  In an effort to be sure I have a repeatable failure test case I have let it run since that time with few reboots and with the original 3.14.54 kernel and it has not failed again.  I must assume at this point that there was some external influence at work with the initial two failures.   

Share this post


Link to post
Share on other sites
Guest
This topic is now closed to further replies.
0