From: john stultz <johnstul@us.ibm.com>
To: linux@horizon.com
Cc: zippel@linux-m68k.org, linux-kernel@vger.kernel.org
Subject: Re: 2.6.19-rc2 and very unstable NTP
Date: Thu, 26 Oct 2006 14:59:46 -0700 [thread overview]
Message-ID: <1161899986.960.59.camel@localhost> (raw)
In-Reply-To: <20061026123051.3831.qmail@science.horizon.com>
On Thu, 2006-10-26 at 08:30 -0400, linux@horizon.com wrote:
> First of all, nobody get too excited, yet. I'm seeing an odd divergence
> between the offset recorded in ntp's peerstats file (the log of the
> measured time differences between each clock source) and the offset in
> the loopstats file (the consensus value it uses to control the local
> clock oscillator) that I need to investigate first.
Ok, let us know if you find anything there.
> If you're deeply suspiscious of a simple device driver, with publicly
> available code, that adds timestamping to the handling of DCD changed
> events from the serial ports, and exports those timestamps to user space,
> I can remove it. The Acutime 2000 can timestamp pulses sent to it
> (via the RTS line), so I can get sub-microsecond time measurements anyway.
One of the recent changes was removing the in-kernel PPS code. This was
done because there were no in-kernel users of the interface (the only
ones being I believe in a variant of this LinuxPPS patch). While from
the diffstat below it doesn't look like the patch affects the
timekeeping code, it would be good to first reproduce the issue without
the patch.
> Having PPS as well was just a nice redundancy feature.
>
> But here's the diffstat, with newly created files marked with a leading "+".
> drivers/Kconfig | 2 +
> drivers/Makefile | 1 +
> +drivers/pps/Kconfig | 43 ++++
> +drivers/pps/Makefile | 7 +
> +drivers/pps/clients/Kconfig | 23 ++
> +drivers/pps/clients/Makefile | 6 +
> +drivers/pps/clients/ktimer.c | 107 +++++++++
> +drivers/pps/kapi.c | 172 ++++++++++++++
> +drivers/pps/pps.c | 385 +++++++++++++++++++++++++++++++
> +drivers/pps/procfs.c | 180 +++++++++++++++
> drivers/serial/8250.c | 85 +++++++-
> include/linux/netlink.h | 2 +-
> +include/linux/pps.h | 93 ++++++++
> +include/linux/timepps.h | 515 ++++++++++++++++++++++++++++++++++++++++++
> 14 files changed, 1617 insertions(+), 4 deletions(-)
>
> I *really* doubt it has any effect on the kernel timekeeping code.
Could you also send me a copy of your full dmesg?
thanks
-john
next prev parent reply other threads:[~2006-10-26 22:01 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-26 9:24 2.6.19-rc2 and very unstable NTP linux
2006-10-26 9:45 ` 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 [this message]
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=1161899986.960.59.camel@localhost \
--to=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@horizon.com \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.