*BSD News Article 2125


Return to BSD News archive

Newsgroups: comp.unix.bsd
Path: sserve!manuel!munnari.oz.au!news.hawaii.edu!kum.kaist.ac.kr!ames!elroy.jpl.nasa.gov!usc!noiro.acs.uci.edu!ucivax!ucla-cs!ucla-mic!scott
From: scott@pita.cns.ucla.edu (Scott Burris)
Subject: 386BSD 0.1: oddities, more oddities
Message-ID: <1992Jul20.144121.13670@mic.ucla.edu>
Nntp-Posting-Host: pita.cns.ucla.edu
Reply-To: scott@pita.cns.ucla.edu (Scott Burris)
Organization: UCLA Campus Network Services
Date: 20 Jul 92 14:41:20 PDT
Lines: 27


Why is it that I see strange things which no one else has seen?  I
upgraded from 0.0 to 0.1 and repartitioned my disk so MSDOS would work.
This is on a 486/33 with OPTI chipset, an IDE and a SCSI drive.

The install program kept insisting I had over 7000MB of space free (I wish!)
when it asked how much for 386BSD.  Anyone else seen this?  Anyway, I gave 
reasonable answers and was able to get a system running anyway, but I'm
puzzled why this figure is so wrong.

I also got intermittent panics of "kmem_map" too small.  Generally this
happens when the system is first powered up.  I believe it is related to
code in the SCSI driver which queries the size of the disk and sometimes
gets a totally bogus answer.  I put in a sanity check in the SCSI driver
to retry getting the size, and the problem has gone away.  But... this
shouldn't be necessary.

Also, the SCSI driver is now broken for variable block size tape drives.
I wrote a fix for that and I'll post it tomorrow.



--
----------
Scott Burris
UCLA Campus Network Services
cnetslb@oac.ucla.edu (213) 206-4860 - OR - scott@pita.cns.ucla.edu