Strange ping timings

Hello,

I'm running a ultra1 with Suse 7.3 ,Kernel 2.4 and
hme ethernet driver.

So far, everything works fine, but sometimes my
eth0 hangs up. If I make a network restart/reload
it still hangs. Only a system reboot fix this problem.

After rebooting, when I make a ping I recive the
following results.

PING 127.0.0.1 (127.0.0.1) from 127.0.0.1 : 56(64) bytes of data
64 bytes from 127.0.0.1: icmp_seq=1 ttl=127 time=1979,786 sec
64 bytes from 127.0.0.1: icmp_seq=2 ttl=127 time=1978,978 sec
64 bytes from 127.0.0.1: icmp_seq=3 ttl=127 time=1977,342 sec
64 bytes from 127.0.0.1: icmp_seq=4 ttl=127 time=1976,453 sec
64 bytes from 127.0.0.1: icmp_seq=5 ttl=127 time=1975,551 sec
64 bytes from 127.0.0.1: icmp_seq=6 ttl=127 time=1974,611 sec

--- 127.0.0.1 ping statistics ---
5 Packets transmitted, 5 recived, 0% loss, time 2019ms
rtt min/avg/max/mdev = 1972705.133/1975230.304/1977756.234/217405.865 ms

Nearly after the 250th icmp_seq the actual time is ~1 ms :-)

The cable are ok.Pinging the ultra from other machines serve normal
results.

There are any alternative ethernet driver or known bugs ? Or there
are some problems with the excessive broadcasting from the NT machines?

The main problem is,that we want to use the sparc primary as dev-workstation
AND as monitoring (netsaint)for the DMZ server ... I don't have to say,
that everything is RED by the "keep-alive-check";-)


Bjoern Schaefer



-- 
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]