From: Christian Iversen <chrivers@iversen-net.dk>
To: linux-scsi@vger.kernel.org
Subject: Re: Controller failing, driver not behaving nicely
Date: Wed, 21 Jun 2006 03:08:57 +0200 [thread overview]
Message-ID: <200606210308.57669.chrivers@iversen-net.dk> (raw)
In-Reply-To: <b1bc6a000606201547r11916e86g814d006c99ce386e@mail.gmail.com>
On Wednesday 21 June 2006 00:47, adam radford wrote:
> Christian,
>
> 0x28 is the scsi opcode for READ_10, which means the command that
> failed was a read command.
Makes sense - that just happened to be what the kernel requested at the time.
> The driver is trying to reset the card, however it is failing the reset.
>
> "AEN drain failed, retrying." means your card is not responding.
I assume it's trying to flush all pending commands or somesuch? What is AEN?
> I would suggest reseating your card if you have moved it recently,
I have - but only because I had this problem before, and I tried to solve it
that way. So that's not going to work, I'm afraid.
> or the card could be dying in which case you should contact 3ware/AMCC
> support.
Yeah I feared that. Too bad, it was a good card :-(
(It's bought off of eBay, so I don't think there's any hope for a
replacement).
Thank you very much for the help!
Wait - how is it that a driver can't reset the card, but a hw reset always
can? Is there some more fundamental type of reset possible, than what the
driver currently tries? Or would that require resetting everything?
It would be ultra-neat if the driver could just stall for a few seconds (or
even a minute). That'd be so much more bearable, compared to a terabyte-class
raid5 just suddenly failing.
Or at least, maybe the driver could try to reset the card a few more times?
Sometimes it seems to work after a couple of attempts.
--
Regards,
Christian Iversen
prev parent reply other threads:[~2006-06-21 1:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-06-20 21:02 Controller failing, driver not behaving nicely Christian Iversen
2006-06-20 22:47 ` adam radford
2006-06-21 1:08 ` Christian Iversen [this message]
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=200606210308.57669.chrivers@iversen-net.dk \
--to=chrivers@iversen-net.dk \
--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