[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20101026140500.GA3578@arch.trippelsdorf.de>
Date: Tue, 26 Oct 2010 16:05:00 +0200
From: Markus Trippelsdorf <markus@...ppelsdorf.de>
To: Borislav Petkov <bp@...64.org>
Cc: "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>,
"hpa@...ux.intel.com" <hpa@...ux.intel.com>,
Thomas Gleixner <tglx@...utronix.de>,
Ingo Molnar <mingo@...e.hu>,
Andreas Herrmann <andreas.herrmann3@....com>
Subject: Re: Clocksource tsc unstable (delta = -8589361717 ns) in current
git
On Tue, Oct 26, 2010 at 03:58:08PM +0200, Markus Trippelsdorf wrote:
> On Tue, Oct 26, 2010 at 03:18:43PM +0200, Borislav Petkov wrote:
> > On Tue, Oct 26, 2010 at 07:20:52AM -0400, Markus Trippelsdorf wrote:
> > > On my AMD system the following kernel messages are sometimes printed
> > > after several hours of uptime:
> > > Clocksource tsc unstable (delta = -8589361717 ns)
> > > Switching to clocksource hpet
> >
> > This is strange, tsc is actually stable on your F10h revC.
>
> Yes. constant_tsc is among the CPU flags.
>
> > > This happened several times already:
> > > # grep "Clocksource" kernel.*
> > > kernel.log:Oct 24 18:31:17 arch kernel: Clocksource tsc unstable (delta = -8591703466 ns)
> > > kernel.log:Oct 26 12:54:38 arch kernel: Clocksource tsc unstable (delta = -8589361717 ns)
> > > kernel.log.1:Oct 22 21:43:51 arch kernel: Clocksource tsc unstable (delta = -25772316650 ns)
> >
> > Do you have any warnings/oopses before that, can we have the whole dmesg
> > with the above messages?
>
> No warning/oopses. The whole dmesg is attached.
This time I will hopefully hit the right key in mutt...
--
Markus
View attachment "kernel.log" of type "text/plain" (44725 bytes)
Powered by blists - more mailing lists