Entering "acpi=noirq noapic" at the prompt in Grub when booting Linux fixed the problem of the fast clock on my Compaq Presario V2312 (Turion) running SUSI 9.3. I'll have to figure out where to add it in to a grub configuration file since I don't see a /boot/grub/grub.conf file on my distribution but that should not be a biggie. What I did wonder is where it is documented what this command actually does, and why it solves this problem. I'd like to know more about it in case there are other side effects that might come up later.

Thanks for the help y'all.

I am running a Compaq R4000 and the only side effect I have found is the battery moniter is not working, of course it was not working before I added the commands.

You need to enter the comands in /boot/grub/menu.lst

I do not know exactly what the comands do, I read about them HERE

Thanks a lot to MooseDaddy!

"acpi=noirq noapic" has finally fixed my problem. I cannot tell for sure whether it screwed anything else, but this annoying bug has now been fixed! Yahooooo!

I googled around a lot, but nothing worked.

thanks a lot moosedaddy! Worked great here (unbuntu 5.04 64)... Now i can finally use linux one my notebook (acer aspire 5022)...

btw: What excactly does the paramater "acpi=noirq noapic" do?

greet'z,
screen

I'm having the same problem on an AMD turion laptop: The clock is always messed up and the keystroke repetition is way too fast.
The "no_timer_check=0" addition didn't solve it but the "acpi=noirq noapic" seems to have done the trick. Also it looks like a former error message:
APIC error on CPU0: 00(40)
APIC error on CPU0: 40(40)
has disappeared from the boot sequence.
It's all good but I'm wondering what this all means? As far as I know APIC is some advanced interrupt control thing. Did this mean that with this parameter APIC is disabled? Have I lost some ACPI or APIC features?

APIC (advanced programmable interrupt controller) architecture, which supports the redirection of interrupts to multiple processors. Since you have only one processor, it won't hurt anything to turn off APIC. Also you don't need to use "acpi=noirq", "noapic" itself can solve the fast clock probelm.

Thanks a lot for the info, I will try the "noapic" alone.

Thats really so true. Now i know why it happens

First of all I would like to say that this is my first post. I installed and compiled kernel 2.6.19.1 on an AMD X2. Once I logged into to KDE, movies, sound, and clock were operating at a speed which seemed to be twice that of normal operation. After several recompiles, I resolved the issue by using the acpi=noirq noapic which worked quite well. I did not have luck with no_timer_check=0 however.

I have had this problem in 2 distributions after a kernel recompile, both Slack 11(moving from 2.4 to 2.6) and Suse 10.1 involving Athlon64s. If anyone has an answer as to why I would greatly appreciate it.

I don't know really.
In the meantime i changed couple of distros.
I am now with PCLinuxOS and everything works.
P. S.
I have never recompiled the kernel myself.
Regards.