From owner-freebsd-scsi Fri Mar 15 11:51: 9 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from aslan.scsiguy.com (aslan.scsiguy.com [63.229.232.106]) by hub.freebsd.org (Postfix) with ESMTP id A5D3D37B438 for ; Fri, 15 Mar 2002 11:50:56 -0800 (PST) Received: from scsiguy.com (localhost [127.0.0.1]) by aslan.scsiguy.com (8.11.6/8.11.5) with ESMTP id g2FJrKI80174; Fri, 15 Mar 2002 12:53:21 -0700 (MST) (envelope-from gibbs@scsiguy.com) Message-Id: <200203151953.g2FJrKI80174@aslan.scsiguy.com> To: Matthew Reimer Cc: scsi@FreeBSD.ORG Subject: Re: no active SCB for reconnecting target In-Reply-To: Your message of "Fri, 15 Mar 2002 11:41:48 CST." <3C92325C.30403@vpop.net> Date: Fri, 15 Mar 2002 12:53:20 -0700 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org >We are getting errors like the following a dozen or so times per day, >for several months now (maybe even a year): > >ahc0:A:13: no active SCB for reconnecting target - issuing BUS DEVICE RESET >Mar 15 00:49:26 ring /kernel: SAVED_SCSIID == 0xd7, SAVED_LUN == 0x0, >ARG_1 == 0x2a ACCUM = 0x17 >... I'm looking into any chip errata that might cause this, but the best bet is a bogus cable or terminator. According to your dmesg output, there is no ID 13 on the bus. Nonetheless, occassionally during a selection the aic7896 believes that bit 13 is set on the bus. Very wierd. -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message