I have a Dell Poweredge 700 that is randomly locking up. After some
googling it seems quite possible that it is related to a bad APIC
implementation.
I suspect this problem because dmesg shows me this:
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:3 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:3 APIC version 20
WARNING: NR_CPUS limit of 1 reached. Processor ignored.
Why on earth is it "finding" a non-existant second processor :-(
I am passing "noapic and nolapic" at boot time but it still seems to
starting up APIC.
Do I need to get someone near the machine (its remote) to check the BIOS
settings?
The other APIC messages are:
$ dmesg|grep -i apic
ACPI: Local APIC address 0xfee00000
ACPI: LAPIC (acpi_id[0x01] lapic_id[0x00] enabled)
Processor #0 15:3 APIC version 20
ACPI: LAPIC (acpi_id[0x02] lapic_id[0x01] enabled)
Processor #1 15:3 APIC version 20
ACPI: LAPIC_NMI (acpi_id[0x01] high edge lint[0x1])
ACPI: LAPIC_NMI (acpi_id[0x02] high edge lint[0x1])
ACPI: Skipping IOAPIC probe due to 'noapic' option.
Using ACPI for processor (LAPIC) configuration information
OEM ID: DELL Product ID: PE 0167 APIC at: 0xFEE00000
I/O APIC #2 Version 32 at 0xFEC00000.
I/O APIC #3 Version 32 at 0xFEC10000.
Enabling APIC mode: Flat. Using 2 I/O APICs
Kernel command line: root=/dev/sda1 ro noapic nolapic quiet splash
mapped APIC to ffffd000 (fee00000)
mapped IOAPIC to ffffc000 (fec00000)
mapped IOAPIC to ffffb000 (fec10000)
BIOS bug, local APIC #0 not detected!...
^^^^ This worries me too!
TIA
--
SLUG - Sydney Linux User's Group Mailing List - http://slug.org.au/
Subscription info and FAQs: http://slug.org.au/faq/mailinglists.html
