[Fwd: [Bug 1474] New: NTP needs too much time correction on 2.6.0-test9]

[Chuck Mead]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

If you are experiencing time problems with linux-beta you should check
this out!

- -------- Original Message --------
Subject: [Bug 1474] New: NTP needs too much time correction on	2.6.0-test9
Date: Sat, 01 Nov 2003 19:57:31 -0800
From: Martin J. Bligh <mbligh at aracnet.com>
To: linux-kernel <linux-kernel at vger.kernel.org>
CC: cesarb at nitnet.com.br

http://bugme.osdl.org/show_bug.cgi?id=1474

~           Summary: NTP needs too much time correction on 2.6.0-test9
~    Kernel Version: 2.6.0-test9
~            Status: NEW
~          Severity: normal
~             Owner: johnstul at us.ibm.com
~         Submitter: cesarb at nitnet.com.br


Distribution: Debian testing/unstable
Hardware Environment: K6II-350
Software Environment: ntpd 4.1.2a
Problem Description:

After upgrading from 2.6.0-test8 to 2.6.0-test9, I started seeing too
many time
reset messages from ntpd (about two or three every hour), all saying the
clock
was set back between 0.5s and 1.5s. Checking the status with ntpq I
noticed it
had a large offset (on the order of 500ms ahead of the peers) and a huge
frequency correction (about -490). Removing ntp.drift (to restore the
correction
to 0) and rebooting didn't help; after a few hours it was back at -500 (the
maximum allowed backwards correction) and still stepping the clock.

Rebooting back into 2.6.0-test8 fixed it; the frequency correction is
now around
- -70 and it is no longer losing sync.

While it was in 2.6.0-test9, a highly unscientific test (running "date"
in it
and in a 2.4 box also using ntpd, in that order, gave me a result 1 second
higher for the first box consistently) shows that ntpd's statistics weren't
bogus; the time in the 2.6 box was really ahead by about 1 second all
the time,
even with ntp trying to slew it (it didn't get higher since ntpd gave up and
stepped it after some time).

Steps to reproduce:

I can reproduce it here simply booting back into 2.6.0-test9; I don't
know which
changes made the difference. I suspect a highly suspicious change in the
timer
code between 2.6.0-test8 and 2.6.0-test9; I will try to find out how to
get the
exact cset in the bkbits web interface and revert by hand to see if it
works.


- -
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo at vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

- --
csm
Lunar Project Leader
Disclaimer: "I am not a curmudgeon! No... really..."
Addendum: "Bwahahaha! Fire up the orbital mind-control lasers!"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.1 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQE/pUcJq3bny/5+GAcRAjdjAJ0aVAfLV+qLLBtmhkrdJ9wup9/DzACcCxiC
aDT8WQL2BTHaACtVgOvttP8=
=R0KO
-----END PGP SIGNATURE-----