Messages in this thread | | | Date | Wed, 30 Mar 2005 00:11:07 +0200 | From | Dominik Brodowski <> | Subject | Re: Clock 3x too fast on AMD64 laptop [WAS Re: Various issues after rebooting] |
| |
On Wed, Mar 30, 2005 at 12:02:11AM +0200, Olivier Fourdan wrote: > Hi, > > A quick look at the source shows that the error is triggered in > arch/i386/kernel/timers/timer_pm.c by the verify_pmtr_rate() function. > > My guess is that the pmtmr timer is right and the pit is wrong in my > case. That would explain why the clock is wrong when being based on pit > (like when forced with "clock=pit") > > Maybe, if I can prove my guesses, a fix could be to "trust" the pmtmr > clock when the user has passed a "clock=pmtmr" argument ? Does that make > any sense ?
This would make a lot of sense, IMHO. John, what do you think?
Dominik - 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/
| |