On 06/04/2011 21:58, Miroslav Lichvar wrote: > On Wed, Apr 06, 2011 at 07:18:24PM +0100, Ed W wrote: >> - I see a clear connection between my cpu Mhz as reported in say >> /proc/cpuinfo (unknown if this source is reliable when processor >> powersave in use?) and the stable chrony tracking parameters > > At least here, MHz in /proc/cpuinfo is affected by powersaving and it > is a nicely rounded value, not what kernel prints in dmesg. > >> I'm quite surprised that others don't see this gross variation that I >> do? For me at least I get no value at all from chrony's saved tracking >> params because chrony is tracking an average offset of around 130ppm, >> but the bootup variation is some 100+ ppm around that offset? Do others >> get less variation with each boot? > > I just made a test with a 2.6.38-rc0 kernel and I have good > news for you :). I noticed this in dmesg: > > Detected 3192.489 MHz processor. > Refined TSC clocksource calibration: 3191.999 MHz
Hmm, will give it a try shortly. > It seems to be this commit, merged just few months ago. > http://git.kernel.org/?p=linux/kernel/git/x86/linux-2.6-tip.git;a=commitdiff;h=08ec0c58fb8a05d3191d5cb6f5d6f81adb419798 Ahh, interesting - sadly the Alix has no PM or HPET timers so I think this is unlikely to help *my* specific case, but it's very good news in general! Ed W --- To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org with "unsubscribe" in the subject. For help email chrony-users-requ...@chrony.tuxfamily.org with "help" in the subject. Trouble? Email listmas...@chrony.tuxfamily.org.