http://bugzilla.kernel.org/show_bug.cgi?id=3927
------- Additional Comments From [EMAIL PROTECTED] 2006-01-31 04:05 ------- AK> ... noapic doesn't use any interrupt routing tables in the DSDT. Well, it does; have a look at my DSDT that I posted here: http://bugzilla.kernel.org/attachment.cgi?id=4448&action=view. When the APIC is not used, ACPI uses the LNK[A-H] devices in the DSDT to determine to which interrupt pins of the PIC the PCI devices are connected. If, as in my case, the SATA controller is (claimed to be) connected to LNK0, but this link is not declared as a device (only LNKA -- LNKH are), ACPI does not enable the controllers interrupt, the boot stops. I think with pci=noacpi Linux asks the BIOS about the interrupt routing and doesnt look at the DSDT for this. AK> ... my understanding is that XP doesn't use the APIC AK> in many circumstances neither. All the machines in my department which are bought after 2004 or so (six different models) show 24 interrupts in XPs Device Manager, and as I understand it, this is only possible with an APIC. Of course I dont know what XP does, but my guess is that if it finds an APIC, it uses it, and the BIOS builders hack at the DSDT et al. until XP works -- and no longer. ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is. ------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Do you grep through log files for problems? Stop! Download the new AJAX search engine that makes searching your log files as easy as surfing the web. DOWNLOAD SPLUNK! http://sel.as-us.falkag.net/sel?cmd=lnk&kid=103432&bid=230486&dat=121642 _______________________________________________ acpi-bugzilla mailing list acpi-bugzilla@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/acpi-bugzilla
