I've already told KDE about this and they of course are pointing to SuSE, so please dont redirect me to KDE, I'm going to redirect to another Linux distribution if somebody doesnt take responsibility.  This is fucking up my day big time as I'm trying to use the system for actual work, not for play.  I depend on the system to work correctly.  The clock works fine in Windows XP, so I know this is not a BIOS problem.  I am having to stop work until this is fixed.  

I have two of these machines, and the problem appears on both machines.

What Happens

The clock applet shows a racing clock, skipping seconds forward rapidly.  I go into YAST, "Adjust Date & Time" and before I touch anything, it resets the clock to the correct time.  I simply hit "Accept" and the time is corrected.  The problem does not present itself until after a few minutes after a reboot. So it looks ok right after booting up the system.  About 10-15 minutes after boot the problem shows up.

I have deleted /etc/adjtime, and searched all over the place to get a resolution, so if you guys dont have a solution I will be installing a different Linux distro to overcome this problem.  I have also upgraded KDE to 3.4.3b just to see if that would fix the problem, and it does not.

cat /etc/adjtime 
0.000000 1132757448 0.000000
1132757448
LOCAL

I also had NTP set up but not only did I stop using it, I actually uninstalled it off the system just to make sure this wasnt causing any problems either.  By the way the YAST dialogs for NTP suck, please make it more configurable without having to be a rocket scientist.

I have also booted the system in to Knoppix x86, Mepis x86, and Xandros x86 Linux and the clock problem did not present itself, so I know it's something to do with this release of SuSE 10. ( or maybe x86 works fine and x86_64 does not??? )

QUESTIONS:  Would buying the commercial version of SuSE10 solve this problem?  

Is there a difference between the OpenSuse10 and the commercial $59 version?

Should I use the x86 version instead of the x86_64 version?

I am a big fan of SUSE but this is a show-stopper, I cannot use it if the clock is not working correctly.



My System

HP Media Center PC m7248n

uname -a
Linux db002 2.6.13-15-smp #1 SMP Tue Sep 13 14:56:15 UTC 2005 x86_64 x86_64 x86_64 GNU/Linux

cat /etc/SuSE-release 
SUSE LINUX 10.0 (X86-64) OSS
VERSION = 10.0


KDE 3.4.3 Level "b"


/proc/cpuinfo

processor       : 0
vendor_id       : AuthenticAMD
cpu family      : 15
model           : 43
model name      : AMD Athlon(tm) 64 X2 Dual Core Processor 4200+
stepping        : 1
cpu MHz         : 994.949
cache size      : 512 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
fpu             : yes
fpu_exception   : yes
cpuid level     : 1
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush mmx fxsr sse sse2 ht syscall nx mmxext fxsr_opt lm 3dnowext 3dnow pni lahf_l
m cmp_legacy
bogomips        : 1993.73
TLB size        : 1024 4K pages
clflush size    : 64
cache_alignment : 64
address sizes   : 40 bits physical, 48 bits virtual
power management: ts fid vid ttp

/proc/meminfo

MemTotal:      1020164 kB
MemFree:         55792 kB
Buffers:        184544 kB
Cached:         215348 kB
SwapCached:          0 kB
Active:         323112 kB
Inactive:       258312 kB
HighTotal:           0 kB
HighFree:            0 kB
LowTotal:      1020164 kB
LowFree:         55792 kB
SwapTotal:     2101640 kB
SwapFree:      2101640 kB
Dirty:               4 kB
Writeback:           0 kB
Mapped:         276916 kB
Slab:           356768 kB
CommitLimit:   2611720 kB
Committed_AS:  1951668 kB
PageTables:       9552 kB
VmallocTotal: 34359738367 kB
VmallocUsed:     12404 kB
VmallocChunk: 34359723635 kB
HugePages_Total:     0
HugePages_Free:      0
Hugepagesize:     2048 kB

------

CLOCK, RACING, CLOCK RACING, RACE CONDITION