Return to BSD News archive
Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.cs.su.oz.au!metro!munnari.OZ.AU!spool.mu.edu!howland.reston.ans.net!vixen.cso.uiuc.edu!uwm.edu!fnnews.fnal.gov!gw1.att.com!news.bu.edu!usenet From: mi@aldan.bu.edu (&khail Teterin) Newsgroups: comp.unix.bsd.freebsd.misc Subject: Re: [BUG] Memory crunch causes reboot? Date: 17 Dec 1995 15:42:58 GMT Organization: Boston University Lines: 19 Message-ID: <4b1dq2$dqn@news.bu.edu> References: <4b0u5b$7rp@mark.ucdavis.edu> NNTP-Posting-Host: ppp-73-11.bu.edu X-Newsreader: knews 0.9.3 In article <4b0u5b$7rp@mark.ucdavis.edu>, ccjason@quadrophenia.ucdavis.edu (Jason Gabler) writes: >memory. I compiled and ran this NOT as root, nor was it setuid to root. >Going..,going..going...crunch..crunch..gri-ii-ii-i-i-nding... blink. Reboot. > >This *shouldn't* happen, right? > I noticed the same and similar things. Once I did have a reboot under heavy loaded system. And not once I've seen Xsession killed (I think, because of lack of memory -- process gets killed instead of getting NULL on the malloc() request). May be that is what is causing reboots -- some vital system process requests memory, and BOOM!? -mi -- "Windows for dummies"