Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1867 ; Tue, 23 Feb 93 15:01:45 EST Organization: Sophomore, Math/Computer Science, Carnegie Mellon, Pittsburgh, PA Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!agate!usenet.ins.cwru.edu!magnus.acs.ohio-state.edu!cis.ohio-state.edu!news.sei.cmu.edu!bb3.andrew.cmu.edu!crabapple.srv.cs.cmu.edu!andrew.cmu.edu!aw2t+ Newsgroups: comp.unix.bsd Message-ID: <gfW4aSq00iV3A61al_@andrew.cmu.edu> Date: Sun, 21 Feb 1993 22:33:50 -0500 From: "Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu> Subject: Re: bad crashes w/ 386bsd In-Reply-To: <1993Feb22.012232.24154@coe.montana.edu> Lines: 60 Excerpts from netnews.comp.unix.bsd: 22-Feb-93 Re: bad crashes w/ 386bsd by Nathan Williams@gemini.o > In article <8fVlfba00WBME6YGZo@andrew.cmu.edu> aw2t+@andrew.cmu.edu (Alex R.N. > Wetmore) writes: > >2) Everything just dies. I can usuaully switch virtual consoles and > >give it the 3 finger salute, but not much more. > > I would suspect that #2 is directly related to > > 5 meg swap > > > Try increasing your swap space. 5 Meg isn't much, and 386BSD doesn't > do well when it starts to swap alot (though it doesn't make multiple > copies of the same file and the same name like another PD O.S. :-) > > > It's possible that some of the VM fixes are triggering some bad > hardware in your machine... Any way to do this without reinstalling? Otherwise, has anyone made a boot disk that will get my machine into nfs? Also, what is the best way to do a copy over nfs to make sure that all permissions get saved (since cp isn't very good at that). Also, I know that I have a revision B 386 chip (I am running on a circa 87 386dx/16). Linux 0.95 (last time I ran it) used to give me some sort of page fault errors, but I compiled the errors out of the kernel life would be happy. Could this be related in someway (I assume that the MMU on my chip has a bug in it). Would getting a new 386 fix this (I would probably just upgrade to a 486sx motherboard). Like I said, things used to work great. > That sounds like my machine BEFORE the patchkit. Now, after the 0.2.1 > patchkit, my machine has been up for a week at one time (needed to > reboot to try out some kernel patches). > > I have only seen one crash since installing the patchkit, and I was > at home when it happened so the message was lost when it rebooted. > > >Looking through the > >386bsd.BUGS list it seems they mention some scheduling problems that > >sound like they could be causing the crashes too. I haven't seen any > >patches for that code outside of the patchkit though. Anything I can do > >about this? > > 0.2 is supposedly the fix for this, when it is released. Any word on when 0.2 is supposed to be released? If it is soon enough I might just upgrade swap when it comes out (since I assume it will require a pretty large reinstall of everything). The shared libs in 0.2 (which I hope will exist) should help life considerably, since I only have a 97 meg BSD partition, which doesn't leave much space for adding swap (I float between 5 and 10 megs free, don't like to go below that). Also, is there a vmstat program out there, so that I could actually see how close I am to running into the top of swap space? thanks, alex