From owner-freebsd-current Fri Aug 8 20:53:32 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.5/8.8.5) id UAA05034 for current-outgoing; Fri, 8 Aug 1997 20:53:32 -0700 (PDT) Received: from troutmask.apl.washington.edu (troutmask.apl.washington.edu [128.95.76.54]) by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id UAA04811; Fri, 8 Aug 1997 20:44:20 -0700 (PDT) Received: (from sgk@localhost) by troutmask.apl.washington.edu (8.8.6/8.8.5) id UAA18785; Fri, 8 Aug 1997 20:45:49 GMT From: Steve Kargl Message-Id: <199708082045.UAA18785@troutmask.apl.washington.edu> Subject: Re: scsi time-out & lockup under smp In-Reply-To: from Tom at "Aug 8, 97 05:17:36 pm" To: tom@uniserve.com (Tom) Date: Fri, 8 Aug 1997 20:45:48 +0000 (GMT) Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG X-Mailer: ELM [version 2.4ME+ PL32 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-freebsd-current@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Tom: > > On Fri, 8 Aug 1997, Steve Kargl wrote: > > ... > > sd1(ahc0:1:0): UNIT ATTENTION asc:29,0 > > sd1(ahc0:1:0): Power on, reset, or bus device reset occurred, retries:4 > > ... > > ahc0: waiting for scsi devices to settle > > scbus0 at ahc0 bus 0 > > sd0 at scbus0 target 0 lun 0 > > sd0: type 0 fixed SCSI 2 > > sd0: Direct-Access 1030MB (2109840 512 byte sectors) > > st0 at scbus0 target 2 lun 0 > > st0: type 1 removable SCSI 2 > > st0: Sequential-Access density code 0x13, drive empty > > What is sd1? Whoops, cut and paste problem. sd1 is a Quantum Lightning 730E. st0 and sd1 are external drives with active termination on sd1. Termination is known to be correct (first thing I checked). > Also, are you sure you aren't having cable problems? The fact that all > the devices go wacko at the same time is strange. Same cables I've been using for 2 years. They could go bad (I guess). No. st0 goes south, then the SCSI bus locks up during the reset, and sd0 and sd1 sieze up. Never sd0 nor sd1 suffer any damage. > Also, check your power supply. Heavy disk io will draw more power, is > your PS cutting out causing the timeouts? sd0 is on the internal main PS. sd0 and st0 each have their own PS. -- Steve finger kargl@troutmask.apl.washington.edu http://troutmask.apl.washington.edu/~kargl/sgk.html