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 14:57:48 -0700 (PDT)	[thread overview]
Message-ID: <20080708215748.BE7A910800B@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 #11 from anonymous@kernel-bugs.osdl.org  2008-07-08 14:57 -------
Reply-To: James.Bottomley@HansenPartnership.com

On Tue, 2008-07-08 at 14:47 -0700, Andrew Morton wrote:
> 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

That's fixed in the scsi-rc-fixes tree ... but it's a symptom, not a
cause.  If essential storage is on this adapter, the system will still
be unbootable.

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 21:57 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
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 [this message]
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=20080708215748.BE7A910800B@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