From owner-freebsd-hackers  Tue Apr 22 15:53:52 1997
Return-Path: <owner-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id PAA13266
          for hackers-outgoing; Tue, 22 Apr 1997 15:53:52 -0700 (PDT)
Received: from root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.5/8.8.5) with ESMTP id PAA13259
          for <hackers@freebsd.org>; Tue, 22 Apr 1997 15:53:50 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by root.com (8.8.5/8.6.5) with SMTP id PAA16049; Tue, 22 Apr 1997 15:55:21 -0700 (PDT)
Message-Id: <199704222255.PAA16049@root.com>
X-Authentication-Warning: implode.root.com: localhost [127.0.0.1] didn't use HELO protocol
To: Jaye Mathisen <mrcpu@cdsnet.net>
cc: hackers@freebsd.org
Subject: Re: Can't put 512MB ram in box ... Extended memory question. 
In-reply-to: Your message of "Tue, 22 Apr 1997 10:36:37 PDT."
             <Pine.NEB.3.95.970422103449.25438i-100000@mail.cdsnet.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Tue, 22 Apr 1997 15:55:21 -0700
Sender: owner-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>I get a "kmem_suballoc" panic.
>
>kmem_suballoc: bad status return of 3
>
>
>Any ideas why?  Kernel is compiled with MAXMEM=523264.  The memory is seen
>by the BIOS boot.

   It means that the kernel has run out of kernel virtual memory. You have
two options: either more carefully tune your system (maxusers, NMBCLUSTERS)
to take less KVM, or (difficult) apply various changes to increase the kernel
virtual memory. I had to do the latter on wcarchive, but not only does this
require kernel changes, but also requires that the userland be rebuilt, and
additionally breaks BSD/OS compatibility.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project