From owner-freebsd-current@FreeBSD.ORG Wed Mar 21 17:58: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 91D1C16A4E2 for ; Wed, 21 Mar 2007 17:58: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 5F84213C4EB for ; Wed, 21 Mar 2007 17:58: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 0EE8D2AD640C; Wed, 21 Mar 2007 17:58: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 640E5A0A44E; Wed, 21 Mar 2007 17:58:18 +0000 (UTC) In-Reply-To: <4600C451.2020407@samsco.org> References: <52299CBE-F3AD-439D-820D-3FC3458614F8@dragondata.com> <4600C451.2020407@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: Wed, 21 Mar 2007 12:58:24 -0500 To: Scott Long X-Mailer: Apple Mail (2.752.3) X-Mailman-Approved-At: Wed, 21 Mar 2007 18:18:59 +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: Wed, 21 Mar 2007 17:58:23 -0000 On Mar 21, 2007, at 12:36 AM, Scott Long wrote: > Kevin Day wrote: >> I've got a Dell PowerEdge 2650 running the 200702 -current >> snapshot. It's fine with 2GB of ram, but when I tried bumping it >> to 6GB and turning on PAE, the aac driver panics on boot. >> aacch0: port 0xcc00-0xccff mem >> 0xfccff000-0xfccfffff irq 30 at device 6.0 on pci5 >> aacch1: port 0xc800-0xc8ff mem >> 0xfccfe000-0xfccfefff irq 31 at device 6.1 on pci5 >> aac0: mem 0xf0000000-0xf7ffffff irq 30 at device >> 8.1 on pci4 >> panic: pmap_mapdev: Couldn't alloc kernel virtual memory > > The device is asking for 128MB of register space. This is exhausting > the limit on the amount of kernel mapped memory, hence the panic. The > difference between PAE and non-PAE is likely that the non-PAE case > isn't consuming as much kernel address space for the extra page > tables, > so you're squeaking by. > > The 128MB of register space is wrong, but it's something that the aac > firmware is causing. I don't have a 2650, but my 2450 only tries to > claim 4K for registers for the aac device, and the hardware is > basically > identical to the 2650. Maybe try flashing in a newer (or older) > firmware? Knowing what firmware version you have would help. I thought it was a bit odd that it wanted a 128MB window as well. This controller DOES have a 128MB battery backed dimm in it, but I can't imagine why it would need to expose that to the host. aac0: i960RX 100MHz, 118MB cache memory, optional battery present 118MB of cache, plus a register window rounds up to 128MB? Maybe just a coincidence though. It says it's using firmware "2.7-1 [Build 3170]". It appears that they're up to 2.8.1 as the latest firmware now, I'll give it a try to upgrade it on my next trip to the datacenter. Nothing in their changelog seems to indicate any changes that might affect this, but I'll give it a shot. I can tell you that a quick scan of all of our systems, all 14 Dells we have that contain a 3/Di, they're all requesting 128MB of memory space. aac0: mem 0xf0000000-0xf7ffffff irq 16 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 7 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 ... etc And we bought them all at random times, so they all probably have different firmware versions.