public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: dormando <dormando@rydia.net>
To: "Ju, Seokmann" <Seokmann.Ju@lsil.com>
Cc: linux-kernel@vger.kernel.org
Subject: Re: x86_86 SMP megaraid_mbox hangups and panics.
Date: Wed, 12 Apr 2006 10:52:50 -0700	[thread overview]
Message-ID: <443D3E72.1050408@rydia.net> (raw)
In-Reply-To: <890BF3111FB9484E9526987D912B261901BCC1@NAMAIL3.ad.lsil.com>

Ju, Seokmann wrote:
> Hi,
>> Most of the time the server hits: "megaraid: probe new device" - with 
>> the device information, then hangs and starts the 180 second 
>> countdown: 
>> "megaraid: wait for FW to boot [blah]"
>> After which I get a VFS panic for not having a root disk.
> This means the controller is NOT taking any commands from the driver at that time.
> In other words, the F/W is NOT ready to take any command, yet.
> It sounds like that the controller is NOT in good condition for some reason and needs to check sanity of it.
> You may want to check with LSI logic SE team.
> 
> Thank you,

Can you confirm that you read my whole message? I might be a complete 
idiot, but let me reiterate some highlights and add a few more details 
from my last mail:

If I build a 32-bit SMP OR 64-bit UP kernel, the cards will boot and 
work *every time*.

Most of the time this is a *kernel panic* in megaraid_ack_sequence, 
somewhere through megaraid_isr in megaraid_mbox.c
*Sometimes* it results in the firmware hanging like you mentioned above.
If I compile the drivers as modules instead of statically, this 
*sometimes* results in the machine booting all the way. Once the machine 
boots up, I can give it a good 'ole I/O beatdown and it does not flinch.

As in: I boot it once, it hangs. I reboot, it panics. I reboot, it 
panics. I reboot, it works. I have 16 cards in 16 systems that all 
exhibit the same behavior. Looks like an x86_64 SMP timing issue of some 
kind to me, and less of a card issue. Please correct me if I am wrong!

-Dormando

  reply	other threads:[~2006-04-12 17:53 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-04-12 12:26 x86_86 SMP megaraid_mbox hangups and panics Ju, Seokmann
2006-04-12 17:52 ` dormando [this message]
  -- strict thread matches above, loose matches on Subject: below --
2006-04-12 18:33 Ju, Seokmann
2006-04-13 21:31 ` dormando
2006-04-12  0:33 dormando
2006-04-12  0:49 ` dormando

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=443D3E72.1050408@rydia.net \
    --to=dormando@rydia.net \
    --cc=Seokmann.Ju@lsil.com \
    --cc=linux-kernel@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