From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
"Support, Software" <support@lsi.com>,
linux-scsi@vger.kernel.org, linux-acpi@vger.kernel.org,
bugme-daemon@bugzilla.kernel.org, "Moore,
Eric Dean" <Eric.Moore@lsi.com>,
kurk@shiftmail.org
Subject: Re: [Bugme-new] [Bug 11045] New: Bug in MPT Fusion 2.6.26-rc7 unbootable
Date: Tue, 08 Jul 2008 12:23:33 -0500 [thread overview]
Message-ID: <1215537813.3214.22.camel@localhost.localdomain> (raw)
In-Reply-To: <200807081051.33892.bjorn.helgaas@hp.com>
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
next prev parent reply other threads:[~2008-07-08 17:23 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <bug-11045-10286@http.bugzilla.kernel.org/>
2008-07-06 19:34 ` [Bugme-new] [Bug 11045] New: Bug in MPT Fusion 2.6.26-rc7 unbootable Andrew Morton
[not found] ` <C5679C710E19AF4C8D9C02FF5C72E3C133C9C76A@cosmail01.lsi.com>
2008-07-08 8:57 ` Andrew Morton
2008-07-08 14:08 ` James Bottomley
2008-07-08 16:51 ` Bjorn Helgaas
2008-07-08 17:23 ` James Bottomley [this message]
2008-07-08 20:56 ` Bjorn Helgaas
2008-07-08 21:47 ` Andrew Morton
2008-07-08 21:57 ` James Bottomley
2008-07-09 8:08 ` Prakash, Sathya
2008-07-10 14:24 ` kurk
2008-07-10 14:52 ` kurk
2008-07-10 23:44 ` Andrew Morton
2008-07-11 0:42 ` James Bottomley
2008-07-11 4:33 ` Prakash, Sathya
2008-07-11 14:05 ` James Bottomley
2008-07-10 14:24 ` kurk
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=1215537813.3214.22.camel@localhost.localdomain \
--to=james.bottomley@hansenpartnership.com \
--cc=Eric.Moore@lsi.com \
--cc=akpm@linux-foundation.org \
--cc=bjorn.helgaas@hp.com \
--cc=bugme-daemon@bugzilla.kernel.org \
--cc=kurk@shiftmail.org \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=support@lsi.com \
/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