The patch titled pci: don't move ioapics below PCI bridge has been added to the -mm tree. Its filename is pci-dont-move-ioapics-below-pci-bridge.patch See http://www.zip.com.au/~akpm/linux/patches/stuff/added-to-mm.txt to find out what to do about this ------------------------------------------------------ Subject: pci: don't move ioapics below PCI bridge From: Kimball Murray <kimball.murray@xxxxxxxxx> A recent Stratus x86_64 platform uses a system ioapic that is a PCI device located below a PCI bridge. Other platforms like this may exist. This patch fixes a problem wherein the kernel's PCI setup code moves the ioapic to an address other than that assigned by the BIOS. It simply adds another exclusion (which already includes classless devices and host bridges) to the function pbus_assign_resources_sorted so that it will not move the ioapic. If the ioapic is moved, the fixmap mapping to it is broken, so the OS should leave it alone. Cc: Greg KH <greg@xxxxxxxxx> Signed-off-by: Andrew Morton <akpm@xxxxxxxx> --- drivers/pci/setup-bus.c | 5 +++-- 1 files changed, 3 insertions(+), 2 deletions(-) diff -puN drivers/pci/setup-bus.c~pci-dont-move-ioapics-below-pci-bridge drivers/pci/setup-bus.c --- 25/drivers/pci/setup-bus.c~pci-dont-move-ioapics-below-pci-bridge Wed May 31 16:12:59 2006 +++ 25-akpm/drivers/pci/setup-bus.c Wed May 31 16:12:59 2006 @@ -55,9 +55,10 @@ pbus_assign_resources_sorted(struct pci_ list_for_each_entry(dev, &bus->devices, bus_list) { u16 class = dev->class >> 8; - /* Don't touch classless devices and host bridges. */ + /* Don't touch classless devices or host bridges or ioapics. */ if (class == PCI_CLASS_NOT_DEFINED || - class == PCI_CLASS_BRIDGE_HOST) + class == PCI_CLASS_BRIDGE_HOST || + class == PCI_CLASS_SYSTEM_PIC) continue; pdev_sort_resources(dev, &head); _ Patches currently in -mm which might be from kimball.murray@xxxxxxxxx are pci-dont-move-ioapics-below-pci-bridge.patch - To unsubscribe from this list: send the line "unsubscribe mm-commits" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html