From owner-freebsd-hackers@FreeBSD.ORG Sun Feb 12 05:37:24 2006 Return-Path: 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 975D116A420 for ; Sun, 12 Feb 2006 05:37:24 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from vms046pub.verizon.net (vms046pub.verizon.net [206.46.252.46]) by mx1.FreeBSD.org (Postfix) with ESMTP id 43D3643D46 for ; Sun, 12 Feb 2006 05:37:24 +0000 (GMT) (envelope-from babkin@verizon.net) Received: from verizon.net ([138.89.156.245]) by vms046.mailsrvcs.net (Sun Java System Messaging Server 6.2-4.02 (built Sep 9 2005)) with ESMTPA id <0IUK006BF7LTJA4A@vms046.mailsrvcs.net> for freebsd-hackers@freebsd.org; Sat, 11 Feb 2006 23:37:10 -0600 (CST) Date: Sun, 12 Feb 2006 00:37:04 -0500 From: Sergey Babkin Sender: root To: Jacques Fourie Message-id: <43EEC980.32C2FA40@verizon.net> MIME-version: 1.0 X-Mailer: Mozilla 4.7 [en] (X11; U; FreeBSD 4.7-RELEASE i386) Content-type: text/plain; charset=us-ascii Content-transfer-encoding: 7bit X-Accept-Language: en, ru References: <20060208164141.GA21718@trispen.com> <20060208185836.GA55307@xor.obsecurity.org> <20060209092139.GB21718@trispen.com> X-Mailman-Approved-At: Sun, 12 Feb 2006 05:42:21 +0000 Cc: freebsd-hackers@freebsd.org Subject: Re: 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: babkin@users.sf.net List-Id: Technical Discussions relating to FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 12 Feb 2006 05:37:24 -0000 Jacques Fourie wrote: > > I have installed 6.0-RELEASE and the behaviour is still the same. If I try > to pre-load an md_image of 64M with 4G of RAM installed, the kernel panics > early in the boot cycle. Here is the panic on 6.0-RELEASE: > > 131072K of memory above 4GB ignored This is a kind of stupid question but is there any chance that the 64MB image overlaps with the PCI address hole? To elaborate: with 4GB memory installed there would be no address range to access the memory-mapped 32-bit PCI cards. So the motherboard circuitry relocates some amount of memory (the 128MB shown above) from some lower address to above 4GB and frees this address space below 4GB for mapping of the PCI cards. So the interesting question is: what is the address of this PCI hole and what is the loading address of the FreeBSD md_image? If they overlap then naturally a part of the image would go into nowhere and cause a panic. On my machine this PCI hole can be disabled in BIOS (I think so, there is also some kind of configuration in BIOS but I did not pay much attention to it as I don't have 4GB). -SB