Re: PMTMR running too fast

2006-12-06 Thread Andi Kleen
> > I don't think the boot time check needs DMI guarding > > DMI guarding? I'm not following... DMI guarding = Making it conditional on a DMI check -Andi - To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to [EMAIL PROTECTED] More majordomo info a

Re: PMTMR running too fast

2006-12-06 Thread Ian Campbell
On Tue, 2006-12-05 at 11:34 -0800, john stultz wrote: > > > Should tsc be preferred to pit though? > > Depends on your system. If C2/C3 or cpufreq state changes are > detected, we mark the tsc as unstable. Turns out I was seeing C2 states. I'll stick with PIT for now. Thanks, Ian. -- Ian Ca

Re: PMTMR running too fast

2006-12-06 Thread john stultz
On Wed, 2006-12-06 at 17:44 +0100, Andi Kleen wrote: > > > > > Is there a specific reason the check was removed (I couldn't see on in > > > the archives) or was it simply overlooked? Without it I need to pass > > > clocksource=tsc to have 2.6.18 work correctly on an older K6 system with > > > an Al

Re: PMTMR running too fast

2006-12-06 Thread Andi Kleen
> > > Is there a specific reason the check was removed (I couldn't see on in > > the archives) or was it simply overlooked? Without it I need to pass > > clocksource=tsc to have 2.6.18 work correctly on an older K6 system with > > an Aladdin chipset (will dig out the precise details if required).

Re: PMTMR running too fast

2006-12-06 Thread Ian Campbell
On Tue, 2006-12-05 at 11:34 -0800, john stultz wrote: > On Tue, 2006-12-05 at 07:41 +, Ian Campbell wrote: > > Should tsc be preferred to pit though? > > Depends on your system. If C2/C3 or cpufreq state changes are detected, > we mark the tsc as unstable. I'm not using them on purpose but I

Re: PMTMR running too fast

2006-12-05 Thread john stultz
On Tue, 2006-12-05 at 07:41 +, Ian Campbell wrote: > On Mon, 2006-12-04 at 12:14 -0800, john stultz wrote: > > I don't have a dev box to test on at the moment, but here's a quick hack > > attempt at re-adding the code. Does the following work for you? > > I get: > PM-Timer running at

Re: PMTMR running too fast

2006-12-04 Thread Ian Campbell
On Mon, 2006-12-04 at 12:14 -0800, john stultz wrote: > On Mon, 2006-12-04 at 19:40 +, Ian Campbell wrote: > > On Mon, 2006-12-04 at 11:19 -0800, john stultz wrote: > > > On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote: > > > > In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pm

Re: PMTMR running too fast

2006-12-04 Thread john stultz
On Mon, 2006-12-04 at 19:40 +, Ian Campbell wrote: > On Mon, 2006-12-04 at 11:19 -0800, john stultz wrote: > > On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote: > > > In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pmtmr_rate > > > contained a check for sensible PMTMR rate and d

Re: PMTMR running too fast

2006-12-04 Thread Ian Campbell
On Mon, 2006-12-04 at 11:19 -0800, john stultz wrote: > On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote: > > In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pmtmr_rate > > contained a check for sensible PMTMR rate and disabled that clocksource > > if it was found to be out of spec[

Re: PMTMR running too fast

2006-12-04 Thread john stultz
On Sun, 2006-12-03 at 13:50 +, Ian Campbell wrote: > In older kernels arch/i386/kernel/timers/timer_pm.c:verify_pmtmr_rate > contained a check for sensible PMTMR rate and disabled that clocksource > if it was found to be out of spec[0]. This check seems to have been lost > in the transition to