From: Dan Merillat <harik.attar@gmail.com>
To: "Mukker, Atul" <atulm@lsil.com>
Cc: linux-scsi@vger.kernel.org
Subject: Re: Megaraid lockup on 2.6.[7-8]
Date: Mon, 9 Aug 2004 16:02:48 -0700 [thread overview]
Message-ID: <c0c0679004080916027cf2f42a@mail.gmail.com> (raw)
In-Reply-To: <c0c0679004080915331801dc0d@mail.gmail.com>
On Mon, 9 Aug 2004 15:33:23 -0700, Dan Merillat <harik.attar@gmail.com> wrote:
> So far, so good. When I stress-tested it I had a device-mapper related lockup,
> but no scsi/Megaraid problems. I'll report back in a few days if I
> get any further errors.
First lockup, but 2.20.2 recovered gracefully:
megaraid: aborting-37816 cmd=2a <c=1 t=0 l=0>
megaraid abort: 37816:53[255:0], fw owner
megaraid: aborting-37817 cmd=2a <c=1 t=0 l=0>
megaraid abort: 37817:34[255:0], fw owner
megaraid: aborting-37818 cmd=2a <c=1 t=0 l=0>
megaraid abort: 37818:26[255:0], fw owner
megaraid: aborting-37821 cmd=2a <c=1 t=0 l=0>
megaraid abort: 37821:18[255:0], fw owner
megaraid: aborting-37824 cmd=2a <c=1 t=0 l=0>
megaraid abort: 37824:7[255:0], fw owner
megaraid: reseting the host...
megaraid: 5 outstanding commands. Max wait 180 sec
megaraid mbox: Wait for 5 commands to complete:180
megaraid mbox: Wait for 5 commands to complete:175
megaraid mbox: Wait for 5 commands to complete:170
megaraid mbox: Wait for 5 commands to complete:165
megaraid mbox: reset sequence completed sucessfully
This time, it appears that we have 3 media errors on one of the drives
(Since this is the first time it's survived a timeout, it's the first
time I can actually get into megamgr without rebooting)
If so, mystery solved: Drive failure and bad error-handling code leads
to an undiagnosed lockup. I KNEW it was too sudden to be random
software bitrot.
next prev parent reply other threads:[~2004-08-09 23:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-08-09 14:11 Megaraid lockup on 2.6.[7-8] Mukker, Atul
2004-08-09 22:33 ` Dan Merillat
2004-08-09 23:02 ` Dan Merillat [this message]
-- strict thread matches above, loose matches on Subject: below --
2004-08-07 1:55 Dan Merillat
[not found] ` <1091882205l.7352l.1l@serve.riede.org>
2004-08-07 16:26 ` Dan Merillat
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=c0c0679004080916027cf2f42a@mail.gmail.com \
--to=harik.attar@gmail.com \
--cc=atulm@lsil.com \
--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 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.