Richard B. Gilbert wrote: > How badly does the clock drift if ntpd is not running? If it's still > ten minutes per day, you either have a severe hardware problem or a > software problem that is causing your system to lose timer interrupts.
Thanks for responding. Yes, it turns out the problem had nothing to do with ntpd after all. It seems that starting in Linux 2.6.18, the CPU's time stamp counter (TSC) is used to keep time. In my case, for some unknown reason, the kernel sometimes misdetects the CPU's TSC frequency on boot, resulting in severe clock drift that ntpd is unable to correct. In case anyone else is afflicted by the same problem, I've managed to work around it by adding the following parameter to my kernel command line in grub.conf: clocksource=acpi_pm This tells the kernel to use the ACPI PM timer to keep time instead of the CPU's TSC. (From what I understand, the ACPI PM timer is what older Linux kernels used by default.) -- Jordan Russell _______________________________________________ questions mailing list questions@lists.ntp.isc.org https://lists.ntp.isc.org/mailman/listinfo/questions