I have this or a similar problem. My system clock run about 4% fast-- gaining an hour a day. To compensate I've had to set adjtimex --tick 9600, which approximately corrects for the drift. But the drift rate isn't constant, and ntpd can't keep up. Here what I get when I run ntpdate once a minute:
20 Mar 05:05:58 ntpdate[17703]: step time server 168.75.65.20 offset 0.060836 sec 20 Mar 05:06:55 ntpdate[17724]: step time server 168.75.65.20 offset -0.514396 sec 20 Mar 05:07:53 ntpdate[17734]: step time server 168.75.65.20 offset 0.263715 sec 20 Mar 05:08:51 ntpdate[17740]: step time server 168.75.65.20 offset -0.047366 sec 20 Mar 05:09:48 ntpdate[17746]: step time server 168.75.65.20 offset -0.215751 sec 20 Mar 05:10:45 ntpdate[17755]: step time server 168.75.65.20 offset -0.646224 sec 20 Mar 05:11:42 ntpdate[17763]: step time server 168.75.65.20 offset -1.274522 sec Right after I boot the clock drift rate is stable at about -50 PPM, but then after a few hours it starts to go nuts. I'm running a custom 64-bit kernel 2.6.15. CPU is Athlon64 X2 4200+, chipset is nForce4. I don't think I can have the "AMD/ATI bug" as in http://bugs.debian.org/338467, because I don't have an ATI chipset. Anyway I've tried booting with each of disable_timer_pin_1 (my host won't boot) no_timer_check noapic acpi=off clock=pmtmr notsc I also disabled CPU frequency spread spectrum in the BIOS. The result is always the same-- the clock is stable after I boot, but a few hours later it goes nuts again. Any help would be greatly appreciated. Andrew. -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
