Hi, I was using my micro2440 and faced a curious fact. Sometimes the ping from my machine to micro2440 suddenly stop for some seconds (~30s). During this time, I can't use telnet, cgi or any other kind of tcp connection. Here are some informations: PC: Ubuntu 8.04. micro2440: default kernel/rootfs - 2.6.32.2 PC ip: 192.168.0.21 micro2440 ip: 192.168.0.250 Ping log (PC -> micro2440): ... 64 bytes from 192.168.0.250: icmp_seq=195 ttl=64 time=0.335 ms 64 bytes from 192.168.0.250: icmp_seq=196 ttl=64 time=0.333 ms 64 bytes from 192.168.0.250: icmp_seq=197 ttl=64 time=0.324 ms [ * freeze time *] [waiting for some seconds] [then, the micro2440 respond the ping] 64 bytes from 192.168.0.250: icmp_seq=218 ttl=64 time=0.398 ms 64 bytes from 192.168.0.250: icmp_seq=219 ttl=64 time=0.395 ms 64 bytes from 192.168.0.250: icmp_seq=220 ttl=64 time=0.401 ms ... --- 192.168.0.250 ping statistics --- 225 packets transmitted, 197 received, 12% packet loss, time 224084ms rtt min/avg/max/mdev = 0.244/0.369/4.511/0.298 ms There is another information that could help. During this "freeze" time, if I ping from micro2440 to my machine, the ping from my machine to micro2440 works again, and the telnet became available again. Ping log (micro2440 -> PC): [root@FriendlyARM /]# ping 192.168.0.21 PING 192.168.0.21 (192.168.0.21): 56 data bytes 64 bytes from 192.168.0.21: seq=0 ttl=64 time=0.875 ms 64 bytes from 192.168.0.21: seq=1 ttl=64 time=0.619 ms 64 bytes from 192.168.0.21: seq=2 ttl=64 time=0.530 ms ^C --- 192.168.0.21 ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max = 0.530/0.674/0.875 ms This could be something related to hardware (dm9000 component)? Thanks in advance
micro 2440 doesn't respond ping request some times
I did some tests and find out that this error don't occur in a small lan. Maybe the tcp component can't support a massive qtty of data from a big lan (broadcasts, ping,...). Anyway, now it's working. Hope it helps if anybody get the same problem.