From owner-freebsd-bugs Sun Jul 25 23:25:30 1999 Delivered-To: freebsd-bugs@freebsd.org Received: from allegro.lemis.com (allegro.lemis.com [192.109.197.134]) by hub.freebsd.org (Postfix) with ESMTP id C60A315155; Sun, 25 Jul 1999 23:25:12 -0700 (PDT) (envelope-from grog@freebie.lemis.com) Received: from freebie.lemis.com (freebie.lemis.com [192.109.197.137]) by allegro.lemis.com (8.9.1/8.9.0) with ESMTP id PAA14855; Mon, 26 Jul 1999 15:53:29 +0930 (CST) Received: (from grog@localhost) by freebie.lemis.com (8.9.3/8.9.0) id PAA58951; Mon, 26 Jul 1999 15:53:07 +0930 (CST) Date: Mon, 26 Jul 1999 15:53:07 +0930 From: Greg Lehey To: Biju Susmer Cc: FreeBSD Questions Subject: Re: "3.2-RELEASE #0" crashed Message-ID: <19990726155307.U51019@freebie.lemis.com> References: <000b01bed719$10eeeb00$88291fac@wipro.tcpn.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.95.4i In-Reply-To: <000b01bed719$10eeeb00$88291fac@wipro.tcpn.com>; from Biju Susmer on Mon, Jul 26, 1999 at 09:13:45AM +0530 WWW-Home-Page: http://www.lemis.com/~grog X-PGP-Fingerprint: 6B 7B C3 8C 61 CD 54 AF 13 24 52 F8 6D A4 95 EF Organization: LEMIS, PO Box 460, Echunga SA 5153, Australia Phone: +61-8-8388-8286 Fax: +61-8-8388-8725 Mobile: +61-41-739-7062 Sender: owner-freebsd-bugs@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org [Format recovered--see http://www.lemis.com/email/email-format.html] [Moved to FreeBSD-questions; there's no evidence of a bug here] On Monday, 26 July 1999 at 9:13:45 +0530, Biju Susmer wrote: > Hi, > > The following program caused my system to crash and reboot. I was > doing a stress test on my machine by keeping it 200% busy... My uid is > 1001 [not root ;) ]. I attached all details which i think may be useful. > The system has swap of 37MB on /dev/wd0s2b. > > Category: kern > Sev: serious > Pri: High > Class: sw_bug It would really help if you sent this message in a legible format. It's very difficult to read this. > 3 out of 6 times it rebooted. In all cases, the message "swap_pager: > out of swap space" was repeated at least 7 times. The messages > generated were different. > > * first time i could not catch (un-expected) > * second and third time it showed some thing, and gave me 15 > seconds, but i could not do anything. I remember it is some thing "de > allocated many times" or so. PLEASE TELL ME HOW CAN I CATCH THE > MESSAGES IF I WANT TO GIVE IT TO U!! You can't in this point. You need to enable dumping. Set dumpdev in /etc/rc.conf to the name of a swap partition which is at least the size of physical memory. For example, dumpdev=/dev/wd0b This will cause the system to write the dump when it crashes. In order to enable it, you need a debug kernel. See the handbook for further details. > The rest 3 times, it went to some loop, i believe. Nothing > worked. The chars i typed were echod on the terminal in which i > started the program. Also switching screens (v0-v2) were fine, but > nothing echod on those screens. Intr or quit char didn't have any > effect. at last after one minute i resetted. > > i tried changing kern.securelevel to 2 but that also didn't help. > > > $ cat crash.c > /* program to create "out of CPU" error */ > #include > #include > > main() > { > while(1) > if(fork()< 0) /* multiply... */ > while(1); /* if no more processes, eat up CPU */ > } It's interesting that you should have run out of swap before you ran out of processes, but basically I don't think what you're doing is a reasonable use of the system. No UNIX system handles this situation well, and FreeBSD is no exception. Since you supply a lot of information, but nothing on swap usage, I suspect that your swap partitions are too small. Greg -- See complete headers for address, home page and phone numbers finger grog@lemis.com for PGP public key To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-bugs" in the body of the message