From owner-freebsd-stable@FreeBSD.ORG Wed Mar 9 00:58:02 2005 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9ADA416A4CE; Wed, 9 Mar 2005 00:58:02 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id EBD1443D49; Wed, 9 Mar 2005 00:57:58 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.11] (junior-wifi.samsco.home [192.168.254.11]) (authenticated bits=0) by pooker.samsco.org (8.13.1/8.13.1) with ESMTP id j290x4SL076761; Tue, 8 Mar 2005 17:59:05 -0700 (MST) (envelope-from scottl@samsco.org) Message-ID: <422E4986.6080409@samsco.org> Date: Tue, 08 Mar 2005 17:55:34 -0700 From: Scott Long User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.5) Gecko/20050218 X-Accept-Language: en-us, en MIME-Version: 1.0 To: David Sze References: <4224F19C.2090207@rackspace.com> <6.2.1.2.2.20050301234017.03e93e68@pop3.tellurian.com> <4225CCE4.3080304@rackspace.com> <20050308235853.GA81150@mail.distrust.net> In-Reply-To: <20050308235853.GA81150@mail.distrust.net> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-2.8 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.0.2 X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on pooker.samsco.org cc: Art Mason cc: scottl@freebsd.org cc: freebsd-stable@freebsd.org Subject: Re: Can FreeBSD be installed on DellPowerEdge2800 ? X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 09 Mar 2005 00:58:02 -0000 David Sze wrote: > On Wed, Mar 02, 2005 at 08:25:40AM -0600, Art Mason wrote: > >>Vinny Abello wrote: >> >>>At 05:50 PM 3/1/2005, Art Mason wrote: >>> >>>>Indeed, just installed on a customer's server last night, and I build >>>>SMP support into the GENERIC kernel this morning. Only issues I >>>>encountered has to do w/ recognizing the full 4GB of RAM, but this >>>>apparently has some compatibility issues w/ the amr driver. >>>>As per Holger's comments about disabling USB in BIOS, this is a good >>>>suggestion, since the DRAC apparently causes some IRQ issues w/ the >>>>PS/2 keyboard controller, or something along those lines. Regardless, >>>>these 2850 boxes are stupid fast, and I'm looking forward to >>>>benchmarking 5.3 on them. >>> >>> >>>FYI, the architecture of the 2850 (assuming it is similar to your 2800) >>>requires that you enable PAE support in your kernel of whatever OS you >>>run to address the full 4GB of RAM. This is due in some part because of >>>the memory mapping that was done for the PCI express bus and/or onboard >>>Perc controller (per Dell tech support). We've run into this with all of >>>our 2850's with various OS's and enabling PAE (per Dell's advice) fixes it. >> >> >>Yeah, I cam across that on some mailing list archives, but saw some >>additional references that this can cause issues with the amr driver. >>Have you experienced any instability issues with the amr driver and PAE >>enabled? If not, then I'll give this a shot on one of our lab boxes for >>testing. Thanks for the suggestion, BTW. > > > > On my 2850 the upper 1GB of RAM cannot be addressed without PAE support > in the kernel. However, amr in 4.11-RELEASE does indeed seem to have > trouble with PAE. The result being that with the option in the kernel, > the root device (ufs:/dev/amrd0s1a) cannot be found. > > I backported scottl's amr PAE fixes from RELENG_5; the diffs applied > cleanly (with offsets). I'm happy to report that my 2850 can now > address its full 4GB and see its amr volumes. > > The diff against 4.11-RELEASE is attached, hopefully someone will be > willing to commit it to RELENG_4. > I don't have the cycles to watch after RELENG_4, so I'll have to take your word that this works. What date is this patch against? I committed some follow-up fixes last week that are required for management apps to work (and yes, LSI is getting ready to support FreeBSD with management apps). Scott