Re: [ntp:questions] Hopelessly broken clock?

2008-11-16 Thread Chris Adams
Once upon a time, Hal Murray <[EMAIL PROTECTED]> said: >>I'm running CentOS 5 on my system and the only clock source I have available >>is jiffies. Newer kernels should give you options like: acpi_pm jiffies hpet >>tsc pit. > >I've been happier since I added > clocksource=acpi_pm >to the boot comm

Re: [ntp:questions] Hopelessly broken clock?

2008-11-16 Thread Hal Murray
>I'm running CentOS 5 on my system and the only clock source I have available >is jiffies. Newer kernels should give you options like: acpi_pm jiffies hpet >tsc pit. I've been happier since I added clocksource=acpi_pm to the boot command line. TSC is the default, at least on most of the system

Re: [ntp:questions] Hopelessly broken clock?

2008-11-16 Thread Unruh
"Phil" <[EMAIL PROTECTED]> writes: >"Chris Richmond" <[EMAIL PROTECTED]> wrote in message >news:[EMAIL PROTECTED] >> I'm trying to set up ntp on a new Core2 Duo box running Fredora Core9. >> It appears that it's local clock runs several seconds an hour fast. I'm >> basing this on running ntpdat

Re: [ntp:questions] Hopelessly broken clock?

2008-11-16 Thread Jason Rabel
Chris, This is *probably* caused from EIST and/or C1E being enabled in your BIOS. These features dynamically adjust the speed of your CPU (and voltage) according to the CPU demand. You can try to disable them and see if things stabilize, if they do then you know what the culprit is. If you really