From owner-freebsd-scsi Wed Oct 6 14:44:54 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from feral.com (feral.com [192.67.166.1]) by hub.freebsd.org (Postfix) with ESMTP id 6E20E14EF9 for ; Wed, 6 Oct 1999 14:44:48 -0700 (PDT) (envelope-from mjacob@feral.com) Received: from feral.com (mjacob@feral.com [192.67.166.1]) by feral.com (8.8.7/8.8.7) with ESMTP id OAA01895; Wed, 6 Oct 1999 14:44:33 -0700 Date: Wed, 6 Oct 1999 14:44:33 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Gerard Roudier , "Justin T. Gibbs" , Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-Reply-To: <199910062143.PAA11327@caspian.plutotech.com> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII 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 parity > >> 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. Or, for some devices (e.g., ESP100 chips), even going to different onchip signal filtration.... -matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message