Return to BSD News archive
Path: sserve!newshost.anu.edu.au!munnari.oz.au!news.Hawaii.Edu!ames!sgiblab!swrinde!cs.utexas.edu!uunet!news2.uunet.ca!fw.novatel.ca!sidney!hpeyerl
From: hpeyerl@sidney (Herb Peyerl)
Newsgroups: comp.os.386bsd.questions
Subject: Re: Mysterious 'autonomous' reboots under NetBSD ???
Date: 7 Feb 1994 00:53:57 GMT
Organization: NovAtel Communications Ltd.
Lines: 19
Message-ID: <2j43f5$r4v@fw.novatel.ca>
References: <2hc3rd$qmb@wzv.win.tue.nl> <hastyCJqqoC.750@netcom.com> <1994Jan16.215309.7660@sifon.cc.mcgill.ca> <2hrjii$m89@homea.ensta.fr> <2ibbnt$lvh@sylvester.cc.utexas.edu>
NNTP-Posting-Host: sidney.novatel.ca
X-Newsreader: TIN [version 1.2 PL1]
Vax (vax@sylvester.cc.utexas.edu) wrote:
: However, now I am experiencing a new one. If I end a large program, such
: as X, or I have just caused a large program to page fault many times, such
: as when I have just finished telnet'ing to a local mud, and I type
: "who" or "w" at the command line, (more often "w"), the command will print
: the uptime line just fine, but when it is about to print the first user's
: name, it causes a vm_fault and reboots - the specific numbers printed flash by
: too fast to read.
If you put "options DDB" in your config file; then when it panics you'll
be able to see the errors and even do a trace.
I'm just guessing but you're probably running 0.9 and you're probably
seeing a panic in _fill_eproc(). This no longer occurs in -current.
--
hpeyerl@novatel.ca | NovAtel Commnications Ltd.
hpeyerl@fsa.ca | <nothing I say matters anyway>
<NetBSD: A drinking group with a serious computing problem!>