From owner-freebsd-current@FreeBSD.ORG Sun Mar 25 19:50:23 2007 Return-Path: X-Original-To: freebsd-current@freebsd.org Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [69.147.83.52]) by hub.freebsd.org (Postfix) with ESMTP id 4D92716A401 for ; Sun, 25 Mar 2007 19:50:23 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from tokyo01.jp.mail.your.org (tokyo01.jp.mail.your.org [204.9.54.5]) by mx1.freebsd.org (Postfix) with ESMTP id 1DE2813C455 for ; Sun, 25 Mar 2007 19:50:21 +0000 (UTC) (envelope-from toasty@dragondata.com) Received: from mail.your.org (server3-a.your.org [64.202.112.67]) by tokyo01.jp.mail.your.org (Postfix) with ESMTP id 43A762AD5683; Sun, 25 Mar 2007 19:50:19 +0000 (UTC) Received: from [69.31.99.11] (pool011.dhcp.your.org [69.31.99.11]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTP id 28634A0A44E; Sun, 25 Mar 2007 19:50:18 +0000 (UTC) In-Reply-To: <4606A3B2.9050005@samsco.org> References: <52299CBE-F3AD-439D-820D-3FC3458614F8@dragondata.com> <4600C451.2020407@samsco.org> <1A67BF14-031C-4771-B4CD-82A46BBDA739@dragondata.com> <4606A3B2.9050005@samsco.org> Mime-Version: 1.0 (Apple Message framework v752.3) Content-Type: text/plain; charset=US-ASCII; delsp=yes; format=flowed Message-Id: Content-Transfer-Encoding: 7bit From: Kevin Day Date: Sun, 25 Mar 2007 14:50:27 -0500 To: Scott Long X-Mailer: Apple Mail (2.752.3) X-Mailman-Approved-At: Sun, 25 Mar 2007 19:51:14 +0000 Cc: freebsd-current@freebsd.org Subject: Re: aac & PAE not happy in -current X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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: Sun, 25 Mar 2007 19:50:23 -0000 On Mar 25, 2007, at 11:30 AM, Scott Long wrote: > Kevin Day wrote: >> Okay, after spending the better part of the weekend trying to >> figure out how to PXE boot the floppies that Dell gives you (using >> their own version of DOS), I've upgraded to the very latest system >> BIOS, controller firmware and kernel, and it's still requesting >> 128MB of memory. Nothing seems to have changed really. >> Any other suggestions? Booting into Linux seems to show that it's >> also eating 128MB of memory space there, so it's nothing FreeBSD >> is doing to cause this. >> Does your controller have the 128MB dimm for caching? I still >> can't see why they'd expose that to the host, but it's my only >> theory at the moment. > > Sorry for the confusion, it turns out that my math was wrong and my > machine is mapping all of the DIMM space as well, though it's not > 128MB. > Exposing the full DIMM size to the host is really just an act of > laziness on the part of the firmware engineers; it's convenient for > debugging the firmware and doing other development tasks, but it's not > useful for anything else. So, we're left with figuring out > workarounds. > I'm not sure if the driver can force less of the space to be mapped, > I'll look into that. The other workaround is to change > VM_KMEM_SIZE_MAX > in /sys/i386/include/vmparam.h to a larger value, but probably no more > than around 500. Okay, I tried: 400 - no difference 500 - Gets further into the boot, but runs out when it tries to exec init(?) 550 - aac0 complains "Not enough contiguous memory available", then the next PCI device that tries to run can't alloc anything 600 - back to what was happening at 400, aac0 can't alloc enough kernel virtual memory Any other suggestions? -- Kevin