super slow clock

[Kurt Wall]

In a 1.1K blaze of typing glory, David A. Bandel wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
> 
> Folks,
> 
> OK, now I've seen it all (or maybe not, but I've not seen this before). 
> I have a system that has suddenly developed a super slow clock.  That
> is, it looses 30 seconds per minute.  NTP couldn't keep it up to date,
> so now I'm running ntpdate via crontab every 15 minutes.  It still hoses
> the MRTG output -- you can actually _see_ the updates every 15 minutes
> as a gap in the graphs.
> 
> This is driving me nuts.  Apart from syncing time every 60 seconds (or
> less), I don't know how to fix this.  Anyone got any bright ideas?

Nothing in the log files? My first suspicion would be a hardware
problem, but I've never heard of a clock going bad like that. My second
suspicion would be that the kernel's timekeeping has somehow gotten 
bollixed up.

Kurt
-- 
Lie, n.:
	A very poor substitute for the truth, but the only one
discovered to date.