Hi all,

This problem is a symptom of a library issue.

The 'ping' utility has the a similar problem.

Until upgrading from 'Etch' to 'Lenny' on AMD64 (dual Opteron)
we had no problems with either.  The system runs 'Smokeping'
tp monitor our networks.  Now it is basically useless.

The results from gettimoefday() are incorrect.

The values have a granularity of 4 milliseconds on our system, which I
guess relates to the 250Hz timer tick.  Unfortunately ping uses the
gettimeofday() function to measure RTT in microseconds, and obviously
this isn't going to work with a4ms granularity in the returned value.

I can confirm that the problem is not in 'ping' itself, the same binary
which works fine on an Athlon system fails in the same way on the Opteron.
A simple 'C' program to print time increments by using the gettimeofday()
function shows the same problems as ping.


tornado:~$ >>> ping lightning
PING lightning.local.jubileegroup.co.uk (192.168.44.236) 56(84) bytes of data.
64 bytes from lightning.local (192.168.44.236): icmp_seq=1 ttl=64 time=4.00 ms
64 bytes from lightning.local (192.168.44.236): icmp_seq=2 ttl=64 time=0.000 ms
64 bytes from lightning.local (192.168.44.236): icmp_seq=3 ttl=64 time=0.000 ms
64 bytes from lightning.local (192.168.44.236): icmp_seq=4 ttl=64 time=0.000 ms
^C
--- lightning.local.jubileegroup.co.uk ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3007ms
rtt min/avg/max/mdev = 0.000/1.000/4.000/1.732 ms
tornado:~$ >>> ssh lightning
Enter passphrase for key '/home/ged/.ssh/id_dsa':
g...@lightning's password:
Linux lightning 2.6.26-1-686 #1 SMP Sat Jan 10 18:29:31 UTC 2009 i686

The programs included with the Debian GNU/Linux system are free software;
the exact distribution terms for each program are described in the
individual files in /usr/share/doc/*/copyright.

Debian GNU/Linux comes with ABSOLUTELY NO WARRANTY, to the extent
permitted by applicable law.
Last login: Wed Feb 18 20:01:38 2009 from laptop.local
g...@lightning:~$ ping tornado
PING tornado.local.jubileegroup.co.uk (192.168.44.47) 56(84) bytes of data.
64 bytes from tornado.local.jubileegroup.co.uk (192.168.44.47): icmp_seq=1 
ttl=64 time=0.133 ms
64 bytes from tornado.local.jubileegroup.co.uk (192.168.44.47): icmp_seq=2 
ttl=64 time=0.147 ms
64 bytes from tornado.local.jubileegroup.co.uk (192.168.44.47): icmp_seq=3 
ttl=64 time=0.145 ms
64 bytes from tornado.local.jubileegroup.co.uk (192.168.44.47): icmp_seq=4 
ttl=64 time=0.163 ms
64 bytes from tornado.local.jubileegroup.co.uk (192.168.44.47): icmp_seq=5 
ttl=64 time=0.157 ms
^C
--- tornado.local.jubileegroup.co.uk ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4014ms
rtt min/avg/max/mdev = 0.133/0.149/0.163/0.010 ms

--

73,
Ged.



-- 
To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org

Reply via email to