From owner-freebsd-scsi Wed Oct 6 13:13:44 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 6B77B1576C for ; Wed, 6 Oct 1999 13:12:53 -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 NAA01559; Wed, 6 Oct 1999 13:11:46 -0700 Date: Wed, 6 Oct 1999 13:11:46 -0700 (PWT) From: Matthew Jacob Reply-To: mjacob@feral.com To: "Justin T. Gibbs" Cc: Vadim Belman , scsi@FreeBSD.ORG Subject: Re: 'Unexpected busfree' In-Reply-To: <199910061823.MAA25143@narnia.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 > In article <85k8p2vvmt.fsf@eagle.plab.ku.dk> you wrote: > > I wonder if someone can tell me: what kind of error is the > > following? > > > > Unexpected busfree. LASTPHASE == 0x0 > > SEQADDR == 0x5e > > > > And what do I do with it? > > This means that the bus appeared to go free during the middle of a > transaction. In this case, it happened during a DATAOUT phase. > Essentially the target hung up without saying good bye first. > > These kinds of problems can be caused by bad cabling setups. Perhaps > the REQ/ACK offset counters got out of sync (initiator did not see a > REQ pulse) so the target timedout and ended the connection. It's hard > to say without an analyzer. Be sure to use forced perfect terminators, > high quality cables, and don't exceed 3m in cable length. 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. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message