http://bugzilla.kernel.org/show_bug.cgi?id=11045 ------- Comment #10 from anonymous@xxxxxxxxxxxxxxxxxxxx 2008-07-08 14:53 ------- Reply-To: akpm@xxxxxxxxxxxxxxxxxxxx On Tue, 8 Jul 2008 14:56:53 -0600 Bjorn Helgaas <bjorn.helgaas@xxxxxx> wrote: > On Tuesday 08 July 2008 11:23:33 am James Bottomley wrote: > > On Tue, 2008-07-08 at 10:51 -0600, Bjorn Helgaas wrote: > > > 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 > > Don't worry, I wasn't trying to talk you out of an ACPI bug report; > I just wanted to get enough specifics so I could see whether it was > something I could fix. > > > 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 ... > > These messages also happen with 2.6.25, where the MPT Fusion driver > worked, so Kurk opened a separate bugzilla, > http://bugzilla.kernel.org/show_bug.cgi?id=11049 > for them. > > Yakui Zhao thinks the messages are harmless because they're > related to interrupt link devices that we don't use in IOAPIC mode, > and given that the driver works in 2.6.25, that seems plausible > to me. > > Regardless, the messages are alarming and annoying. I'd like > to understand them better, but I'll pursue that in the 11049 > bugzilla. > Let us not forget the other part of this report: BUG: unable to handle kernel NULL pointer dereference at 0000034c IP: [<f885cc5e>] :mptspi:mptspi_dv_renegotiate_work+0xa/0x9f Oops: 0000 [#1] SMP -- Configure bugmail: http://bugzilla.kernel.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug, or are watching the assignee. -- To unsubscribe from this list: send the line "unsubscribe linux-scsi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
