This is what bug 699 is all about I think. As far as I can see, it is a
serious issue for people with MPS 1.4 systems: The system is unusable due to
wrong IRQ mappings. MPS 1.4 is used in most (all ?) PPro and PII SMP systems,
though often can be disabled. I can't say how many systems really rely on MPS
1.4. Workaround that works for most people is booting with pci=noacpi, though
I have reports of systems where this isn't the solution. MPS 1.1 systems
work, though this is more a coincidence than well coded ACPI behaviour.
The amount of people that can't possibly get Linux booting with ACPI enabled
will not be big. The amount of people that think it's annoying they have to
disable MPS 1.4 or ACPI to get a running system might be somewhat bigger. My
box only shuts down with ACPI, and thanks to MPS 1.4 my soundcard doesn't
glitch when there is heavy SCSI activity. (Onboard SCSI & Soundcard share the
interrupt when MPS 1.4 is disabled).
Basically, what happens is that ACPI forgets to look for MPS tables when no
MADT is found. It assumes the APIC should be set up in PIC mode, though the
APIC has been rerouted already. As a result, the irq entries in pci_dev are
filled with the "below 15" values, while the APIC generates "above 15"
interrupts.
Jos
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/