From owner-freebsd-current Wed Aug 12 21:05:29 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id VAA05274 for freebsd-current-outgoing; Wed, 12 Aug 1998 21:05:29 -0700 (PDT) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from narnia.plutotech.com (narnia.plutotech.com [206.168.67.130]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id VAA05261 for ; Wed, 12 Aug 1998 21:05:15 -0700 (PDT) (envelope-from gibbs@narnia.plutotech.com) Received: (from gibbs@localhost) by narnia.plutotech.com (8.8.8/8.7.3) id VAA01243; Wed, 12 Aug 1998 21:59:02 -0600 (MDT) Date: Wed, 12 Aug 1998 21:59:02 -0600 (MDT) From: "Justin T. Gibbs" Message-Id: <199808130359.VAA01243@narnia.plutotech.com> To: "randyd@ameritech.net" cc: current@FreeBSD.ORG Subject: Re: Unexpected busfree??? Newsgroups: pluto.freebsd.current In-Reply-To: <01BDC604.1D2932D0.randyd@ameritech.net> User-Agent: tin/pre-1.4-971204 (UNIX) (FreeBSD/3.0-CURRENT (i386)) Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In article <01BDC604.1D2932D0.randyd@ameritech.net> you wrote: > Greetings, > > This message just popped up on one of my 3.0-SNAP machines.... > > Unexpected busfree. LASTPHASE == 0x0 > SEQADDR = 0x121 It means that a target released the BSY signal on the bus unexpectedly. Bus free should only occur after a disconnect or command complete message, or in responds to an abort, abort tag, bus device reset, or BUS RESET request from the initior. If you system stayed up, the driver recovered properly from the target's protocol botch. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message