From owner-freebsd-scsi Tue Jul 25 13:22:28 2000 Delivered-To: freebsd-scsi@freebsd.org Received: from pluto.plutotech.com (mail.plutotech.com [206.168.67.137]) by hub.freebsd.org (Postfix) with ESMTP id C6B0337B67F for ; Tue, 25 Jul 2000 13:22:04 -0700 (PDT) (envelope-from gibbs@plutotech.com) Received: from caspian.plutotech.com (root@mail.plutotech.com [206.168.67.137]) by pluto.plutotech.com (8.9.2/8.9.1) with ESMTP id OAA50400; Tue, 25 Jul 2000 14:21:11 -0600 (MDT) (envelope-from gibbs@plutotech.com) Message-Id: <200007252021.OAA50400@pluto.plutotech.com> X-Mailer: exmh version 2.1.1 10/15/1999 To: Mike Meyer Cc: "Justin T. Gibbs" , scsi@freebsd.org Subject: Re: (noperiph:ahc0:0:-1:-1) & forwarded message ... In-Reply-To: Your message of "Tue, 25 Jul 2000 14:59:59 CDT." <14717.61887.241374.229647@guru.mired.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Tue, 25 Jul 2000 14:21:57 -0600 From: "Justin T. Gibbs" Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org >> Also, your picture seemed to show that all devices live on the >> same (LVD?) segment. It that true? > >There are two segments. All the drives live on one, and yes, that one >is plugged into the LVD socket on the motherboard. The other end of >that cable is plugged into an active terminator. The slower devices >are on socket adapters to go from 68 to 50 pins. > >The second is on the 50 pin socket on the motherboard, and runs to an >expansion socket (50pin HD), and then to an external >scanner. So the bus is not "T-ed" at the motherboard's 50pin connector? Just wanted to make sure that having the single ended bus terminated, as the driver reported, is correct. >> When the system hangs, if you are at the console, can you drop >> into the debugger. You must have options DDB in your kernel >> to try this. > >Are you just curious about whether or not I can, or is there something >specific you'd like to know? If the former, the system is still >responding to interrupts - it echos characters and answers to >pings. Does that answer the question? A stack trace from the hung system would be useful. db> trace -- Justin To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message