AnsweredAssumed Answered

Sometimes Eth0 can't recv data when BF609-board powers on

Question asked by HoJuly on Aug 27, 2013
Latest reply on Sep 23, 2013 by Aaronwu

Hi!

    I draw my own board according to the bf609-ezkit, and the ucLinux is almost the default one. When I power on that board, everything seems works fine, and eth0 can be reached through "ping" cmd.

   But if I repower the board again and again(about 40 times), some one time eth0 always can't be reached through "ping". In this situation, I unplug the network cable and pull in again, the board out puts:

 

root:/> PHY: stmmac-0:01 - Link is Down
PHY: stmmac-0:01 - Link is Up - 100/Full

root:/> ping 192.168.61.93
PING 192.168.61.93 (192.168.61.93): 56 data bytes
^C
--- 192.168.61.93 ping statistics ---
319 packets transmitted, 0 packets received, 100% packet loss

root:/> arp -a

? (192.168.61.93) at <incomplete>  on eth0

root:/> ifconfig

can0      Link encap:UNSPEC  HWaddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00 

          UP RUNNING NOARP  MTU:16  Metric:1

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

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

          collisions:0 txqueuelen:10

          RX bytes:48664 (47.5 KiB)  TX bytes:2218 (2.1 KiB)  

eth0      Link encap:Ethernet  HWaddr 02:80:AD:20:31:6B 
          inet addr:192.168.61.107  Bcast:192.168.61.255  Mask:255.255.255.0
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:17 errors:0 dropped:3 overruns:0 frame:0
          TX packets:0 errors:2 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000
          RX bytes:2714 (2.6 KiB)  TX bytes:29232 (28.5 KiB)
          Interrupt:75

lo        Link encap:Local Loopback 
          inet addr:127.0.0.1  Mask:255.0.0.0
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:617 errors:0 dropped:0 overruns:0 frame:0
          TX packets:617 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0
          RX bytes:67490 (65.9 KiB)  TX bytes:67490 (65.9 KiB)

 

  As above says, when I ping again, it says failed.

  But, if I "ifconfig eth0 down", and then "ifconfig eth0 up", it works OK again.

root:/> ifconfig eth0 down

root:/> ifconfig eth0 up

eth0: device MAC address 02:80:ad:20:31:6b

No MAC Management Counters available

root:/> ifconfig eth0 up PHY: stmmac-0:01 - Link is Up - 100/Full

root:/> ping 192.168.61.93

PING 192.168.61.93 (192.168.61.93): 56 data bytes

64 bytes from 192.168.61.93: seq=0 ttl=128 time=1.293 ms

64 bytes from 192.168.61.93: seq=1 ttl=128 time=0.819 ms

64 bytes from 192.168.61.93: seq=2 ttl=128 time=0.762 ms

^C

--- 192.168.61.93 ping statistics ---

3 packets transmitted, 3 packets received, 0% packet loss

round-trip min/avg/max = 0.762/0.958/1.293 ms

root:/>

 

   Why sometimes eth0 fail to send data out?

 

Outcomes