Date: Thu, 14 Aug 2003 18:17:03 +0100
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"
Message-ID: <20030814171703.GA10889@mail.jlokier.co.uk>
References: <20030813014735.GA225@timothyparkinson.com> <1060793667.10731.1437.camel@cog.beaverton.ibm.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
In-Reply-To: <1060793667.10731.1437.camel@cog.beaverton.ibm.com>
User-Agent: Mutt/1.4.1i
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1004
Lines: 25

john stultz wrote:
> Sounds like either your PIT is running slowly or something is
> consistently keeping the timer interrupt from being handled. In 2.4 do
> you have any time related issues at all?  Does the "Loosing too many
> ticks!" message correlate to any event on the system (boot, heavy load)?
> 
> Also listing system type, motherboard, any sort of funky devices you've
> got might be helpful.

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.

It does not have this problem with 2.4 - the time synchronises perfectly.

-- Jamie


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/