From owner-freebsd-scsi Fri Mar 15 16:16:36 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 2A2DF37B417 for ; Fri, 15 Mar 2002 16:16:30 -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 g2G0GOF16128; Fri, 15 Mar 2002 16:16:25 -0800 (PST) (envelope-from mreimer@vpop.net) Message-ID: <3C928F0B.3060508@vpop.net> Date: Fri, 15 Mar 2002 18:17:15 -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. One more datapoint: I went through the logs for the last week and counted which bogus ids tried to reconnect: id # of bogus reconnects resulting in BDR -- --- 9 2 12 15 13 91 I.e. the "no active SCB for reconnecting target" was issued twice for ID 9, 15 times for id 12, and 91 times for id 13. There are no devices with these ids on any of the SCSI busses. I also found that every one of these errors was generated by ahc0:A, where da0 and da1 are. It's seem like bits 2 and 3 are getting randomly changed. Matt To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message