Serious time drift - clock running fast

Serious time drift - clock running fast

[Marc Perkel]

Not sure what the problem is but it seem kernel related. If it's not - 
please forgive me.

I'm running and AMD Athlon 64 X2 on an Asus board with NVidia chipset. 
The software clock gains several seconds every minute. I'm running the 
2.6.13 kernel. NTPD doesn't help. It sets the time when it starts but I 
suspect the drift is too great for it to lock on. How can setting the 
clock be so hard?

Using these settings:

CONFIG_X86_64=y
CONFIG_64BIT=y
CONFIG_X86=y
CONFIG_MMU=y
CONFIG_RWSEM_GENERIC_SPINLOCK=y
CONFIG_GENERIC_CALIBRATE_DELAY=y
CONFIG_X86_CMPXCHG=y
CONFIG_EARLY_PRINTK=y
CONFIG_GENERIC_ISA_DMA=y
CONFIG_GENERIC_IOMAP=y

Falling asleep .... ZZZzzzzzZZZZzzzzzz

Help!


-- 
Marc Perkel - marc@perkel.com

Spam Filter: http://www.junkemailfilter.com
    My Blog: http://marc.perkel.com

Re: Serious time drift - clock running fast

[Howard Chu]

I'm having the same problem with 2.6.13, AMD64 X2, Asus A8V Deluxe 
motherboard. What's worse is that this is my local net's NTP server, so 
it's taking all my other machines' clocks along for the ride, and I'm 
losing my associations to the upper strata servers because the skew gets 
too great. (So ntpd needs to be restarted periodically.)

I've seen earlier reports on this list about the clock running twice 
normal speed. That's not what I'm seeing here; after several hours it's 
only ahead by 5 minutes at the moment. (The system has been up 20 days, 
but I restarted ntpd a few hours ago, and it resync'd via ntpdate at 
that point.) Maybe it would be running at 2X if I kill ntpd, I haven't 
checked that.

If it matters, I configured a 250Hz clock tick on this kernel.

-- 
  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/