public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: bugme-daemon@bugzilla.kernel.org
To: linux-scsi@vger.kernel.org
Subject: [Bug 11045] Bug in MPT Fusion 2.6.26-rc7 unbootable
Date: Tue,  8 Jul 2008 09:52:32 -0700 (PDT)	[thread overview]
Message-ID: <20080708165232.8D5F9108035@picon.linux-foundation.org> (raw)
In-Reply-To: <bug-11045-11613@http.bugzilla.kernel.org/>

http://bugzilla.kernel.org/show_bug.cgi?id=11045





------- Comment #7 from bjorn.helgaas@hp.com  2008-07-08 09:52 -------
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?

I know about the ancient "pci=routeirq" recipe, but as far as I know,
there are no current problems that require that.

> 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.

  parent reply	other threads:[~2008-07-08 16:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <bug-11045-11613@http.bugzilla.kernel.org/>
2008-07-06 18:58 ` [Bug 11045] Bug in MPT Fusion 2.6.26-rc7 unbootable bugme-daemon
2008-07-06 19:34 ` bugme-daemon
2008-07-06 20:28 ` bugme-daemon
2008-07-06 20:50 ` bugme-daemon
2008-07-07  9:36 ` bugme-daemon
2008-07-08  9:03 ` bugme-daemon
2008-07-08 14:09 ` bugme-daemon
2008-07-08 16:52 ` bugme-daemon [this message]
2008-07-08 17:24 ` bugme-daemon
2008-07-08 20:57 ` bugme-daemon
2008-07-08 21:53 ` bugme-daemon
2008-07-08 21:57 ` bugme-daemon
2008-07-09  8:19 ` bugme-daemon
2008-07-09  8:40 ` bugme-daemon
2008-07-10 13:57 ` bugme-daemon
2008-07-10 14:25 ` bugme-daemon
2008-07-10 14:25 ` bugme-daemon
2008-07-10 16:02 ` bugme-daemon
2008-07-10 23:50 ` bugme-daemon
2008-07-11  0:42 ` bugme-daemon
2008-07-11  4:35 ` bugme-daemon
2008-07-11 14:06 ` bugme-daemon
2008-07-16 20:40 ` bugme-daemon

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20080708165232.8D5F9108035@picon.linux-foundation.org \
    --to=bugme-daemon@bugzilla.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox