From owner-freebsd-scsi Wed Oct 6 14:43:48 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from caspian.plutotech.com (caspian.plutotech.com [206.168.67.80]) by hub.freebsd.org (Postfix) with ESMTP id B86D915163 for ; Wed, 6 Oct 1999 14:43:42 -0700 (PDT) (envelope-from gibbs@caspian.plutotech.com) Received: from caspian.plutotech.com (localhost [127.0.0.1]) by caspian.plutotech.com (8.9.3/8.9.1) with ESMTP id PAA11327; Wed, 6 Oct 1999 15:43:41 -0600 (MDT) (envelope-from gibbs@caspian.plutotech.com) Message-Id: <199910062143.PAA11327@caspian.plutotech.com> X-Mailer: exmh version 2.0.2 2/24/98 To: Gerard Roudier Cc: Matthew Jacob , "Justin T. Gibbs" , Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-reply-to: Your message of "Wed, 06 Oct 1999 23:57:07 +0200." Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Date: Wed, 06 Oct 1999 15:43:41 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Also, for some older peripherals I've found that if they detect a pari= ty >> error when receiving data they just drop off the bus rather than go to= the >> bother of completing the command first. > >The behaviour of those old peripherals does not look that bad to me, >even if some better one may be possible. Reporting sense information exonerates the device from your suspect list.= Without that information, you cannot assume that the device did not simply lose its mind. The sense information will also allow you to attempt to increase the reliability of the connection to the device by lowering the sync rate or reverting to narrow transfers. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message