From: Lee Revell <rlrevell@joe-job.com>
To: Valdis.Kletnieks@vt.edu
Cc: Udo van den Heuvel <udovdh@xs4all.nl>,
linux-kernel@vger.kernel.org, john stultz <johnstul@us.ibm.com>
Subject: Re: 2.6.18 w/ GPS time source: worse performance
Date: Wed, 18 Oct 2006 17:46:35 -0400 [thread overview]
Message-ID: <1161207996.15860.134.camel@mindpipe> (raw)
In-Reply-To: <200610181957.k9IJvw4m013149@turing-police.cc.vt.edu>
[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,
My crystal ball says this is related to the clocksource changes. But at
the very least dmesg and kernel .config is required for debugging.
Also, don't trim CC lists - always use Reply-To-All for LKML threads.
Lee
next prev parent reply other threads:[~2006-10-18 21:46 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 [this message]
2006-10-18 23:17 ` john stultz
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=1161207996.15860.134.camel@mindpipe \
--to=rlrevell@joe-job.com \
--cc=Valdis.Kletnieks@vt.edu \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=udovdh@xs4all.nl \
/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