From: linux@horizon.com
To: johnstul@us.ibm.com, linux-kernel@vger.kernel.org, zippel@linux-m68k.org
Cc: linux@horizon.com
Subject: 2.6.19-rc2 and very unstable NTP
Date: 26 Oct 2006 05:24:30 -0400 [thread overview]
Message-ID: <20061026092430.25816.qmail@science.horizon.com> (raw)
There have been a bunch of changes to timekeeping since 2.6.17, and I've
noticed that, with 2.6.19-rc2 + linuxpps, I'm getting some impressively
unstable oscillations in the local time. +/- 350 us, when, given a
good quality local PPS source, it should be wiggling +/- a few us.
And the shape of the curves is not "wander" but "overcorrecting wildly".
It's sort of series of exponential decay curves, but each one overshoots
by 100%, and then before it fully flattens out, starts surging in the
other direction. (Actually, the overshoot amplitudes fluctuate
erratically, too.) As best I can render it in ASCII art:
* * *
* *
* *
* *
* * * *
* *
* *
--------------*----------------------*-----------
* *
* * * *
* *
* *
* *
* *
600-700 us p-p, with 2200-2400 s per full cycle.
It looks like ajtimex() isn't doing what NTP is expecting,
leading to loop instability.
I'm going to git bisect this, although it's a bit time-consuming
waiting to see if things will settle own cleanly after each reboot.
And some of the patches have been anything but one-liners, so
that's not necessarily a direct pointer to the problem.
I know there have been a number of reports of ntp timekeeping
problems with 2.6.18. Has there been any progress already?
(Local system: AMD64 uniprocessor, 2.6.19-rc2+linuxpps kernel,
NTP 4.2.2, Acutime 2000 GPS clock + PPS input.)
next reply other threads:[~2006-10-26 9:24 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:24 linux [this message]
2006-10-26 9:45 ` 2.6.19-rc2 and very unstable NTP Roman Zippel
2006-10-26 10:00 ` linux
2006-10-26 10:22 ` Roman Zippel
2006-10-26 12:30 ` linux
2006-10-26 13:01 ` Roman Zippel
2006-10-26 21:59 ` john stultz
2006-10-26 23:06 ` Roman Zippel
2006-10-27 9:15 ` linux
2006-10-27 10:58 ` Roman Zippel
2006-10-27 11:30 ` linux
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20061026092430.25816.qmail@science.horizon.com \
--to=linux@horizon.com \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=zippel@linux-m68k.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox