Return to BSD News archive
Path: sserve!manuel!munnari.oz.au!uunet!spool.mu.edu!agate!soda.berkeley.edu!wjolitz From: wjolitz@soda.berkeley.edu (William F. Jolitz) Newsgroups: comp.unix.bsd Subject: Re: 386BSD & AHA1542B & CDC94171-9 Disk problem Message-ID: <14ca62INNhfr@agate.berkeley.edu> Date: 19 Jul 92 17:53:06 GMT Article-I.D.: agate.14ca62INNhfr References: <1992Jul19.121003.27453@ulrik.uio.no> Organization: U.C. Berkeley, CS Undergraduate Association Lines: 19 NNTP-Posting-Host: soda.berkeley.edu In article <1992Jul19.121003.27453@ulrik.uio.no> tha@ulrik.uio.no writes: > ... > changing root device to fd0a > as0b: controller error 0x16 reading fsbn 0 > scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 > as0b: controller error 0x16 reading fsbn 0 > scsi sense: 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 This looks like the problem Rob Warnock had with the Adaptec. Try running the diagnostic program's that just exercise DMA without a disk. If it randomly fails, that's it. Rob found that when he "dumbed down" the config by adding wait states to memory, then the SCSI controller would randomly fail. According to my Adaptec manual,this is an invalid CCB operation Code, which indicates that the DMA of the CCB failed. So it's got to be a config problem of some kind... Bill