From: Jamie Lokier <jamie@shareable.org>
To: john stultz <johnstul@us.ibm.com>
Cc: timothy parkinson <t@timothyparkinson.com>,
lkml <linux-kernel@vger.kernel.org>
Subject: Re: 2.6.0-test3 "loosing ticks"
Date: Thu, 14 Aug 2003 22:58:28 +0100 [thread overview]
Message-ID: <20030814215828.GA12650@mail.jlokier.co.uk> (raw)
In-Reply-To: <1060882084.10732.1588.camel@cog.beaverton.ibm.com>
john stultz wrote:
> > I am seeing something similar on my dual Athlon MP 1800 box.
> >
> > It is running NTP to synchronise with another machine over the LAN,
> > but ntpdc reports that it develops a larger and larger offset relative
> > to the server - ntpd clearly is not managing to regulate the clock.
>
> Approximately at what rate does it skew? Does ntpdate -b <server> set it
> properly?
I'll keep a note. It's not very fast, but enough to reach several
tens of seconds after a day's work - enough to break Make over NFS,
that's why I noticed.
It might stop showing up now, as I am now running 2.5.75 on the server too :)
> Are you also seeing the "Loosing too many ticks!" message?
No.
-- Jamie
next prev parent reply other threads:[~2003-08-14 22:00 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-08-13 1:47 timothy parkinson
2003-08-13 16:54 ` john stultz
2003-08-14 17:17 ` Jamie Lokier
2003-08-14 17:28 ` john stultz
2003-08-14 21:58 ` Jamie Lokier [this message]
2003-08-15 0:19 ` PIT, TSC and power management [was: Re: 2.6.0-test3 "loosing ticks"] Charles Lepple
2003-08-15 12:10 ` Jamie Lokier
2003-08-15 17:48 ` john stultz
2003-08-15 18:53 ` PIT, TSC and power management [was: Re: 2.6.0-test3 "loosingticks"] Charles Lepple
2003-08-15 23:12 ` PIT, TSC and power management [was: Re: 2.6.0-test3 "loosing ticks"] Jamie Lokier
2003-08-15 23:25 ` john stultz
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=20030814215828.GA12650@mail.jlokier.co.uk \
--to=jamie@shareable.org \
--cc=johnstul@us.ibm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=t@timothyparkinson.com \
/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
all inboxes | Powered by JetHome®