On Tue, 2008-07-08 at 10:51 -0600, Bjorn Helgaas wrote: > On Tuesday 08 July 2008 08:08:46 am James Bottomley wrote: > > That said, this line: > > > > mptbase: ioc0: ERROR - Doorbell ACK timeout (count=4999), IntStatus=80000009! > > > > is absolutely characteristic of a lost interrupt. > > > > With the current LSI driver, we have two possible causes for this. One > > is the usual ACPI screw up that we never seem to be able to fix. > > Which ACPI screw up is that? And what's the usual recipe? The usual screw up where subtle ACPI breakage from release to release causes some IRQs to get misrouted. Usually you start with noacpi and cycle through the pci routing options > I know about the ancient "pci=routeirq" recipe, but as far as I know, > there are no current problems that require that. If you actually read this bug report, you'll see there was a message ACPI: Resource is not an IRQ entry Just before the fusion IRQ failed to get delivered, so I think it's a good indicator that there *are* ACPI problems ... James -- To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
