Date: Wed, 16 Jun 2010 16:31:14 -0400 From: Andrew Boyer <aboyer@averesystems.com> To: Matthew Jacob <mj@feral.com> Cc: freebsd-scsi@freebsd.org Subject: Re: Overlapped Commands error Message-ID: <A29A9125-871C-42F0-90D6-85EF96602419@averesystems.com> In-Reply-To: <4C1930BF.3090408@feral.com> References: <51DD9715-89B2-4058-A4FE-7097603013CC@averesystems.com> <4C1930BF.3090408@feral.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Jun 16, 2010, at 4:14 PM, Matthew Jacob wrote:
>> Can anyone point me to where in the stack the command identifier is =
assigned? I see where MPT assigns tags in target mode, but it's the =
initiator in this case. Any advice?
>=20
> The mpt f/w assigns tags. Don't really know what happened here.
>=20
>> Also, is CAM doing the right thing by retrying? scsi_error_action() =
in cam/scsi/scsi_all.c always sets the retry bit on aborted commands, =
even though the spec quoted above makes it sound like this should be a =
fatal error ("This is considered a catastrophic failure on the part of =
the SCSI initiator device"). Should scsi_error_action() be looking at =
the Additional Sense Code?
>=20
> Not really, IMO. It's up to each periph driver to decide whether =
commands are statefull or can be retried with impunity.
>=20
OK. Thank you for looking into it.
-Andrew
--------------------------------------------------
Andrew Boyer aboyer@averesystems.com
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A29A9125-871C-42F0-90D6-85EF96602419>