From owner-freebsd-current@FreeBSD.ORG  Thu Sep 30 12:09:46 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id EC98E16A4FD
	for <freebsd-current@FreeBSD.org>;
	Thu, 30 Sep 2004 12:09:46 +0000 (GMT)
Received: from web14107.mail.yahoo.com (web14107.mail.yahoo.com
	[216.136.172.137])
	by mx1.FreeBSD.org (Postfix) with SMTP id A548743D2F
	for <freebsd-current@FreeBSD.org>;
	Thu, 30 Sep 2004 12:09:46 +0000 (GMT)
	(envelope-from cguttesen@yahoo.dk)
Message-ID: <20040930120946.26047.qmail@web14107.mail.yahoo.com>
Received: from [194.248.174.58] by web14107.mail.yahoo.com via HTTP;
	Thu, 30 Sep 2004 14:09:46 CEST
Date: Thu, 30 Sep 2004 14:09:46 +0200 (CEST)
From: Claus Guttesen <cguttesen@yahoo.dk>
To: Scott Long <scottl@FreeBSD.org>
In-Reply-To: <415BB667.9000302@FreeBSD.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=iso-8859-1
Content-Transfer-Encoding: 8bit
cc: freebsd-current@FreeBSD.org
Subject: Re: unable to install beta6 [amd64] on Dell 2850 with 4 GB
	RAM,workaround
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Thu, 30 Sep 2004 12:09:47 -0000

> The AMR driver cannot handle >4GB of RAM.  Even
> though you only have 
> 4GB, your chipset is remapping part of it to the
> >4GB region.  The 
> driver incorrectly interfaces with busdma and cannot
> handle this
> scenario very well.  The panic is to be expected. 
> You can verify
> this by setting the tunable 'hw.physmem' in the
> loader to some
> value under 4GB to artifically limit the amount of
> RAM that the OS
> sees.

Added hw.physmem=4G to /boot/loader.conf and it seems
to solve the issue. Dmesg now tells me that I have

real memory  = 3489398784 (3327 MB)
avail memory = 3367739392 (3211 MB)

It seems that it does ignore some RAM, but is this the
correct behaviour?

Without hw.physmem I get

real memory  = 5100273664 (4864 MB)
avail memory = 4125847552 (3934 MB)

So it appears to perform an incorrect probing of
memory.

Thank you.
Claus