public inbox for linux-scsi@vger.kernel.org
 help / color / mirror / Atom feed
From: Paul Wagland <paul@kungfoocoder.org>
To: Linux SCSI mailing list <linux-scsi@vger.kernel.org>
Subject: megaraid: ABORTING problem
Date: Tue, 13 Apr 2004 16:26:52 +0200	[thread overview]
Message-ID: <1081866411.2111.11.camel@morsel.kungfoocoder.org> (raw)

Hi all,

In trying to do some performance analysis on my LSI Login SATA-150-6, I
set it off running bonnie against multiple filesystems against multiple
stripe sizes and RAID levels. Well, all was fine for about three days (I
was running a lot of tests ;-) and then I get back to my machine today
to discover that it was locked up, and the following was on the console:

megaraid: ABORTING-188cf36 cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf36[52], fw owner.
megaraid: ABORTING-188cf37 cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf37[51], fw owner.
megaraid: ABORTING-188cf38 cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf38[37], fw owner.
megaraid: ABORTING-188cf39 cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf39[3e], fw owner.
megaraid: ABORTING-188cf3a cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf3a[3], fw owner.
megaraid: ABORTING-188cf3b cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf3b[65], fw owner.
megaraid: ABORTING-188cf3c cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf3c[c], fw owner.
megaraid: ABORTING-188cf3d cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf3d[1e], fw owner.
megaraid: ABORTING-188cf3e cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf3e[57], fw owner.
megaraid: ABORTING-188cf3f cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf3f[b], fw owner.
megaraid: ABORTING-188cf40 cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf40[5d], fw owner.
megaraid: ABORTING-188cf41 cmd=2a <c=0 t=5 l=0>
megaraid: ABORTING-188cf41[5e], fw owner.


Does anyone know what is the cause of this failure?

I can see in the code that this comes out of the
megaraid_abort_and_reset() function, and this is in turn called by
megaraid_abort() and megaraid_reset(). These in turn appear to be called
from the SCSI layer? But why? And why did the machine hang?

Thanks in advance for any help,
Cheers,
Paul


             reply	other threads:[~2004-04-13 14:26 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-04-13 14:26 Paul Wagland [this message]
  -- strict thread matches above, loose matches on Subject: below --
2004-04-13 15:09 megaraid: ABORTING problem Mukker, Atul
2004-04-13 15:15 ` Paul Wagland
2004-04-13 16:01 Mukker, Atul
2004-04-14  9:18 Tomita, Haruo
2004-04-14 13:43 Bagalkote, Sreenivas

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=1081866411.2111.11.camel@morsel.kungfoocoder.org \
    --to=paul@kungfoocoder.org \
    --cc=linux-scsi@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