From owner-freebsd-scsi  Tue Mar  7  6:59:36 2000
Delivered-To: freebsd-scsi@freebsd.org
Received: from feral.com (feral.com [192.67.166.1])
	by hub.freebsd.org (Postfix) with ESMTP id E740237BC09
	for <scsi@FreeBSD.ORG>; Tue,  7 Mar 2000 06:59:33 -0800 (PST)
	(envelope-from mjacob@feral.com)
Received: from beppo.feral.com (beppo [192.67.166.79])
	by feral.com (8.9.3/8.9.3) with ESMTP id GAA12297;
	Tue, 7 Mar 2000 06:59:28 -0800
Date: Tue, 7 Mar 2000 06:59:22 -0800 (PST)
From: Matthew Jacob <mjacob@feral.com>
Reply-To: mjacob@feral.com
To: Nick Hibma <n_hibma@calcaphon.com>
Cc: FreeBSD SCSI Mailing List <scsi@FreeBSD.ORG>
Subject: Re: first INQUIRY goes round in circles (fwd)
In-Reply-To: <Pine.BSF.4.20.0003071438580.1418-100000@localhost>
Message-ID: <Pine.BSF.4.10.10003070658210.26840-100000@beppo.feral.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-scsi@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org


> Transport problems (so-called wire errors) are handled in the USB part
> and are signalled differently. They are reported as CAM_REQ_CMP_ERR.

Uh, the USB adapter can't tell when the *target* has gotten a prity error.

> 
> > *The second INQUIRY that FreeBSD's xpt_probe always sends that asks for the
> > VPD info will generally always get a CHECK CONDITION for devices that don't
> > support VDP info, so blindly saying "don't request sense after an INQUIRY" is
> > a Bad Thing To Do (tm) as it will leave the latched up Illegal Bit in CDB for
> > the next command to have to cope with- which will be the poor old Test Unit
> > Ready.
> 
> In that case the command or data transport will fail. This means that
> SENSE will be requested.
> 

Uh, okay.




To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-scsi" in the body of the message