Date: Wed, 21 Mar 2007 12:58:24 -0500 From: Kevin Day <toasty@dragondata.com> To: Scott Long <scottl@samsco.org> Cc: freebsd-current@freebsd.org Subject: Re: aac & PAE not happy in -current Message-ID: <A53A3AAB-C9B3-4A77-96EE-B987942FB385@dragondata.com> In-Reply-To: <4600C451.2020407@samsco.org> References: <52299CBE-F3AD-439D-820D-3FC3458614F8@dragondata.com> <4600C451.2020407@samsco.org>
index | next in thread | previous in thread | raw e-mail
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: <AAC RAID Channel> port 0xcc00-0xccff mem >> 0xfccff000-0xfccfffff irq 30 at device 6.0 on pci5 >> aacch1: <AAC RAID Channel> port 0xc800-0xc8ff mem >> 0xfccfe000-0xfccfefff irq 31 at device 6.1 on pci5 >> aac0: <Dell PERC 3/Di> 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: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 16 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 7 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> mem 0xf0000000-0xf7ffffff irq 30 at device 8.1 on pci4 aac0: <Dell PERC 3/Di> 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.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?A53A3AAB-C9B3-4A77-96EE-B987942FB385>