*BSD News Article 16943


Return to BSD News archive

Newsgroups: comp.os.386bsd.bugs
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!doc.ic.ac.uk!uknet!zaphod.axion.bt.co.uk!sol!root
From: msmith@rheya.lssec.bt.co.uk (Martin Smith)
Subject: Re: 1542C not taking commands!
Message-ID: <1993Jun9.125931.537@lssec.bt.co.uk>
Keywords: SCSI BSD 1542
Sender: msmith@rheya (Martin Smith)
Organization: BT D&P, London Engineering Centre
References: <C8AFKF.5EH@NeoSoft.com> <1993Jun8.120703.12538@cnplss5.cnps.philips.nl>
Date: 09 Jun 93 13:59:32 GMT
Lines: 53

In article <1993Jun8.120703.12538@cnplss5.cnps.philips.nl>, rooij@mozart.cft.philips.nl (Guido van Rooij) writes:
|> egan@blkbox.COM (Doug Egan) writes:
|> 
|> 
|> >	I am currently experiencing a SCSI controller problem with my
|> >	NetBSD installation. I have installed the binary distribution,
|> >	nothing more (at this point)... and I intermitantly get the
|> >	following error messages: 
|> 
|> >             aha0: device 0 timed out
|> >             aha0: device 0 timed out aha0 not taking commands!
|> >	     panic: should call debugger here (adaptec.c)  
|> >	     updating disks before rebooting...
|> 
|> >	NOTE: - The system hangs.
|> >	      - During installation the following warning message is 
|> >	        displayed: 
|> > 
|> >	        73 sectors in last cylinder unallocated  
|> 
|> >  1. Should I call Adaptec?
|> >  2. Has anyone else encountered this problem? 
|> >     What is fix?
|> >  3. Will I need to go into debugger?
|> >     (Will be hard, due to the occurances of this problem) 
|> 
|> As far as I know, this seems to be a terminator problem. You might
|> want to ask hasty@netcom.com who reported a similar problem as far 
|> as I remember.
|> 
|> >Thanks N Advance (TNA)
|> >Doug 
|> >--
|> >                       Doug Egan    CompuVision Research                      
|> >                       Internet:    egan@blkbox.com                           
|> >                       Friendswood, Texas                                     
|> >______________________________________________________________________________
|> 
|> -Guido

It wasn't termination when it happened to me. It was the setting of 'Enable
Disconnection' under the 'SCSI Device Configuration' menu.

It should be set to YES for all devices, as the manual warns you. If only
I read manuals.

Martin

-------------------------------------------------------------------------------
Martin Smith          | You've got a magic carpet for three people to fly to 
msmith@lssec.bt.co.uk | the King of the Potato People to plead your case and
BT D&P Nodnol         | you're trying to tell me you're sane? - A.J. Rimmer
-------------------------------------------------------------------------------