From: john stultz <johnstul@us.ibm.com>
To: Lee Revell <rlrevell@joe-job.com>
Cc: Valdis.Kletnieks@vt.edu, Udo van den Heuvel <udovdh@xs4all.nl>,
linux-kernel@vger.kernel.org,
Roman Zippel <zippel@linux-m68k.org>
Subject: Re: 2.6.18 w/ GPS time source: worse performance
Date: Wed, 18 Oct 2006 16:17:39 -0700 [thread overview]
Message-ID: <1161213459.5875.52.camel@localhost.localdomain> (raw)
In-Reply-To: <1161207996.15860.134.camel@mindpipe>
On Wed, 2006-10-18 at 17:46 -0400, Lee Revell wrote:
> [added John Stultz to cc]
>
> On Wed, 2006-10-18 at 15:57 -0400, Valdis.Kletnieks@vt.edu wrote:
> > On Wed, 18 Oct 2006 18:44:59 +0200, Udo van den Heuvel said:
> > >
> > > It is stuff that is visible by watching ntpq -pn output, by letting mrtg
> > > graph stuff, etc. Watch the offset and jitter collumns.
> > > Check /usr/sbin/ntpdc -c kerninfo output. Graph that stuff.
> >
> > So... you've presumably done that while identifying there is an issue.
> > Please share the results. Have you tried booting back into a 2.6.17
> > or so and seen offset/jitter improve? etc etc etc.
Udo:
Are you running the linuxpps patches, or is this vanilla 2.6.18 without
any additional patches? Mind sending your dmesg and some "ntpdc -c
kerninfo" output? Any of those graphs you mention above would be great
as well.
thanks
-john
next prev parent reply other threads:[~2006-10-18 23:17 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-10-17 15:25 2.6.18 w/ GPS time source: worse performance Udo van den Heuvel
2006-10-17 16:46 ` Lee Revell
2006-10-17 17:07 ` Udo van den Heuvel
2006-10-18 15:20 ` Udo van den Heuvel
2006-10-18 16:36 ` Lee Revell
2006-10-18 16:44 ` Udo van den Heuvel
2006-10-18 19:57 ` Valdis.Kletnieks
2006-10-18 21:46 ` Lee Revell
2006-10-18 23:17 ` john stultz [this message]
2006-10-19 14:12 ` Udo van den Heuvel
2006-10-19 14:14 ` Udo van den Heuvel
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=1161213459.5875.52.camel@localhost.localdomain \
--to=johnstul@us.ibm.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=rlrevell@joe-job.com \
--cc=udovdh@xs4all.nl \
--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