From: James Bottomley <James.Bottomley@SteelEye.com>
To: "Bagalkote, Sreenivas" <Sreenivas.Bagalkote@engenio.com>
Cc: "'linux-scsi@vger.kernel.org'" <linux-scsi@vger.kernel.org>,
'Christoph Hellwig' <hch@infradead.org>,
"'hch@lst.de'" <hch@lst.de>,
"Kolli, Neela Syam" <Neela.Kolli@engenio.com>
Subject: RE: [2.4.21] Spurious ABORTs
Date: Tue, 27 Sep 2005 12:18:21 -0500 [thread overview]
Message-ID: <1127841501.4814.53.camel@mulgrave> (raw)
In-Reply-To: <0E3FA95632D6D047BA649F95DAB60E57060CD1DF@exa-atlanta>
On Tue, 2005-09-27 at 13:10 -0400, Bagalkote, Sreenivas wrote:
> What do you mean by "actually do a reset"? I see that firmware doesn't
> have any pending commands. So I simply return success from reset routine.
> Do you see any problem in this? After a hundred or so such cycles, the
> system is frozen. I should also tell you that if I introduce abort handler
> and return success for all the completed commands, I don't see the OS hang.
Well, yes, for two reasons
1. you do clustering, so a reset request could be from a reservation
breaking protocol
2. The fact that the eh activated indicates something went wrong. If
you take no corrective action and the test unit ready that follows the
reset fails or times out then the device will be taken offline.
James
next prev parent reply other threads:[~2005-09-27 17:18 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-09-27 17:10 [2.4.21] Spurious ABORTs Bagalkote, Sreenivas
2005-09-27 17:18 ` James Bottomley [this message]
-- strict thread matches above, loose matches on Subject: below --
2005-09-27 19:48 Bagalkote, Sreenivas
2005-09-27 20:10 ` James Bottomley
2005-09-27 16:39 Bagalkote, Sreenivas
2005-09-27 17:00 ` James Bottomley
2005-09-27 16:18 Bagalkote, Sreenivas
2005-09-27 16:32 ` James Bottomley
2005-09-23 21:28 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=1127841501.4814.53.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=Neela.Kolli@engenio.com \
--cc=Sreenivas.Bagalkote@engenio.com \
--cc=hch@infradead.org \
--cc=hch@lst.de \
--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