Return to BSD News archive
Xref: sserve comp.os.386bsd.bugs:1917 comp.unix.internals:6596 comp.unix.bsd:13096 Newsgroups: comp.os.386bsd.bugs,comp.unix.internals,comp.unix.bsd Path: sserve!newshost.anu.edu.au!munnari.oz.au!bunyip.cc.uq.oz.au!harbinger.cc.monash.edu.au!yeshua.marcam.com!news.kei.com!sol.ctr.columbia.edu!howland.reston.ans.net!europa.eng.gtefsd.com!uunet!spcuna!spcvxb!terry From: terry@spcvxb.spc.edu (Terry Kennedy, Operations Mgr.) Subject: Re: Swap overallocation in i386 BSD's Nntp-Posting-Host: spcvxa.spc.edu References: <CI27Jo.DGy@candle.uucp> Sender: news@spcuna.spc.edu (Network News) Organization: St. Peter's College, US Date: Thu, 16 Dec 1993 10:52:48 GMT Message-ID: <1993Dec16.055248.1@spcvxb.spc.edu> Lines: 20 In article <CI27Jo.DGy@candle.uucp>, root@candle.uucp (Bruce Momjian) writes: > I am running BSD/386 from BSDI. When running with 5MB of RAM, I found > that the system locked up about once every week. In researching the > problem with Mike Karels of BSDI, I think we have found a bug that > exists on BSD/386 and most free 386-based *BSD systems. Here are the > details. There is another small-memory bug in the Net-2 derived sources which is fixed by BSDI's patch #13 for BSD/386 1.0. On the machines I had here with small memory configurations (8Mb) I would get all sorts of corrupted pro- cesses. Mike didn't think it was related, but sent me a beta copy of patch #13 anyway. It turned out that was the cause of the problems I was seeing. If you don't have this patch installed, you may want to try it. I'm not saying that it will fix the problem you're seeing, but it does fix some other problems on systems where memory is scarce. Terry Kennedy Operations Manager, Academic Computing terry@spcvxa.bitnet St. Peter's College, Jersey City, NJ USA terry@spcvxa.spc.edu +1 201 915 9381