Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.carno.net.au!harbinger.cc.monash.edu.au!news.mira.net.au!news.netspace.net.au!news.mel.connect.com.au!munnari.OZ.AU!uunet!in3.uu.net!128.83.139.5!cs.utexas.edu!atlantis.utmb.edu!news From: "Ernest C. Hymel" <ehymel@utmb.edu> Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: NCR SCSI Fatal errors! Date: 22 May 1997 16:08:24 GMT Organization: University of Texas Medical Branch Lines: 22 Message-ID: <01bc66c9$fc095160$27366d81@masscomp> References: <Pine.BSF.3.95q.970521173345.372A-100000@ipamzlx.physik.uni-mainz.de> NNTP-Posting-Host: masscomp.utmb.edu X-Newsreader: Microsoft Internet News 4.70.1161 Xref: euryale.cc.adfa.oz.au comp.unix.bsd.freebsd.misc:41431 O. Hartmann <ohartman@ipamzlx.physik.uni-mainz.de> wrote in article <Pine.BSF.3.95q.970521173345.372A-100000@ipamzlx.physik.uni-mainz.de>... > Dear Sirs. > > Using FreeBSD 2.2.2 produces a lot of errors when booting. > I switched these days from FreeBSD 2.1.7.1 to FreeBSD 2.2.2 > and my NCR 53C810 SCSI controler did its work well until the > switch. Sometimes when I must reboot the system this error > occurs like ncr0(0:0:0) FATAL ERROR and so on. I think its a > kernel problem and it should be possible to change some parameter > to solve this problem. > Hmmm... same controller here with no problems before or after switch. Nearly identical kernel for both 2.1.7.1 and 2.2-STABLE, certainly identical where the controller is concerned. Are you sure you didn't change something else? Ernie Hymel <<stuff I can't help with deleted>> > O. Hartmann