Re: clocksource change of behavior in 2.6.22 compared to 2.6.20causes massive system clock slowdown

[john stultz]

On Tue, 2007-07-10 at 00:29 -0700, Andrew Morton wrote:
> On Mon, 9 Jul 2007 16:27:59 +0200 "Alessandro Suardi" <alessandro.suardi@xxxxxxxxx> wrote:
> 
> > My oldish AMD K7-800's clock began falling behind after
> >  rebooting from 2.6.20 (and 109 days uptime with a spotless
> >  clock) into 2.6.22; time lost is about four minutes each hour.
> > 
> > Turns out that 2.6.22 marks my TSC as unstable and starts
> >  using PIT instead. Rebooting 2.6.22 with clocksource=tsc
> >  gets the original stable system time back.

Alessandro,
Can you send me dmesg output for 2.6.20 and 2.6.22 (without
clocksource=tsc)?

thanks
-john

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