Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!munnari.OZ.AU!spool.mu.edu!usenet.eel.ufl.edu!arclight.uoregon.edu!feed1.news.erols.com!howland.erols.net!newsfeed.internetmci.com!netnews.nwnet.net!news.u.washington.edu!news.alt.net!news1.alt.net!news.aa.net!ratty.wolfe.net!usenet From: mgmead@smmedia.com (Malcolm Mead) Newsgroups: comp.unix.bsd.bsdi.misc Subject: Re: SCSI Bug on BSDI 2.0.1 ?? Date: Fri, 11 Oct 1996 16:57:25 GMT Organization: Wolfe Internet Access, L.L.C. Lines: 56 Message-ID: <53lucc$tnr@ratty.wolfe.net> References: <PAULE.95Dec9143256@mx42.cht.de> <4af4fi$h81@hops.entertain.com> NNTP-Posting-Host: origin.original.com Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-Newsreader: Forte Agent .99f/32.299 dwatson@abwam.com (Darryl Watson) wrote: >In article <PAULE.95Dec9143256@mx42.cht.de>, paule@mx42.cht.de (Gerd M. Pauli) says: >> >>Hello, >> >>I have some strage problems with the SCSI driver. >> >>Machine: 486/BSDI 2.0.1 >>aha0: parity, bus transfer 5 Mb/s, bus on/off 11/4 us >>tg0 at aha0 target 0 >>sd0 at tg0 unit 0: IBM OEM 0662S12 rev 2 23 (SCSI-2) >>sd1 at tg1 unit 0: SEAGATE ST41650 rev 6414 (SCSI-2) >>sd2 at tg2 unit 0: HP 97558 rev 0A0F (SCSI-2) >> >>Sometimes ( about every 24 hours ) the machine reports: >>"aha0: operation time exceeds xxxxx seconds" >> >>The Message repeates every 60 seconds and the machine is dead. :-( >> >> >>The source said ( aha.c ): >> >> /* >> * Scan sccb list, look for stale entries. >> * If a read or write entry hasn't been serviced in a reasonable >> * amount of time, complain (should abort the transaction?). >> */ ^^^^^^^^^^^^ >> YES this would be better than hangin around and doing nothing !! >> >>Is there a fix for this problem. >> >It sounds like your SCSI devices are just on the edge of functionality... >meaning that maybe you've got one-too-many terminators in your SCSI chain, >or something like that. Maybe the SCSI cable is too long? (What is >it, 14ft for SCSI-2?) Hmm, probably not that. >We have a 486 box running 2.0.1 with lots of SCSI-2 devices, and never >have a blip. What we did was to take out system drive, put the terminator >on the external cabinet, and all other devices in-between have no >terminators. In other words, our 0 device is our system drive, and we >made it the last device in the chain. I have to concur with the idea that there is a problem with termination or the chain setup. I was having JUST the same trouble during install on a Pentium running SCSI. It was giving the "xxxx seconds" messages over and over ad infinitum. I called the techs and they said that it was probably a termination problem. I went back over the setup and found that a "self terminating" CD of mine was NOT. Once i fixed that, all problems were solved. Malcolm