[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <20080710155154.GB22862@redhat.com>
Date: Thu, 10 Jul 2008 10:51:54 -0500
From: David Teigland <teigland@...hat.com>
To: James Bottomley <James.Bottomley@...senPartnership.com>
Cc: Kamalesh Babulal <kamalesh@...ux.vnet.ibm.com>,
Stephen Rothwell <sfr@...b.auug.org.au>,
linux-next@...r.kernel.org, LKML <linux-kernel@...r.kernel.org>,
linux-scsi@...r.kernel.org, Eric.Moore@....com,
Andy Whitcroft <apw@...dowen.org>
Subject: Re: [BUG] linux-next: Tree for March 25 kernel oops, when loading mpt fusion driver - regression
On Mon, Jul 07, 2008 at 10:43:14AM -0500, James Bottomley wrote:
> On Mon, 2008-07-07 at 10:27 -0500, David Teigland wrote:
> > On Sun, Jul 06, 2008 at 02:23:35PM -0500, James Bottomley wrote:
> > > On Thu, 2008-06-26 at 15:38 -0500, David Teigland wrote:
> > > > On Wed, Mar 26, 2008 at 12:14:00PM +0530, Kamalesh Babulal wrote:
> > > > > Hi Stephen,
> > > > >
> > > > > Kernel bug is hit while booting up the next-20080325 kernel with MPT
> > > > > Fusion driver built in.This was reported previously for the
> > > > > next-20080320 kernel
> > > > > http://marc.info/?l=linux-next&m=120601013920868&w=2
> > > >
> > > > Hi, did you ever get this fixed? I've been having the same problem,
> > > > http://marc.info/?l=linux-scsi&m=121061780821823&w=4
> > > > still exists on 2.6.26-rc8 for me,
> > > >
> > > > Loading scsi_transport_spi.ko module
> > > > Loading mptscsih.ko module
> > > > Loading mptspi.ko module
> > > > Fusion MPT SPI Host driver 3.04.06
> > > > ACPI: PCI Interrupt 0000:86:01.0[A] -> GSI 32 (level, low) -> IRQ 32
> > > > mptbase: ioc0: Initiating bringup
> > > > ioc0: LSI53C1030 B2: Capabilities={Initiator,Target}
> > > > mptbase: ioc0: PCI-MSI enabled
> > >
> > > I speculate that this might be related to the problem. The fusion
> > > driver was recently flipped to default to MSI enable (previously it had
> > > disabled them). Could you boot it with the fusion module parameter
> > >
> > > mpt_msi_enable=0
> > >
> > > if it actually boots that will be a good confirmation that MSI is to
> > > blame.
> >
> > It all works using that option.
>
> It sounds like your motherboard might need to be added to the
> drivers/pci/quirks.c with quirk_disable_all_msi ... can you try a
> different card with MSI just to see if it's something specific either to
> the fusion or the location in the system?
I don't have easy access to the hardware, it's just some lab machine I was
told I could use for unrelated testing. Until this came up I'd never
heard of "MSI", or "Fusion" before, and still don't have much idea about
they are :-)
Dave
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Powered by blists - more mailing lists