Bug 17680

Summary: Multiple crashes due to load in 4.0/5.0 environment
Product: Base System Reporter: geniusj <geniusj>
Component: kernAssignee: freebsd-bugs (Nobody) <bugs>
Status: Closed FIXED    
Severity: Affects Only Me    
Priority: Normal    
Version: 4.0-STABLE   
Hardware: Any   
OS: Any   

Description geniusj 2000-03-30 07:30:01 UTC 
	Multiple crashes I have experienced, here's a summary of a couple..

	Maxusers was 128 on both boxes..

	NFS setup on a raid server using vinum and nfsd .. if I did du -k or something on the NFS mount, the machine would freeze and require a reboot..

	On another machine, same release dates, I ran a perl script that looped an executable file (Maxproc limits were set at 1024, max for machine was 4192)
	The Machine crashed completely as a result.. It didnt even hit the maxpr        On another machine with an older cvs date, we had a BRIDGE setup.. options BRIDGE etc, and it too crashed under heavy traffic.. I think it is pretty serious what is happening, if it has been fixed within the last 6 or so days, then i'm sorry, but would just like to report this as I found it a pretty nasty bug.

Fix: 

I wish I knew
How-To-Repeat: 	make perl script on 4.0 box that loops just like.. fetch for instance on a file or something.
Comment 1 Chris D.Faulhaber freebsd_committer freebsd_triage 2000-03-31 01:31:34 UTC 
Responsible Changed
From-To: gnats-admin->freebsd-bugs

Misfiled PR
Comment 2 jedgar 2000-03-31 01:35:42 UTC 
Any chance you can give some specifics here.  'if I did du -k or
something' and 'fetch for instance on a file or something' aren't going to
fly to far.  A backtrace of a dump or panic message is much more useful
than 'crashed under heavy traffic'.

-----
Chris D. Faulhaber - jedgar@fxp.org - jedgar@FreeBSD.org
--------------------------------------------------------
FreeBSD: The Power To Serve   -   http://www.FreeBSD.org
Comment 3 Mike Barcroft freebsd_committer freebsd_triage 2001-07-22 01:58:06 UTC 
State Changed
From-To: open->closed


Not enough information to make use of this PR.  Timeout; no response 
from originator.