Return to BSD News archive
Path: sserve!manuel.anu.edu.au!sorokin!jason From: jason@sorokin.anu.edu.au (Jason Andrade) Newsgroups: comp.unix.bsd Subject: Re: Occasional system hangs Date: 11 Dec 92 11:03:00 GMT Organization: Australian National University Lines: 31 Message-ID: <jason.724071780@sorokin> References: <1992Dec2.140837.12619@cli.di.unipi.it> <jason.723781864@sorokin> <ByysLH.Axr@ns1.nodak.edu> <1g95ueINNhri@manuel.anu.edu.au> <andrewh.724059111@bruce.cs.monash.edu.au> NNTP-Posting-Host: 150.203.76.12 andrewh@cs.monash.edu.au (Andrew Herbert) writes: >titus@coombs.anu.edu.au (titus chiu) writes: >[386bsd hang description deleted] [more text deleted] >news usually keep ticking away for quite some time (i.e. disk is unaffected), occasinally i do notice the disk goes crazy (ie the drive light never goes out ...) no its not thrashing. just sitting there dead...) >but it looks a whole lot like anything requiring a fork(), such as programs >are run from the shell just hangs. Eventually all processes grind to a halt, >but the system can still be pinged. The VM problem sounds quite a likely not in my case. once the system hangs. its totally hung. I cant ping it etc.. >cause, alas. gcc 2.3.1 is particularly good at bringing about this problem, >while X8514 and friends rarely lasts more than 12 hours without hanging 386bsd >and requiring a reboot. Well, im going to have fun when [more likely IF] i get X happening. Not. Oh, system uptime record so far is way behind your 12 hours and its a nominally 'quiet' machine.... >Time for more RAM I guess! Would be nice, but I'd prefer a patch to the kernel myself. :-) >Andrew -jason