From: Andrew Morton <akpm@linux-foundation.org>
To: Bjorn Helgaas <bjorn.helgaas@hp.com>
Cc: James Bottomley <James.Bottomley@hansenpartnership.com>,
"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, 8 Jul 2008 14:47:20 -0700 [thread overview]
Message-ID: <20080708144720.998a13f2.akpm@linux-foundation.org> (raw)
In-Reply-To: <200807081456.53460.bjorn.helgaas@hp.com>
On Tue, 8 Jul 2008 14:56:53 -0600 Bjorn Helgaas <bjorn.helgaas@hp.com> 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
next prev parent reply other threads:[~2008-07-08 21:47 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
2008-07-08 20:56 ` Bjorn Helgaas
2008-07-08 21:47 ` Andrew Morton [this message]
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=20080708144720.998a13f2.akpm@linux-foundation.org \
--to=akpm@linux-foundation.org \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@hansenpartnership.com \
--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