[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#516150: marked as done (linux-2.6 - gettimeofday have 4ms granularity)

Your message dated Sun, 23 Jun 2013 16:08:48 +0200
with message-id <20130623140847.GB5918@pisco.westfalen.local>
and subject line Closing
has caused the Debian Bug report #516150,
regarding linux-2.6 - gettimeofday have 4ms granularity
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact owner@bugs.debian.org
immediately.)


-- 
516150: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=516150
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: traceroute
Version: 2.0.11-2
Severity: important
Forum reference to the problem: http://forums.debian.net/viewtopic.php?p=208492 Upgraded to lenny 5.0.0, and since then traceroute's reported times are incorrect. 
I experience this problem on ubuntu 8.04 and greater.
I replaced the PC's motherboard (Gigabyte GA-K8NS) with a new one but this made no difference. 
PC is an AMD64 3400+ with 1GB DDR.
The results are consistent and something has definitely broken it since Etch. 

Here is an example output to show the difference/problem:

root@linuxfw:/etc/ppp/accs # traceroute 172.16.1.1
traceroute to 172.16.1.1 (172.16.1.1), 30 hops max, 40 byte packets
 1  172-16-6-10.fragtion.jawug (172.16.6.10)  1.725 ms  1.818 ms  1.923 ms
 2  wlan-gw.sc1-1.sc.Jawug (172.16.26.1)  13.135 ms  15.498 ms  17.392 ms
 3  nc.sc.jawug (172.16.253.9)  17.737 ms  21.009 ms  21.359 ms
 4  wugbox.jawug (172.16.1.1)  21.535 ms  23.776 ms  24.031 ms

Compare results with those of `traceroute-nanog`:

root@linuxfw:/etc/ppp/accs # traceroute-nanog 172.16.1.1
traceroute to 172.16.1.1 (172.16.1.1), 30 hops max, 40 byte packets
 1  172-16-6-10.fragtion.jawug (172.16.6.10)  1.029 ms  0.970 ms  0.939 ms
 2  wlan-gw.sc1-1.sc.Jawug (172.16.26.1)  2.445 ms  2.305 ms  3.862 ms
 3  nc.sc.jawug (172.16.253.9)  4.745 ms  3.599 ms  2.867 ms
 4  wugbox.jawug (172.16.1.1)  3.862 ms  3.278 ms  3.637 ms

root@linuxfw:/etc/ppp/accs # ping 172.16.1.1
PING 172.16.1.1 (172.16.1.1) 56(84) bytes of data.
64 bytes from 172.16.1.1: icmp_seq=1 ttl=61 time=3.32 ms
64 bytes from 172.16.1.1: icmp_seq=2 ttl=61 time=3.79 ms
64 bytes from 172.16.1.1: icmp_seq=3 ttl=61 time=3.85 ms
64 bytes from 172.16.1.1: icmp_seq=4 ttl=61 time=3.12 ms
64 bytes from 172.16.1.1: icmp_seq=5 ttl=61 time=3.70 ms

--- 172.16.1.1 ping statistics ---
5 packets transmitted, 5 received, 0% packet loss, time 4001ms
rtt min/avg/max/mdev = 3.126/3.559/3.858/0.285 ms


-- System Information:
Debian Release: 5.0
  APT prefers stable
  APT policy: (500, 'stable')
Architecture: i386 (i686)

Kernel: Linux 2.6.26-1-486
Locale: LANG=en_ZA.UTF-8, LC_CTYPE=en_ZA.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash

Versions of packages traceroute depends on:
ii  libc6                         2.7-18     GNU C Library: Shared libraries

traceroute recommends no packages.

traceroute suggests no packages.

-- no debconf information

--- End Message ---
--- Begin Message --- 
Hi,
your bug has been filed against the "linux-2.6" source package and was filed for
a kernel older than the recently released Debian 7.x / Wheezy with a severity
less than important.

We don't have the ressources to reproduce the complete backlog of all older kernel
bugs, so we're closing this bug for now. If you can reproduce the bug with Debian Wheezy
or a more recent kernel from testing or unstable, please reopen the bug by sending
a mail to control@bugs.debian.org with the following three commands included in the
mail:

reopen BUGNUMBER
reassign BUGNUMBER src:linux
thanks

Cheers,
        Moritz

--- End Message ---
Reply to: