From owner-freebsd-current@FreeBSD.ORG Wed Mar 21 05:36:28 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 6E77616A416 for ; Wed, 21 Mar 2007 05:36:28 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.freebsd.org (Postfix) with ESMTP id 0BDE013C45D for ; Wed, 21 Mar 2007 05:36:25 +0000 (UTC) (envelope-from scottl@samsco.org) Received: from phobos.samsco.home (phobos.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.8/8.13.8) with ESMTP id l2L5aHDw063911; Tue, 20 Mar 2007 23:36:22 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4600C451.2020407@samsco.org> Date: Tue, 20 Mar 2007 23:36:17 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; Intel Mac OS X; en-US; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 MIME-Version: 1.0 To: Kevin Day References: <52299CBE-F3AD-439D-820D-3FC3458614F8@dragondata.com> In-Reply-To: <52299CBE-F3AD-439D-820D-3FC3458614F8@dragondata.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Greylist: Sender succeeded SMTP AUTH authentication, not delayed by milter-greylist-2.0.2 (pooker.samsco.org [168.103.85.57]); Tue, 20 Mar 2007 22:36:23 -0700 (MST) X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.1 X-Spam-Checker-Version: SpamAssassin 3.1.1 (2006-03-10) on pooker.samsco.org 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 05:36:28 -0000 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 > > Backtrace: > > pmap_mapdev > nexus_activate_resource > bus_generic_activate_resource > bus_generic_activate_resource > bus_generic_activate_resource > pci_alloc_resource > bus_alloc_resource > aac_pci_attach > device_attach > device_probe_and_attach > bus_generic_attach > pci_attach > device_attach > device_probe_and_attach > bus_generic_attach > mptable_hostb_attach > nexus_attach > ... > > 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. Scott