From: Xose Vazquez Perez <xose@wanadoo.es>
To: Gabor Burjan <buga@buvoshetes.hu>,
linux-scsi <linux-scsi@vger.kernel.org>
Subject: Re: problem with megaraid2 driver
Date: Sat, 29 Nov 2003 16:38:57 +0100 [thread overview]
Message-ID: <3FC8BD91.6060201@wanadoo.es> (raw)
In-Reply-To: 20031128155020.GB18860@odin.sis.hu
Gabor Burjan wrote:
> Is that possible that only the new driver triggers the problem which is
> "built-in" in the firmware, while using the old driver everything seems
> to be OK?
1.18k and 2.00.9 are very different drivers.
It looks like the firmware of the board is unable to
complete some commands of the pending list.
megaraid: aborting-4027815 cmd=2a <c=0 t=0 l=0>
megarid: Waiting for 11 commands to flush: iter:0
megarid: Waiting for 11 commands to flush: iter:1000
megarid: Waiting for 11 commands to flush: iter:2000
megaraid: aborted cmd 3d75a7[76] complete.
megarid: Waiting for 8 commands to flush: iter:3000
[... 4000, 5000, 6000, ... 59000]
megarid: Waiting for 8 commands to flush: iter:60000
megaraid: critical hardware error!
If those command were completed you would see the message:
"megaraid: abort sequence successfully complete".
So, try latest firmware.
--
There are 10 kinds of people.
Those that know to count in binary and those that no.
next prev parent reply other threads:[~2003-11-29 15:39 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-11-28 15:27 problem with megaraid2 driver Xose Vazquez Perez
2003-11-28 15:50 ` Gabor Burjan
2003-11-29 15:38 ` Xose Vazquez Perez [this message]
2003-12-04 9:56 ` Gabor Burjan
-- strict thread matches above, loose matches on Subject: below --
2003-11-28 14:17 Gabor Burjan
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=3FC8BD91.6060201@wanadoo.es \
--to=xose@wanadoo.es \
--cc=buga@buvoshetes.hu \
--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.