From owner-freebsd-current@FreeBSD.ORG Thu Sep 30 16:04:42 2004 Return-Path: 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 BA38E16A4CE for ; Thu, 30 Sep 2004 16:04:42 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 66DE043D39 for ; Thu, 30 Sep 2004 16:04:42 +0000 (GMT) (envelope-from scottl@FreeBSD.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id i8UG5UIh073173; Thu, 30 Sep 2004 10:05:32 -0600 (MDT) (envelope-from scottl@FreeBSD.org) Message-ID: <415C2E61.8070904@FreeBSD.org> Date: Thu, 30 Sep 2004 10:03:45 -0600 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.2) Gecko/20040831 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Claus Guttesen References: <20040930120946.26047.qmail@web14107.mail.yahoo.com> In-Reply-To: <20040930120946.26047.qmail@web14107.mail.yahoo.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org 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 List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 30 Sep 2004 16:04:42 -0000 Claus Guttesen wrote: >>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 > That's not always the case. The system might be excluding a large part of the address space for some reason and mapping the RAM around it. Can you send a verbose dmesg to me in private? Scott