From: Kamalesh Babulal <kamalesh@linux.vnet.ibm.com>
To: James Bottomley <James.Bottomley@HansenPartnership.com>
Cc: David Teigland <teigland@redhat.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>
Subject: Re: [BUG] linux-next: Tree for March 25 kernel oops, when loading mpt fusion driver - regression
Date: Tue, 08 Jul 2008 16:18:09 +0530 [thread overview]
Message-ID: <487345E9.8090505@linux.vnet.ibm.com> (raw)
In-Reply-To: <1215462321.3274.34.camel@localhost.localdomain>
James Bottomley wrote:
> On Tue, 2008-07-08 at 01:47 +0530, Kamalesh Babulal wrote:
>> 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.
>>>
>>>> mptbase: ioc0: Initiating recovery
>>> This I suspect is because of a lost interrupt.
>>>
>>>> BUG: unable to handle kernel NULL pointer dereference at 0000000000000948
>>> And this one looks to be a second bug: The MSI fault path is actually
>>> causing this oops.
>>>
>>> James
>>>
>> Hi James,
>>
>> Kernel Bug is still reproducible with 2.6.26-rc9-git1 kernel, I tried booting with mpt_msi_enable=0
>> as boot paramenter, but the call trace remains the same
>>
>> oading mptbase.ko module[ 6.766853] Fusion MPT base driver 3.04.06
>>
>> [ 6.783482] Copyright (c) 1999-2007 LSI Corporation
>> Loading mptscsih.ko module
>> Loading mptspi.ko module
>> [ 6.813157] Fusion MPT SPI Host driver 3.04.06
>> [ 6.827369] ACPI: PCI Interrupt 0000:01:01.0[A] -> GSI 22 (level, low) -> IRQ 22
>> [ 6.850624] mptbase: ioc0: Initiating bringup
>> [ 6.985601] ioc0: LSI53C1030 B2: Capabilities={Initiator}
>> [ 7.002711] mptbase: ioc0: PCI-MSI enabled
> ^^^^^^^^^^^^^^^
>
> If you had successfully specified mpt_msi_enable=0 this line wouldn't
> appear.
>
> My best guess is that you incorrectly specified it as a kernel command
> line parameter rather than a module parameter.
>
> James
>
Hi James,
Sorry my fault :(, the kernel bug is not reproducible after disabling it.
--
Thanks & Regards,
Kamalesh Babulal,
Linux Technology Center,
IBM, ISTL.
next prev parent reply other threads:[~2008-07-08 10:55 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-25 6:52 linux-next: Tree for March 25 Stephen Rothwell
2008-03-25 21:39 ` linux-next: Tree for March 25 (ocfs2 build) Randy Dunlap
2008-04-04 19:47 ` Mark Fasheh
2008-04-04 19:56 ` Randy Dunlap
2008-03-26 6:44 ` [BUG] linux-next: Tree for March 25 kernel oops, when loading mpt fusion driver - regression Kamalesh Babulal
2008-06-26 20:38 ` David Teigland
2008-06-27 17:42 ` Kamalesh Babulal
2008-07-06 19:23 ` James Bottomley
2008-07-07 15:27 ` David Teigland
2008-07-07 15:43 ` James Bottomley
2008-07-10 15:51 ` David Teigland
2008-07-07 20:17 ` Kamalesh Babulal
2008-07-07 20:25 ` James Bottomley
2008-07-08 10:48 ` Kamalesh Babulal [this message]
-- strict thread matches above, loose matches on Subject: below --
2008-06-27 14:26 David Teigland
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=487345E9.8090505@linux.vnet.ibm.com \
--to=kamalesh@linux.vnet.ibm.com \
--cc=Eric.Moore@lsi.com \
--cc=James.Bottomley@HansenPartnership.com \
--cc=apw@shadowen.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-next@vger.kernel.org \
--cc=linux-scsi@vger.kernel.org \
--cc=sfr@canb.auug.org.au \
--cc=teigland@redhat.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.