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

On Tue, 2007-07-10 at 00:29 -0700, Andrew Morton wrote:
> On Mon, 9 Jul 2007 16:27:59 +0200 "Alessandro Suardi" <[email protected]> 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

Follow-Ups:
- Re: clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown
  - From: "Alessandro Suardi" <[email protected]>

References:
- clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown
  - From: "Alessandro Suardi" <[email protected]>
- Re: clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown
  - From: Andrew Morton <[email protected]>

Prev by Date: Re: -mm merge plans for 2.6.23 -- sys_fallocate
Next by Date: Re: [patch] mm: recheck lock rlim after f_op->mmap() method
Previous by thread: Re: clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown
Next by thread: Re: clocksource change of behavior in 2.6.22 compared to 2.6.20 causes massive system clock slowdown
Index(es):
- Date
- Thread

[Index of Archives] [Kernel Newbies] [Netfilter] [Bugtraq] [Photo] [Stuff] [Gimp] [Yosemite News] [MIPS Linux] [ARM Linux] [Linux Security] [Linux RAID] [Video 4 Linux] [Linux for the blind] [Linux Resources]