I've been trying to figure out what I can do about a clock drift that happens only on Suse Linux.
My hardware is a 4 processor Dual core F socket AMD system (Supermicro) and it keeps going over by about 3-4 minutes per hour. I installed Windows 2003 server on the same machine and it does not have this problem. So it seems specific to Suse 10.2.

This system is needs to go into production with a very accurate clock, I can't even use NTP services because even if it syncs every 2 minutes that's not good enough. (It needs to be within a 5 seconds)

I've read various clock drifts on Linux and it seems that some older kernels had this problem, but I haven't found anything specific for Suse 10.2 (which is fairly recent) and uses 2.4 kernel (I believe).

I'm fairly new to Linux, so I'm hoping there are some things that can be done..