From owner-freebsd-current@FreeBSD.ORG Mon Apr 21 10:54:44 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 A89B437B40C for ; Mon, 21 Apr 2003 10:54:44 -0700 (PDT) Received: from wabakimi.chat.carleton.ca (wabakimi.chat.carleton.ca [134.117.1.98]) by mx1.FreeBSD.org (Postfix) with ESMTP id 8BF0443FE1 for ; Mon, 21 Apr 2003 10:54:43 -0700 (PDT) (envelope-from creyenga@connectmail.carleton.ca) Received: from fireball (terry.cavern.carleton.ca [134.117.93.187] (may be forged))h3LHsfC7020514; Mon, 21 Apr 2003 13:54:41 -0400 (EDT) Message-ID: <000d01c3082f$0ef83ae0$0200000a@fireball> From: "Craig Reyenga" To: "Mike Hunter" References: <000501c307ad$86897d80$0200000a@fireball> <20030421162242.GB23473@ack.Berkeley.EDU> Date: Mon, 21 Apr 2003 13:54:19 -0400 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 6.00.2600.0000 X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2600.0000 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 17:54:45 -0000 From: "Mike Hunter" > 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. > Was it SCHED_ULE? That's the one I've been using. -Craig