Return to BSD News archive
Newsgroups: comp.unix.bsd.netbsd.misc Path: euryale.cc.adfa.oz.au!newshost.anu.edu.au!harbinger.cc.monash.edu.au!news.uwa.edu.au!disco.iinet.net.au!news.uoregon.edu!arclight.uoregon.edu!news.dacom.co.kr!usenet.seri.re.kr!news.cais.net!bofh.dot!news.mathworks.com!newsfeed.internetmci.com!newsserver.jvnc.net!newsserver2.jvnc.net!news.cac.psu.edu!news.cse.psu.edu!news.cc.swarthmore.edu!netnews.upenn.edu!news.voicenet.com!news2.noc.netcom.net!noc.netcom.net!ixnews1.ix.netcom.com!netcom.com!ikhala From: ikhala@netcom.com (I'Khala) Subject: Re: Help me, Mister Wizard! Message-ID: <ikhalaDrGH4K.55I@netcom.com> Organization: DisOrganiZed Geeks References: <Pine.NEB.3.93.960515044938.164A-100000@natrix.wcrb.com> Date: Wed, 15 May 1996 16:43:31 GMT Lines: 46 Sender: ikhala@netcom5.netcom.com In article <Pine.NEB.3.93.960515044938.164A-100000@natrix.wcrb.com>, Rob Landry <umar@wcrb.com> wrote: >I'm running NetBSD 1.1/i386 on a Compudyne 386-33 with 4 MB RAM and a 1.2 >GB hard drive. Every few days the system freezes up. > >When that happens, it won't respond to anything typed on the keyboard. >The machine can be pinged, however, and I can telnet to it and get >"Connected to zzzzz.wcrb.com", but no login prompt. The machine runs >sendmail, named and httpd, none of which respond while it is in its >"comatose" state. The only way I've been able to bring it back to life >is to power it down and cold-boot it. > >When it first happened, I thought the problem might have been caused by a >power surge, so I put the machine on a UPS. > >When the machine next froze up, I decided it must be a hardware problem. >So I took out the hard drive and network adapter and installed them in a >completely different computer. > >And the problem happened again. If it's not a hardware problem, and it's >not Boston Edison's fault, then there must be something wrong with NetBSD >or the way I've installed it. > >NetBSD 1.1 is the only OS installed on this machine, which is used as a >DNS server, mail server and HTTP server for our local area network. > >Does anyone have any ideas on how I might track this problem down? > > >Rob Landry >WCRB 102.5 FM Classical Radio Boston >umar@wcrb.com (work) >umar@cybercom.net (home) > > i'm certainly no wizard, but 4mb of ram seems a bit tight for what you're doing. try installing another 4mb at least and see what happens ... :) i'chi -- ikhala@netcom.com - Nubian Scientific Research Support the free! - NetBSD/FreeBSD/Linux/Minix Freely distributable O/S's and software ... Software for users with discriminating taste ...