http://bugzilla.kernel.org/show_bug.cgi?id=11045 ------- Comment #6 from anonymous@xxxxxxxxxxxxxxxxxxxx 2008-07-08 07:09 ------- Reply-To: James.Bottomley@xxxxxxxxxxxxxxxxxxxxx On Tue, 2008-07-08 at 01:57 -0700, Andrew Morton wrote: > You removed everyone from cc. Please don't do that - there's not much > point in asking me to do things - this bug is reported by > kurk@xxxxxxxxxxxxxx > > I don't know what "we do not assist with compiling drivers" can possibly > mean. Eric, can you please help here? heh, well, cc'ing a support line on a technical bug report isn't necessarily conducive to producing useful results ... what we're discussing is probably already at level 4 or 5 (the real engineering problems). Support calls go in at levels 1-3 (as in consult manual and spit out canned response before triaging for escalation). 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. The other is that the driver recently enabled MSI (commit 23a274c8a5adafc74a66f16988776fc7dd6f6e51 in v2.6.26-rc1). For the former, just follow the usual ACPI screw up recipe. For the latter, you should see this message in the boot up: mptbase: ioc0: PCI-MSI enabled MSI can be turned off again by using the module parameter mpt_msi_enable=0. Unfortunately, the true fix is to find out if the motherboard really has a global MSI problem (and I know MSI works with the LSI because I have a 1030 in an ia64 system here working just fine) and add it to the PCI quirks file as unable to use MSI. James -- 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
