From owner-freebsd-hackers Fri Nov 1 05:36:11 1996 Return-Path: owner-hackers Received: (from root@localhost) by freefall.freebsd.org (8.7.5/8.7.3) id FAA02193 for hackers-outgoing; Fri, 1 Nov 1996 05:36:11 -0800 (PST) Received: from ocean.campus.luth.se (ocean.campus.luth.se [130.240.194.116]) by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id FAA02173 for ; Fri, 1 Nov 1996 05:36:04 -0800 (PST) Received: (from karpen@localhost) by ocean.campus.luth.se (8.7.5/8.7.3) id OAA08663; Fri, 1 Nov 1996 14:44:17 +0100 (MET) From: Mikael Karpberg Message-Id: <199611011344.OAA08663@ocean.campus.luth.se> Subject: Re: Another data point in the daily panics... To: jgreco@brasil.moneng.mei.com (Joe Greco) Date: Fri, 1 Nov 1996 14:44:17 +0100 (MET) Cc: greg@uswest.net, freebsd-hackers@freefall.freebsd.org, ponds!rivers@dg-rtp.dg.com In-Reply-To: <199610311645.KAA27895@brasil.moneng.mei.com> from Joe Greco at "Oct 31, 96 10:45:48 am" X-Mailer: ELM [version 2.4ME+ PL22 (25)] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-hackers@FreeBSD.ORG X-Loop: FreeBSD.org Precedence: bulk According to Joe Greco: > > > Recall, this is a 386DX-33, 8MEG, IDE controller, sio ports, running > > > my news and mail and SL/IP connections. > > I run several stable news servers too (soon to be more)... Mr. Rivers > seems to be running a "stress test from hell" configuration :-( I read some mail someone showed me, not long ago... I think it was from the NetBSD lists... Some guy stating (in some argument with a Linux hacker) that "Your machine is probably idle while you read this", upon which the Linux hacker said "No, it's not. I fire up 40 creashmes in init". I'd say that linux hacker is boooored ;-) Then again, I know a friends 2.1.5 machine rebooted after running 30 seconds of "crashme". Firing up _40_ at boot time, just for kicks, must mean he can get a lot more out of Linux's vm/fs system then we can get out of FreeBSD's, when it comes to stablilty. If you want to stress the machine, and shake out bugs, "crashme" seems quite a nice stresser for the system, doing a lot of mean stuff, but nothing illegal (which should not be possible anyway, or the system is not very safe, or?) as far as I know. I know we got HUGE amounts of "sig 10 recieved" when running crashme. So, if crashme is not reading longs out of alignment, or so, then there is a problem in the system somewhere. Anyone tried to fire up 40 crashmes and wait? Should produce nice output for debugging a stressed system, no? /Mikael