From: James Bottomley <James.Bottomley@SteelEye.com>
To: Hannes Reinecke <hare@suse.de>
Cc: SCSI Mailing List <linux-scsi@vger.kernel.org>
Subject: Re: Overlapped command error handling
Date: Thu, 02 Feb 2006 09:12:27 -0600 [thread overview]
Message-ID: <1138893147.3363.3.camel@mulgrave> (raw)
In-Reply-To: <43E20272.5000506@suse.de>
On Thu, 2006-02-02 at 14:00 +0100, Hannes Reinecke wrote:
> It looks to me as if the device has aborted _both_ commands when
> returning the 'overlapped commands attempted' sense.
> Is that conformant behaviour?
>
> SCSI-2 states in section 7.5.2:
> A target that detects an incorrect initiator connection shall abort all
> I/O processes for the initiator on the logical unit or target routine
> and shall return CHECK CONDITION status. The sense key shall be set to
> ABORTED COMMAND and the additional sense code shall be set to OVERLAPPED
> COMMANDS ATTEMPTED.
Actually, I think it's probably complaining about tag reuse in the sense
of SAM-3 section 5.9.3. You return this sense if an initiator attempts
to use a duplicate tag. Since the aic79xx manges its own tags, then
it's probably a driver error. You could verify this by having the
aic79xx print out the tag as it sends the command out on the wire. (The
device does support TCQ, doesn't it?)
James
next prev parent reply other threads:[~2006-02-02 15:12 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-02-02 13:00 Overlapped command error handling Hannes Reinecke
2006-02-02 15:12 ` James Bottomley [this message]
2006-02-03 9:34 ` Hannes Reinecke
2006-02-03 15:31 ` James Bottomley
-- strict thread matches above, loose matches on Subject: below --
2006-02-03 11:00 Emmanuel Fusté
2006-02-03 11:13 Emmanuel Fusté
2006-02-04 17:01 Emmanuel Fusté
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=1138893147.3363.3.camel@mulgrave \
--to=james.bottomley@steeleye.com \
--cc=hare@suse.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