From owner-freebsd-scsi Wed Oct 6 11:36:38 1999 Delivered-To: freebsd-scsi@freebsd.org Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (Postfix) with ESMTP id 726811572D for ; Wed, 6 Oct 1999 11:36:09 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.9.3/8.7.3) id MAA25143; Wed, 6 Oct 1999 12:23:35 -0600 (MDT) Date: Wed, 6 Oct 1999 12:23:35 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199910061823.MAA25143@narnia.plutotech.com> To: Vadim Belman Cc: scsi@FreeBSD.org Subject: Re: 'Unexpected busfree' X-Newsgroups: pluto.freebsd.scsi In-Reply-To: <85k8p2vvmt.fsf@eagle.plab.ku.dk> User-Agent: tin/pre-1.4-980818 ("Laura") (UNIX) (FreeBSD/4.0-CURRENT (i386)) 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. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message