From owner-freebsd-questions  Thu Oct  2 22:58:52 1997
Return-Path: <owner-freebsd-questions>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.7/8.8.7) id WAA20593
          for questions-outgoing; Thu, 2 Oct 1997 22:58:52 -0700 (PDT)
Received: from gdi.uoregon.edu (gdi.uoregon.edu [128.223.170.30])
          by hub.freebsd.org (8.8.7/8.8.7) with ESMTP id WAA20588
          for <questions@FreeBSD.ORG>; Thu, 2 Oct 1997 22:58:49 -0700 (PDT)
Received: from localhost (dwhite@localhost)
          by gdi.uoregon.edu (8.8.5/8.8.5) with SMTP id WAA26433;
          Thu, 2 Oct 1997 22:58:41 -0700 (PDT)
Date: Thu, 2 Oct 1997 22:58:41 -0700 (PDT)
From: Doug White <dwhite@gdi.uoregon.edu>
Reply-To: Doug White <dwhite@resnet.uoregon.edu>
To: Adam Laurie <adam@algroup.co.uk>
cc: questions@FreeBSD.ORG
Subject: Re: putting MAXMEM option into 2.2.2 causes fatal trap 9
In-Reply-To: <342D8050.6878178@algroup.co.uk>
Message-ID: <Pine.BSF.3.96.971002225816.26112X-100000@gdi.uoregon.edu>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-questions@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Sat, 27 Sep 1997, Adam Laurie wrote:

> On a system that was otherwise happy, adding the 
> 
> option "MAXMEM=131072"
> 
> to the kernel config causes the above error during boot. The BIOS
> reports 131072K present, and I have disabled all shadowing. 
> 
> Any ideas?

Try setting it to 131071.

I think a trap 9 is a kernel attempt to map memory that doesn't exist.

Doug White                              | University of Oregon  
Internet:  dwhite@resnet.uoregon.edu    | Residence Networking Assistant
http://gladstone.uoregon.edu/~dwhite    | Computer Science Major