From owner-freebsd-hackers@FreeBSD.ORG  Wed Feb  8 16:41:55 2006
Return-Path: <owner-freebsd-hackers@FreeBSD.ORG>
X-Original-To: freebsd-hackers@freebsd.org
Delivered-To: freebsd-hackers@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id 0557116A420
	for <freebsd-hackers@freebsd.org>; Wed,  8 Feb 2006 16:41:55 +0000 (GMT)
	(envelope-from jacques@trispen.com)
Received: from brolloks.trispen.com (brolloks.trispen.com [196.22.177.34])
	by mx1.FreeBSD.org (Postfix) with ESMTP id D7C4143D46
	for <freebsd-hackers@freebsd.org>; Wed,  8 Feb 2006 16:41:52 +0000 (GMT)
	(envelope-from jacques@trispen.com)
Received: by brolloks.trispen.com (Postfix, from userid 1000)
	id 951821E8; Wed,  8 Feb 2006 18:41:41 +0200 (SAST)
Date: Wed, 8 Feb 2006 18:41:41 +0200
From: Jacques Fourie <jf@trispen.com>
To: freebsd-hackers@freebsd.org
Message-ID: <20060208164141.GA21718@trispen.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
User-Agent: Mutt/1.4.2.1i
Subject: Pre-loaded mfsroot size and FreeBSD 4.9 with 4G RAM
X-BeenThere: freebsd-hackers@freebsd.org
X-Mailman-Version: 2.1.5
Precedence: list
Reply-To: jf@trispen.com
List-Id: Technical Discussions relating to FreeBSD
	<freebsd-hackers.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>, 
	<mailto:freebsd-hackers-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-hackers>
List-Post: <mailto:freebsd-hackers@freebsd.org>
List-Help: <mailto:freebsd-hackers-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-hackers>,
	<mailto:freebsd-hackers-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 08 Feb 2006 16:41:55 -0000

Hi,

I am pre-loading an image (used as MFS root) from the boot loader on FreeBSD
4.9 by using 'load -t mfs_root mfsroot' in loader.conf. The size of this
image is 64M. If I have 4G of RAM in the machine, the 64M size causes the
kernel to panic almost immediately. With only 2G of RAM the kernel boots
without a problem. I have tried to increase the KVA_PAGES value to 512 but
the kernel still panics. If I decrease the image size to 40M the kernel
boots successfully on a machine with 4G of RAM. Any ideas as to how I can go
about finding (or fixing) this problem?

Regards,
jacques