Date: Fri, 1 Nov 1996 09:11:02 -0600 (CST) From: Joe Greco <jgreco@brasil.moneng.mei.com> To: karpen@ocean.campus.luth.se (Mikael Karpberg) Cc: jgreco@brasil.moneng.mei.com, greg@uswest.net, freebsd-hackers@freefall.freebsd.org, ponds!rivers@dg-rtp.dg.com Subject: Re: Another data point in the daily panics... Message-ID: <199611011511.JAA00196@brasil.moneng.mei.com> In-Reply-To: <199611011344.OAA08663@ocean.campus.luth.se> from "Mikael Karpberg" at Nov 1, 96 02:44:17 pm
next in thread | previous in thread | raw e-mail | index | archive | help
> 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?
daily-planet2# uptime
9:06AM up 18 mins, 2 users, load averages: 100.51, 86.35, 49.57
daily-planet2# ps agxuww|grep crashme|wc
201 3307 20448
daily-planet2# top
load averages: 101.47, 91.55, 56.48 09:08:56
425 processes: 102 running, 322 sleeping, 1 stopped
Cpu states: 66.7% user, 0.0% nice, 33.3% system, 0.0% interrupt, 0.0% idle
Mem: 41M Active, 2256K Inact, 8948K Wired, 4920K Cache, 2880K Buf, 4104K Free
Swap: 131M Total, 18M Used, 113M Free, 14% Inuse
PID USERNAME PRI NICE SIZE RES STATE TIME WCPU CPU COMMAND
5384 jgreco 82 0 164K 428K RUN 0:00 1.21% 1.18% crashme
5444 jgreco 82 0 164K 428K RUN 0:00 1.18% 1.14% crashme
5409 jgreco 82 0 164K 428K RUN 0:00 1.18% 1.14% crashme
5435 jgreco 83 0 164K 428K RUN 0:00 1.14% 1.11% crashme
5465 jgreco 82 0 164K 428K RUN 0:00 1.15% 1.11% crashme
5443 jgreco 82 0 164K 428K RUN 0:00 1.10% 1.07% crashme
5442 jgreco 82 0 164K 428K RUN 0:00 1.10% 1.07% crashme
5431 jgreco 82 0 164K 428K RUN 0:00 1.06% 1.03% crashme
5491 jgreco 82 0 164K 428K RUN 0:00 1.08% 1.03% crashme
5164 jgreco 81 0 164K 428K RUN 0:01 1.03% 1.03% crashme
5470 jgreco 81 0 164K 428K RUN 0:00 0.99% 0.95% crashme
5415 jgreco 81 0 164K 428K RUN 0:00 0.98% 0.95% crashme
5475 jgreco 81 0 164K 428K RUN 0:00 0.99% 0.95% crashme
5416 jgreco 81 0 164K 428K RUN 0:00 0.94% 0.92% crashme
5485 jgreco 81 0 164K 428K RUN 0:00 0.95% 0.92% crashme
5380 jgreco 81 0 164K 428K RUN 0:00 0.94% 0.92% crashme
5397 jgreco 81 0 164K 428K RUN 0:00 0.94% 0.92% crashme
Unfortunately this fills the 64MB of RAM on the machine. I do not think
I have ever seen a FreeBSD machine with so many runnable processes.
I will let it run for a while and see if anything interesting happens.
... JG
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?199611011511.JAA00196>