Return to BSD News archive
Received: by minnie.vk1xwt.ampr.org with NNTP id AA1910 ; Tue, 23 Feb 93 15:03:37 EST Newsgroups: comp.unix.bsd Path: sserve!manuel.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!saimiri.primate.wisc.edu!usenet.coe.montana.edu!nate From: nate@cs.montana.edu (Nate Williams) Subject: Re: bad crashes w/ 386bsd Message-ID: <1993Feb22.055340.10269@coe.montana.edu> Sender: usenet@coe.montana.edu (USENET News System) Organization: Dept. of Computer Science, MSU, Bozeman Mt 59717 References: <gfW4aSq00iV3A61al_@andrew.cmu.edu> Date: Mon, 22 Feb 1993 05:53:40 GMT Lines: 59 In article <gfW4aSq00iV3A61al_@andrew.cmu.edu> "Alex R.N. Wetmore" <aw2t+@andrew.cmu.edu> writes: >>I write >> >(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). cp -Rp does a pretty good job. Or you could use tar, or dump, or any other type of archiver. To get NFS support, just compile the kernel with the NFS option. Works great for me. I now mount all sorts of directories, and for grins once mounted up wuarchive's system disk. Slow, but it worked. > >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. > Hmm, if it were me, I couldn't afford, but I would try getting a new chip. 386 chips are pretty cheap now, since I know you can get a brand new 386SX 20 Mboard for around $150. >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? > I think Warren Toomey posted a similar program called vstat, which is probably on his archive, winnie.????.au (Can't remember the name right now) Nate -- opjnw@terra.oscs.montana.edu | Still trying to find a good reason for nate@cs.montana.edu | these 'computer' things. Personally, home #: (406) 586-0579 | I don't think they'll catch on - Don H.