From hsu@mail.clinet.fi  Tue Dec 22 06:49:39 1998
Received: from lohi.clinet.fi (lohi.clinet.fi [194.100.0.7])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id GAA26422
          for <FreeBSD-gnats-submit@freebsd.org>; Tue, 22 Dec 1998 06:49:37 -0800 (PST)
          (envelope-from hsu@mail.clinet.fi)
Received: from katiska.clinet.fi (katiska.clinet.fi [194.100.0.4])
	by lohi.clinet.fi (8.9.1/8.9.0) with ESMTP id QAA14876
	for <FreeBSD-gnats-submit@freebsd.org>; Tue, 22 Dec 1998 16:50:17 +0200 (EET)
Received: (from root@localhost)
	by katiska.clinet.fi (8.9.0/8.9.0) id QAA23558;
	Tue, 22 Dec 1998 16:49:31 +0200 (EET)
Message-Id: <199812221449.QAA23558@katiska.clinet.fi>
Date: Tue, 22 Dec 1998 16:49:31 +0200 (EET)
From: Heikki Suonsivu <hsu@clinet.fi>
Reply-To: hsu@clinet.fi
To: FreeBSD-gnats-submit@freebsd.org
Subject: maxusers 1024 results in unbootable kernel
X-Send-Pr-Version: 3.2

>Number:         9171
>Category:       kern
>Synopsis:       maxusers 1024 results in unbootable kernel
>Confidential:   no
>Severity:       serious
>Priority:       medium
>Responsible:    freebsd-bugs
>State:          closed
>Quarter:        
>Keywords:       
>Date-Required:  
>Class:          sw-bug
>Submitter-Id:   current-users
>Arrival-Date:   Tue Dec 22 06:50:00 PST 1998
>Closed-Date:    Wed Aug 11 01:13:47 PDT 1999
>Last-Modified:  Tue Aug 17 04:00:01 PDT 1999
>Originator:     Heikki Suonsivu
>Release:        FreeBSD 2.2.7-STABLE i386
>Organization:
Clinet, Espoo, Finland
>Environment:

-stable (I think this problem has been around long)

64M P90 IDE.

>Description:

kernel with maxusers 1024 panics on boot:

kmem_suballoc: bad status return of 3
panic: kmem_suballoc

>How-To-Repeat:

Set maxusers to 1024 and boot on 64M P90.  I think this is repeatable on
this kind of configuration, but I am not sure whether it happens on larger
configurations.

>Fix:

I do not know.  I guess the actual problem is that "maxusers" does not
really indicate any relation to maximum number of users.  256 is not enough
for host running just an irc server, nothing else.  Increasing NMBCLUSTERS
separately seems to be the "fix" here (in addition to fixing process sizes,
file descriptors and such more standard things).

>Release-Note:
>Audit-Trail:

From: Robert Garrett <eagle@phc.igs.net>
To: freebsd-gnats-submit@freebsd.org, hsu@clinet.fi
Cc:  
Subject: Re: kern/9171: maxusers 1024 results in unbootable kernel
Date: Sun, 08 Aug 1999 21:41:00 -0400

 wasnt this fixed a while back? at least in -current
 
 
State-Changed-From-To: open->closed 
State-Changed-By: des 
State-Changed-When: Wed Aug 11 01:13:47 PDT 1999 
State-Changed-Why:  
This was fixed in both -CURRENT and -STABLE early this year. 

From: Heikki Suonsivu <hsu@vdslsystems.com>
To: Robert Garrett <eagle@phc.igs.net>
Cc: freebsd-gnats-submit@freebsd.org, hsu@clinet.fi
Subject: Re: kern/9171: maxusers 1024 results in unbootable kernel
Date: Tue, 17 Aug 1999 13:15:47 +0300 (EEST)

 Robert Garrett writes:
  > wasnt this fixed a while back? at least in -current
 
 It was not couple of months ago.  I have been using -stable.
 
 -- 
 Heikki Suonsivu / Taysikuu 10 C 83 / FI-02150 Espoo / FINLAND,
 hsu@vdslsystems.com mobile +358-40-5519679
 
>Unformatted:
