All of lore.kernel.org
 help / color / mirror / Atom feed
From: Chuck Ebbert <cebbert@redhat.com>
To: "Yang, Bo" <Bo.Yang@lsi.com>
Cc: Andrew Morton <akpm@linux-foundation.org>,
	Scott Shambarger <scott-lkml@shambarger.net>,
	linux-kernel@vger.kernel.org, "Patro,
	Sumant" <Sumant.Patro@lsi.com>,
	linux-scsi@vger.kernel.org,
	DL-MegaRAID Linux <megaraidlinux@lsi.com>,
	"Kolli, Neela" <Neela.Kolli@lsi.com>
Subject: Re: Oops in megaraid_mbox_dpc(), kernel 2.6.23.9-85.fc8.i686
Date: Thu, 07 Feb 2008 17:03:43 -0500	[thread overview]
Message-ID: <47AB803F.7070208@redhat.com> (raw)
In-Reply-To: <9738BCBE884FDB42801FAD8A7769C26501EE201D@NAMAIL1.ad.lsil.com>

On 02/06/2008 02:38 PM, Yang, Bo wrote:
> Andrew/Scott,
> 
> Can you give me more details about this issue?  Such as: MegaRAID
> Controller name, FW version, RAID configuration, host system info, how
> to reproduce this issue.  Also do you see the issue on other kernel
> versions.  
> 

He has hit the BUG() here in megaraid_mbox_dpc():

                // Make sure f/w has completed a valid command
                if (scb->state != SCB_ISSUED) {
                        con_log(CL_ANN, (KERN_CRIT
                        "megaraid critical err: invalid command %d:%d:%p\n",
                                scb->sno, scb->state, scp));
                        BUG();
                        continue;       // Must never happen!
                }

  reply	other threads:[~2008-02-07 22:03 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-02 23:03 Oops in megaraid_mbox_dpc(), kernel 2.6.23.9-85.fc8.i686 Scott Shambarger
2008-02-05 23:27 ` Andrew Morton
2008-02-06 19:38   ` Yang, Bo
2008-02-06 19:38     ` Yang, Bo
2008-02-07 22:03     ` Chuck Ebbert [this message]
2008-02-08  0:59     ` Scott Shambarger
2008-02-08  0:59       ` Scott Shambarger

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=47AB803F.7070208@redhat.com \
    --to=cebbert@redhat.com \
    --cc=Bo.Yang@lsi.com \
    --cc=Neela.Kolli@lsi.com \
    --cc=Sumant.Patro@lsi.com \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-scsi@vger.kernel.org \
    --cc=megaraidlinux@lsi.com \
    --cc=scott-lkml@shambarger.net \
    /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.