On Tue, 5 Apr 2005, Andi Kleen wrote:
> Alternatively you can try to boot with noapic. Does that help?
Yes, with 'noapic' the system boots normally and the clock runs at normal
speed.
dmesg of 2.6.11.6 without any command line options. (default: ACPI
enabled, APIC enabled):
http://www-personal.engin.umich.edu/~wingc/apictimer/dmesg/dmesg-2.6.11.6-acpi-apic
/proc/interrupts on 2.6.11.6 with ACPI enabled, APIC enabled:
http://www-personal.engin.umich.edu/~wingc/apictimer/dmesg/interrupts-2.6.11-6-acpi-apic
(clock runs at double speed)
dmesg of 2.6.11.6 with 'noapic' command line option:
http://www-personal.engin.umich.edu/~wingc/apictimer/dmesg/dmesg-2.6.11.6-acpi-noapic
/proc/interrupts on 2.6.11.6 with 'noapic':
http://www-personal.engin.umich.edu/~wingc/apictimer/dmesg/interrupts-2.6.11-6-acpi-noapic
(clock runs normally)
Are you thinking of blacklisting the APIC on this system until we figure
out what's going on?
-Chris
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
