From sfarrell@couatl.uchicago.edu  Sun Nov  8 14:12:35 1998
Received: from couatl.uchicago.edu (couatl.uchicago.edu [128.135.21.64])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id OAA27516
          for <FreeBSD-gnats-submit@freebsd.org>; Sun, 8 Nov 1998 14:12:34 -0800 (PST)
          (envelope-from sfarrell@couatl.uchicago.edu)
Received: (from sfarrell@localhost)
	by couatl.uchicago.edu (8.9.1/8.9.0) id PAA07323;
	Sun, 8 Nov 1998 15:52:46 -0600 (CST)
Message-Id: <199811082152.PAA07323@couatl.uchicago.edu>
Date: Sun, 8 Nov 1998 15:52:46 -0600 (CST)
From: sfarrell@farrell.org
Reply-To: sfarrell@farrell.org
To: FreeBSD-gnats-submit@freebsd.org
Subject: maxprocsperuid and sybase segfault
X-Send-Pr-Version: 3.2

>Number:         8607
>Category:       kern
>Synopsis:       maxprocsperuid setting causes sybase/linux segfaul
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Sun Nov  8 14:20:00 PST 1998
>Closed-Date:    Thu Jul 19 15:02:30 PDT 2001
>Last-Modified:  Thu Jul 19 15:05:23 PDT 2001
>Originator:     stephen farrell
>Release:        FreeBSD 3.0.0-RELEASE i386
>Organization:
>Environment:

Running Sybase/Linux under FreeBSD current.  I don't believe the problem
encountered is as a result of emulation.

>Description:

	Here is my posting to emulators mailing list:

This is a follow-up to my last post on the subject of problems with
sybase/linux running under emulation in FreeBSD 3.0R.

Here's what I've found out: The problem is triggered when maxusers is
set from default 32 to 64 (sorry, no other data points).  I've
narrowed down the various variables that maxusers affect, and
maxprocsperuid appears to be the culprit.  Interestingly, even if the
kernel is built with maxusers 64 (the broken value), then using sysctl
to change maxprocsperuid will fix sybase's problem (I think you just
need to frob it a bit--it doesn't matter what you set it to (521 is a
known working value)).  It might also be interesting to note that when
sysctl is used to change maxprocsperuid, the value of that variable
doesn't change in the kernel (at least as it's referenced in
kernel_resource.c).

I should point out that it appears to be a general kernel problem and
not an emulation problem, as there are no references to maxusers and
friends in the linux emulator.

	More information can be found about this by searching for
	sybase and freebsd (and possibly "farrell") at dejanews.

	Also note this URL: http://people.healthquiz.com/~sfarrell/traces/
	for some ktrace output.

>How-To-Repeat:

	Set maxusers to 64 and try to run sybase ASE on FreeBSD
	and see it die.  Change maxprocesperuid to 521 with systctl
	and see it work.

>Fix:
	
	No fix is know to me.  Playing with sysctl and changing the
	maxprocesperuid does seem to be a work-around.  

>Release-Note:
>Audit-Trail:
State-Changed-From-To: open->feedback 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 13:48:07 PDT 2001 
State-Changed-Why:  

Does this problem still occur in newer versions of FreeBSD, 
such as 4.3-RELEASE? 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=8607 
State-Changed-From-To: feedback->closed 
State-Changed-By: mike 
State-Changed-When: Thu Jul 19 15:02:30 PDT 2001 
State-Changed-Why:  

The orginator, in a private e-mail to me, has indicated that 
he is no longer able to confirm whether this bug still exists. 
If someone else encounters this bug, they should open a new 
PR. 

http://www.FreeBSD.org/cgi/query-pr.cgi?pr=8607 
>Unformatted:
