From owner-freebsd-scsi Fri Mar 15 12: 3: 2 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from boromir.vpop.net (dns1.vpop.net [206.117.147.2]) by hub.freebsd.org (Postfix) with ESMTP id 9212537B417 for ; Fri, 15 Mar 2002 12:02:58 -0800 (PST) Received: from vpop.net (bilbo.vpop.net [65.103.33.41]) by boromir.vpop.net (8.11.6/8.11.6) with ESMTP id g2FK2oF99001; Fri, 15 Mar 2002 12:02:50 -0800 (PST) (envelope-from mreimer@vpop.net) Message-ID: <3C9253A4.1060302@vpop.net> Date: Fri, 15 Mar 2002 14:03:48 -0600 From: Matthew Reimer Organization: VPOP Technologies, Inc. User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:0.9.9) Gecko/20020312 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Justin T. Gibbs" Cc: scsi@FreeBSD.ORG Subject: Re: no active SCB for reconnecting target References: <200203151953.g2FJrKI80174@aslan.scsiguy.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit 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 Justin T. Gibbs wrote: >>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. The cable the disks are on is a preterminated LVD from Adaptec. We replaced it at least once (possibly twice; I can't remember) with another preterminated Adaptec LVD cable trying to cure this problem, but to no avail. Forgot to mention that we see this error a dozen or so times per day. FWIW, on another machine we occasionally see the same problem on another machine with the same motherboard, but not in the last week (don't have logs further back than a week). Thanks for your help Justin. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message