From owner-freebsd-current@FreeBSD.ORG Sun Mar 25 10:54:59 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 E5E8416A401 for ; Sun, 25 Mar 2007 10:54:59 +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 B75F013C45E for ; Sun, 25 Mar 2007 10:54:59 +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 DA02F2AD569F; Sun, 25 Mar 2007 10:54:57 +0000 (UTC) Received: from [69.31.99.14] (pool014.dhcp.your.org [69.31.99.14]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) by mail.your.org (Postfix) with ESMTP id D1A66A0A44E; Sun, 25 Mar 2007 10:54:56 +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: <1A67BF14-031C-4771-B4CD-82A46BBDA739@dragondata.com> Content-Transfer-Encoding: 7bit From: Kevin Day Date: Sun, 25 Mar 2007 05:55:32 -0500 To: Scott Long X-Mailer: Apple Mail (2.752.3) X-Mailman-Approved-At: Sun, 25 Mar 2007 11:23:31 +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 10:55:00 -0000 On Mar 21, 2007, at 12:36 AM, Scott Long wrote: >> Booting the same kernel without PAE I get the same thing: >> 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 >> aac0: [FAST] >> aac0: Adaptec Raid Controller 2.0.0-1 >> and it works fine. >> Is this a known problem, or is there any other info I can give? >> Happy to try anything anyone might suggest. :) > > 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. 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.