linux-next.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Sachin Sant <sachinp@in.ibm.com>
To: "Desai, Kashyap" <Kashyap.Desai@lsi.com>
Cc: "linux-next@vger.kernel.org" <linux-next@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	"Moore, Eric" <Eric.Moore@lsi.com>
Subject: Re: [-next Feb 9] Boot failure on x86_64: mptbase fails to initialize
Date: Wed, 10 Mar 2010 15:25:27 +0530	[thread overview]
Message-ID: <4B976C8F.1000703@in.ibm.com> (raw)
In-Reply-To: <1C9608B8A4CD534FB19C7C7543CBB249020E1A7BF0@inbmail02.lsi.com>

Desai, Kashyap wrote:
> Sachin,
>
> This may be related to something specific to your system's APIC/or bad HW rather than pure driver issue.
> Below line from log is important to note.
> "mptsas 0000:03:04.0: can't find IRQ for PCI INT A; probably buggy MP table"
>
> It means LSI controller is not able to reserve IRQ line and that is where all problem starts.
> Need to broaden the scope of the issue.
>
> Another confusing thing to me.
> I have seen "probably buggy MP table" print only in arch/x86, but you have mentioned that in your case arch is x86_64.
>
> Thanks,
> Kashyap
>   
This actually was because of some other problem.

Here is the post for it.
http://marc.info/?l=linux-kernel&m=126741813906116&w=2

Which was eventually fixed. Patch is available here.
http://marc.info/?l=linux-kernel&m=126745177832615&w=2

Thanks
-Sachin

>
>
>   
>> -----Original Message-----
>> From: linux-scsi-owner@vger.kernel.org [mailto:linux-scsi-
>> owner@vger.kernel.org] On Behalf Of Sachin Sant
>> Sent: Tuesday, February 09, 2010 6:12 PM
>> To: linux-scsi
>> Cc: linux-next@vger.kernel.org; LKML; Moore, Eric
>> Subject: [-next Feb 9] Boot failure on x86_64: mptbase fails to
>> initialize
>>
>> Today's next failed to boot on my 4 way x86_64 box because of mptbase
>> driver initialization failure.
>>
>> Snippet of messages during boot :
>>
>> Fusion MPT SAS Host driver 3.04.14
>> mptsas 0000:03:04.0: can't find IRQ for PCI INT A; probably buggy MP
>> table
>> mptbase: ioc0: Initiating bringup
>> ioc0: LSISAS1064 A3: Capabilities={Initiator}
>> mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
>> mptbase: ioc0: Initiating recovery
>> mptbase: ioc0: Attempting Retry Config request type 0x1, page 0x2,
>> action 0
>> mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
>> mptbase: ioc0: Initiating recovery
>> mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
>> mptbase: ioc0: Initiating recovery
>> mptbase: ioc0: Attempting Retry Config request type 0x1, page 0x1,
>> action 0
>> mptbase: ioc0: WARNING - Issuing Reset from mpt_config!!
>>
>> Eventually machine fails to boot. I have similar problem on a x86 box
>> but with IPS driver. So might not be a driver specific issue.
>>
>> I had similar problem with yesterday's next.IIRC the last successful
>> boot was with next-20100203.
>>
>> Have attached the boot log from x86_64 box.
>>
>> Thanks
>> -Sachin
>>
>>
>> --
>>
>> ---------------------------------
>> Sachin Sant
>> IBM Linux Technology Center
>> India Systems and Technology Labs
>> Bangalore, India
>> ---------------------------------
>>     
>
>   


-- 

---------------------------------
Sachin Sant
IBM Linux Technology Center
India Systems and Technology Labs
Bangalore, India
---------------------------------

      reply	other threads:[~2010-03-10  9:55 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-02-09  8:07 linux-next: Tree for February 9 Stephen Rothwell
2010-02-09 12:41 ` [-next Feb 9] Boot failure on x86_64: mptbase fails to initialize Sachin Sant
2010-03-10  9:45   ` Desai, Kashyap
2010-03-10  9:55     ` Sachin Sant [this message]

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=4B976C8F.1000703@in.ibm.com \
    --to=sachinp@in.ibm.com \
    --cc=Eric.Moore@lsi.com \
    --cc=Kashyap.Desai@lsi.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-next@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;
as well as URLs for NNTP newsgroup(s).