Subject: Re: [BUG]  linux-next: Tree for March 25 kernel oops, when loading
	mpt fusion driver - regression
From: James Bottomley <James.Bottomley@HansenPartnership.com>
To: David Teigland <teigland@redhat.com>
Cc: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>,
       Stephen Rothwell <sfr@canb.auug.org.au>, linux-next@vger.kernel.org,
       LKML <linux-kernel@vger.kernel.org>, linux-scsi@vger.kernel.org,
       Eric.Moore@lsi.com, Andy Whitcroft <apw@shadowen.org>
In-Reply-To: <20080707152708.GA10404@redhat.com>
References: <20080325175224.3ee62b09.sfr@canb.auug.org.au>
	 <47E9F0B0.4060006@linux.vnet.ibm.com> <20080626203857.GB3815@redhat.com>
	 <1215372215.4197.28.camel@localhost.localdomain>
	 <20080707152708.GA10404@redhat.com>
Content-Type: text/plain
Date: Mon, 07 Jul 2008 10:43:14 -0500
Message-Id: <1215445394.3274.26.camel@localhost.localdomain>
Mime-Version: 1.0
Content-Transfer-Encoding: 7bit
Sender: linux-kernel-owner@vger.kernel.org
Content-Length: 1952
Lines: 50

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?

Thanks,

James


--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/