From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 09:22:45 2003 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 390A337B401 for ; Mon, 21 Apr 2003 09:22:45 -0700 (PDT) Received: from ack.Berkeley.EDU (ack.Berkeley.EDU [128.32.206.66]) by mx1.FreeBSD.org (Postfix) with ESMTP id D1DE643F85 for ; Mon, 21 Apr 2003 09:22:44 -0700 (PDT) (envelope-from mhunter@ack.Berkeley.EDU) Received: (from mhunter@localhost) by ack.Berkeley.EDU (8.11.3/8.11.3) id h3LGMgk25095; Mon, 21 Apr 2003 09:22:42 -0700 (PDT) Date: Mon, 21 Apr 2003 09:22:42 -0700 From: Mike Hunter To: Craig Reyenga Message-ID: <20030421162242.GB23473@ack.Berkeley.EDU> References: <000501c307ad$86897d80$0200000a@fireball> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <000501c307ad$86897d80$0200000a@fireball> User-Agent: Mutt/1.4i cc: freebsd-current@freebsd.org Subject: Re: Hang after running out of memory X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 21 Apr 2003 16:22:45 -0000 On Apr 20, "Craig Reyenga" wrote: > I have been following the thread here on current@ about problems occuring > when running out of memory, so I wrote a C++ program that simply mallocs > about 144M of memory. My system has 256MB+491MB(swap). I can run the system > out of memory just fine by running multiple copies of the program, and the > kernel does kill one if I run too many, however shortly after, when I go to > killall the programs the system hangs, (although pings, etc manage to > survive for a few mintues longer) and I have no choice but to press the > reset button. While it is hung, I _can_ press ^T and it shows the load, > which increases by 1 about every 45 seconds: > > load: 11.58 cmd: killall 20125 [running] 0.00u 0.00s 11% 292k > load: 12.27 cmd: killall 20125 [running] 0.00u 0.00s 12% 292k > > Also, the console is just as unusable as any other terminal. I'm not sure > what is going on, but this is reproducible, and I can post more info upon > request. I've experienced similar things after running out of memory. It seemed like the scheduler went crazy: The only way I could get my ssh session to keep talking was to start other ssh sessions, which would buy me about 20 keystrokes. shutdown -r got half done and failed into a weird state. I think the kernel was from around April 8.