Subject: Re: 2.6.0-test3 "loosing ticks"
From: john stultz <johnstul@us.ibm.com>
To: timothy parkinson <t@timothyparkinson.com>
Cc: lkml <linux-kernel@vger.kernel.org>
In-Reply-To: <20030813014735.GA225@timothyparkinson.com>
References: <20030813014735.GA225@timothyparkinson.com>
Content-Type: text/plain
Organization: 
Message-Id: <1060793667.10731.1437.camel@cog.beaverton.ibm.com>
Mime-Version: 1.0
Date: 13 Aug 2003 09:54:27 -0700
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1214
Lines: 30

On Tue, 2003-08-12 at 18:47, timothy parkinson wrote:
> the 2.6 kernels have been loosing time on my box, and i just noticed this
> message at the very bottom of dmesg that i think may relate:
> 
> Loosing too many ticks!
> TSC cannot be used as a timesource. (Are you running with SpeedStep?)
> Falling back to a sane timesource.
> 
> i'm running test-3 right now, but i've been seeing the same problem back into
> the 2.5 kernels.  any ideas?  it's a dual PIII coppermine, relatively close
> to default slackware 9, i'll attach the config in case that helps.  thanks in
> advance!

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.

thanks
-john


-
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/