Slowness over a local network

Howard Lowndes lannet at lannet.com.au
Mon Jun 3 20:55:55 EST 2002


I have a client's workstation on the bench at the moment which has a
complaint of being _very_ slow on their local ethernet.

I just booted it up on my local network and it gave no symptoms, but I
have since rebooted it and am getting the described symptoms.

An ssh into the box takes over 5 _minutes_ and a ping from the workstation
to the workbench server looks like:

64 bytes from 192.168.253.1: icmp_seq=0 ttl=255 time=996.294 msec
Warning: time of day goes back, taking countermeasures.
64 bytes from 192.168.253.1: icmp_seq=1 ttl=255 time=503 usec
64 bytes from 192.168.253.1: icmp_seq=2 ttl=255 time=1.000 sec
64 bytes from 192.168.253.1: icmp_seq=3 ttl=255 time=316 usec
64 bytes from 192.168.253.1: icmp_seq=4 ttl=255 time=1.000 sec
64 bytes from 192.168.253.1: icmp_seq=5 ttl=255 time=434 usec
64 bytes from 192.168.253.1: icmp_seq=6 ttl=255 time=1.000 sec
64 bytes from 192.168.253.1: icmp_seq=7 ttl=255 time=268 usec
64 bytes from 192.168.253.1: icmp_seq=8 ttl=255 time=1.000 sec
64 bytes from 192.168.253.1: icmp_seq=9 ttl=255 time=347 usec
64 bytes from 192.168.253.1: icmp_seq=10 ttl=255 time=1.000 sec
64 bytes from 192.168.253.1: icmp_seq=11 ttl=255 time=273 usec


and a ping from the workbench server to the workstation looks like:

64 bytes from 192.168.253.133: icmp_seq=0 ttl=255 time=997.064 msec
64 bytes from 192.168.253.133: icmp_seq=1 ttl=255 time=999.942 msec
64 bytes from 192.168.253.133: icmp_seq=2 ttl=255 time=999.955 msec
64 bytes from 192.168.253.133: icmp_seq=3 ttl=255 time=999.950 msec
64 bytes from 192.168.253.133: icmp_seq=4 ttl=255 time=999.956 msec
64 bytes from 192.168.253.133: icmp_seq=5 ttl=255 time=999.960 msec

The response is similar to one I have seen before where there was an IRQ
conflict but I don't think that is the case here.

It's a VIA VT82C694T chipset on the mobo with a Davicom NIC chip.  I have
had problems with VIA chipsets and Realtek NIC chips before, but that does
not apply here, I don't think.

Has anyone seen this type of behaviour before, or better still, know a
cause and a fix?

-- 
Howard.
LANNet Computing Associates - Your Linux people
Contact detail at http://www.lannetlinux.com
"Life is like a hot bath - it's great when you're in it,
 but the longer you stay the more wrinkled you become."
  - Garfield






More information about the linux mailing list