Date: Fri, 8 Aug 1997 20:45:48 +0000 (GMT) From: Steve Kargl <sgk@troutmask.apl.washington.edu> To: tom@uniserve.com (Tom) Cc: jwd@unx.sas.com, freebsd-current@FreeBSD.ORG, freebsd-smp@FreeBSD.ORG Subject: Re: scsi time-out & lockup under smp Message-ID: <199708082045.UAA18785@troutmask.apl.washington.edu> In-Reply-To: <Pine.BSF.3.96.970808171538.28159B-100000@shell.uniserve.com> from Tom at "Aug 8, 97 05:17:36 pm"
next in thread | previous in thread | raw e-mail | index | archive | help
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: <SEAGATE ST51080N 0943> type 0 fixed SCSI 2 > > sd0: Direct-Access 1030MB (2109840 512 byte sectors) > > st0 at scbus0 target 2 lun 0 > > st0: <HP HP35480A 1109> 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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199708082045.UAA18785>