From owner-freebsd-hackers Sat Oct 11 02:14:25 1997 Return-Path: Received: (from root@localhost) by hub.freebsd.org (8.8.7/8.8.7) id CAA09881 for hackers-outgoing; Sat, 11 Oct 1997 02:14:25 -0700 (PDT) (envelope-from owner-freebsd-hackers) Received: from word.smith.net.au (ppp20.portal.net.au [202.12.71.120]) by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id CAA09874 for ; Sat, 11 Oct 1997 02:14:19 -0700 (PDT) (envelope-from mike@word.smith.net.au) Received: from word.smith.net.au (localhost [127.0.0.1]) by word.smith.net.au (8.8.7/8.8.5) with ESMTP id SAA00991; Sat, 11 Oct 1997 18:41:21 +0930 (CST) Message-Id: <199710110911.SAA00991@word.smith.net.au> X-Mailer: exmh version 2.0zeta 7/24/97 To: "Brian N. Handy" cc: freebsd-hackers@freebsd.org Subject: Re: Run out of swap In-reply-to: Your message of "Fri, 10 Oct 1997 15:41:51 MST." Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Date: Sat, 11 Oct 1997 18:41:19 +0930 From: Mike Smith Sender: owner-freebsd-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk > > I'm having problems with my machine hanging when I run it up against the > stops in terms of memory usage. Is it actually hitting the wall swapwise when it dies, or is it a case of "sometimes I run out of swap, sometimes it dies"? > Now every so often I start up a too-ambitious job, run out of memory and > it crashes. I get the predictable "job kilt" line which tells me I ran > out of memory and I was dutifully kicked out. HOWEVER, now what I'm > seeing every so often is that it doesn't kick me out, but instead the > machine just hangs. The clock in the corne of my screen stops, the mouse > stops, the num lock light doesn't go off and off. Fixed and dialated. > Once this happens, it seems like I have to hit the reset button. You say "now what I'm seeing" - did you have similar problems when you were running with 64M? > It could be these last two are too big for the smallish about of swap I > have available. Anyway, are there any suggestions out there? I'm not > sure how to figure out where I'm hanging, but I seem to be able to repeat > the problem fairly consistently. I'd rather the job crashed instead of > just running into a wall. Wind up a killer job, and then swap to the text console. Keep an eye out for any console messages. Particularly, do you have DDB in the kernel? mike