From owner-freebsd-questions  Wed Sep 10 18:36:00 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id SAA13536
          for questions-outgoing; Wed, 10 Sep 1997 18:36:00 -0700 (PDT)
Received: from implode.root.com (implode.root.com [198.145.90.17])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id SAA13521
          for <questions@FreeBSD.ORG>; Wed, 10 Sep 1997 18:35:57 -0700 (PDT)
Received: from implode.root.com (localhost [127.0.0.1])
	by implode.root.com (8.8.5/8.8.5) with ESMTP id SAA14031;
	Wed, 10 Sep 1997 18:38:31 -0700 (PDT)
Message-Id: <199709110138.SAA14031@implode.root.com>
To: Network Coordinator <nc@ai.net>
cc: questions@FreeBSD.ORG
Subject: Re: Memory >64 suballoc error? 
In-reply-to: Your message of "Wed, 10 Sep 1997 20:34:21 EDT."
             <Pine.BSF.3.91.970910203217.21381A-100000@alyssa.ai.net> 
From: David Greenman <dg@root.com>
Reply-To: dg@root.com
Date: Wed, 10 Sep 1997 18:38:31 -0700
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

>
>When trying to get BSD to recognize >64MB in certain machines [AMI bios] 
>only 130688k is reported instead of 131xxxk, and the kernel with the 
>appropriate MAXMEM value hangs immediately during initial boot up with a 
>sub allocation panic error (3). 
>
>Any ideas? This is readily reproducible, but doesn't happen on any other 
>machine I have found . The motherboard is a generic.

   The suballoc failure is caused by running out of kernel virtual memory.
This is likely caused by a kernel config parameter being too high.

-DG

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