[netperf-talk] When test some times the network card download

[Rick Jones]

liuhu wrote:
> Hi Rick,
>             I use netperf test on ARM board ,the network work module is 
> 10M half/full duplex. but test
>  
> some times appear the following  phenomenon:
>  
> TCP STREAM TEST from 0.0.0.0 (0.0.0.0) port 0 AF_INET to 192.168.1.2 
> (192.168.1.2) port 0 AF_INET
> *NETDEV WATCHDOG: eth0: transmit timed out
> netperf: receive_response: no response received. errno 0 counter 0*
> ....................
> The TCP_STREAM result:
> *establish control: are you sure there is a netserver listening on 
> 192.168.1.2 at port 12865?
> establish_control could not establish the control connection from 
> 0.0.0.0 port 0 address family AF_UN
> SPEC to 192.168.1.2 port 12865 address family AF_UNSPEC
> *eth0      Link encap:Ethernet  HWaddr 00:00:EB:FA:02:13 
>           inet addr:192.168.1.7  Bcast:192.168.1.255  Mask:255.255.255.0
>           UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>           RX packets:60330 errors:26929 dropped:0 overruns:26929 frame:0
>           TX packets:1845293 errors:446 dropped:0 overruns:4 carrier:442
>           collisions:0 txqueuelen:1000

It looks very odd to me that you have a NIC in half-duplex and no collisions 
reported.  Also, those are rather large numbers of errors, overruns and (loss 
of) carrier events.  Definitely _not_ a happy network.

>           RX bytes:4116539 (3.9 Mb)  TX bytes:2755830578 (2628.1 Mb)
>           Interrupt:4 Base address:0xe300 DMA chan:ff
>  
> lo        Link encap:Local Loopback 
>           UP LOOPBACK RUNNING  MTU:16436  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:0
>           RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)
>  
> then the follow test can not go on.
>  
> Why the network card eth0 transmit timed out?

Typically, it means there is a bug in the driver, or a hardware fault.  You may 
need to contact the HW vendor.


> Why the netperf receive_response?

Since the NIC isn't working, traffic is not flowing on the control connection. 
Netperf was expecting something on the control connection and timed-out

> It's my ARM board driver question or another ?

Either the driver, the hardware, or even the network itself - or a combination 
of all of them.

rick jones