AnsweredAssumed Answered

FEC: MDIO read timeout, mii_id=1

Question asked by Raana on Mar 20, 2013
Latest reply on Apr 7, 2013 by Yuri Muhin
Branched to a new discussion

Hi,

 

Currently am working on Gigabit Ethernet on i.MX6 Dual Lite/Solo, (Q/D compatible)

 

Console print:

--------------------

root@iWave-G15M /$ udhcpc

udhcpc (v1.20.2) started

eth0: Freescale FEC PHY driver [Micrel KSZ9021 Gigabit PHY] (mii_bus:phy_addr=1:01, irq=-1)

Sending discover...

PHY: 1:01 - Link is Up - 100/Full

Sending discover...

Sending select for 192.168.2.216...

Lease of 192.168.2.216 obtained, lease time 43200                                               

Deleting routers                                                                                

adding dns 192.168.2.37                                                                         

adding dns 202.138.96.2                                                                         

adding dns 202.138.103.100

adding dns 220.225.236.84

adding dns 220.225.236.85

adding dns 8.8.8.8

adding dns 121.242.190.180

adding dns 121.242.190.211

adding dns 192.168.2.194

root@iWave-G15M /$

 

After some fraction of second the Link is going down and again up

it's coming continuously

 

Console print

-------------------

root@iWave-G15M /$ PHY: 1:01 - Link is Down

PHY: 1:01 - Link is Up - 100/Full

PHY: 1:01 - Link is Down

PHY: 1:01 - Link is Up - 100/Full

 

Later, I tried to ping with some other IP

In between the ping print MDIO Timeout also coming

 

Console print

--------------------

root@iWave-G15M /$ ping 192.168.2.37

PING 192.168.2.37 (192.168.2.37): 56 data bytes

64 bytes from 192.168.2.37: seq=0 ttl=64 time=0.422 ms

64 bytes from 192.168.2.37: seq=1 ttl=64 time=0.316 ms

FEC: MDIO read timeout, mii_id=1

64 bytes from 192.168.2.37: seq=2 ttl=64 time=0.317 ms

64 bytes from 192.168.2.37: seq=3 ttl=64 time=0.305 ms

64 bytes from 192.168.2.37: seq=2 ttl=64 time=0.317 ms

FEC: MDIO read timeout, mii_id=1

FEC: MDIO read timeout, mii_id=1

64 bytes from 192.168.2.37: seq=3 ttl=64 time=0.305 ms

 

Is it an issue or warning ???

If this is an issue means How to recover ???


Thanks in Advance

Regards,

J.P.Raja

Outcomes