Bug#252289: general: system clock

[Antos Andras <antos@szit.bme.hu>]

On Thu, 17 Jun 2004, Andrew Suffield wrote:
> > > That's probably a misconfigured APIC. Kernel/hardware bug. Don't use
> > > the APIC, or find a fix for your motherboard.
> ...But there's a kernel command-line argument for it as well.
> ACPI is probably irrelevant, although you never know with some BIOSes.

On Mon, 21 Jun 2004 mjr@dsl.pipex.com wrote:
> did the "noapic" kernel option fix your clock troubles?

Yes!
So far, I have the following experience: Booting the kernel with parameters

'noapic' and 'acpi=off'  =>  no problem so far
only 'noapic'  =>  no problem so far
only 'acpi=off'  =>  the kernel clock is not so fast, but after a while
      it was stuck again

So apic is the first to blame, indeed. Could I help to further narrow what 
is causing the problem ? Is it still can be a hardware and software 
(kernel) bug ? Should I fiddle with the APIC kernel options one by one ?

Thanks,
Andras