AnsweredAssumed Answered

IMX6UL-EVK 'eth1' interface does not become ready after Linux reboot

Question asked by Vitaliy Avramenko on Jun 29, 2016

Hello,

I could see one issue with U-Boot/Linux binaries  I had run on my IMX6UL-EVK board

that came from L4.1.15_1.1.0_ga_images_MX6ULEVK.tar.gz

 

U-Boot 2015.04-imx_v2015.04_4.1.15_1.0.0_ga+gd7d7c43 (Apr 01 2016 - 10:17:30)

...

Linux version 4.1.15-1.1.0+ga4d2a08 (bamboo@shlinux12) (gcc version 5.2.0 (GCC) ) #1 SMP PREEMPT Fri Apr 1 05:37:10 CST 2016

...

 

At Power ON  "eth1' interface always starts without problems.

But If I execute a 'reboot' command  then 'eth1' does not start permanently.


fec 2188000.ethernet eth1: Freescale FEC PHY driver [Generic PHY] (mii_bus:phy_addr=20b4000.ethernet:02, irq=-1)

IPv6: ADDRCONF(NETDEV_UP): eth1: link is not ready

 

'ifconfig -a' shows

eth1      Link encap:Ethernet  HWaddr 00:04:9F:04:20:01

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

 

 

I have tried to connect 'eth1' of my board to 3 different routers and switches.

The results are the same and negative.  The 'eth1' link does not become ready.

With kernels Linux 4.6 and 4.6.3 I have not seen that issue.

 

Any help would be appreciated

Thanks in advance

I could see one minor issue even with

Linux 4.1.15 from  http://git.freescale.com/git/cgit.cgi/imx/linux-2.6-imx.git/log/?h=imx_4.1.15_1.0.0_ga

At Power ON  "eth1' interface always starts without problems.

But If I execute a 'reboot' command  then 'eth1' periodically does not start.

'ifconfig -a' shows

eth1      Link encap:Ethernet  HWaddr 00:04:9F:04:20:01

          BROADCAST MULTICAST  MTU:1500  Metric:1

          RX packets:0 errors:0 dropped:0 overruns:0 frame:0

          TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

          collisions:0 txqueuelen:1000

          RX bytes:0 (0.0 B)  TX bytes:0 (0.0 B)

With kernels 4.6 and 4.6.3 I have not seen that issue.

 

Outcomes