From owner-freebsd-stable@FreeBSD.ORG Fri Dec 10 15:34:33 2004 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 0A9B016A4CE for ; Fri, 10 Dec 2004 15:34:33 +0000 (GMT) Received: from pooker.samsco.org (pooker.samsco.org [168.103.85.57]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9CE1243D46 for ; Fri, 10 Dec 2004 15:34:32 +0000 (GMT) (envelope-from scottl@freebsd.org) Received: from pooker.samsco.org (scottl@localhost [127.0.0.1]) by pooker.samsco.org (8.12.11/8.12.10) with ESMTP id iBAFappk026153; Fri, 10 Dec 2004 08:36:51 -0700 (MST) (envelope-from scottl@freebsd.org) Received: from localhost (scottl@localhost)iBAFaoV2026150; Fri, 10 Dec 2004 08:36:51 -0700 (MST) (envelope-from scottl@freebsd.org) X-Authentication-Warning: pooker.samsco.org: scottl owned process doing -bs Date: Fri, 10 Dec 2004 08:36:50 -0700 (MST) From: Scott Long Sender: scottl@pooker.samsco.org To: L G In-Reply-To: <9a1d931704121002183d3b2886@mail.gmail.com> Message-ID: <20041210083453.W398@pooker.samsco.org> References: <9a1d931704121002183d3b2886@mail.gmail.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII X-Spam-Status: No, hits=0.0 required=3.8 tests=none autolearn=no version=2.63 X-Spam-Checker-Version: SpamAssassin 2.63 (2004-01-11) on pooker.samsco.org cc: freebsd-stable@freebsd.org Subject: Re: Perc 4e/di amr driver 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: Fri, 10 Dec 2004 15:34:33 -0000 On Fri, 10 Dec 2004, L G wrote: > Hi, > Im installing 5.3 amd64 on Dell Poweredge servers 2800 and 2850. All > machines have 4 to 8gb of ram and Perc 4e/di hardware Raid controller. > The install does not boot completely because of the amr driver for the > Perc 4e/di not recognising 4gb+. To solve this I specify hw.physmem=4G > at boot time. The system then recognises 3.3gb of the ram. > To solve the issue of the amr driver i took the driver source from > 6.0-CURRENT kernel source, replacing the driver in the 5.3 kernel > source with it and compiling a new kernel. This worked and now all > system ram is recognised. > My question is,as these servers will be production servers under a > heavy load a lot of the time,will this new driver be stable enough to > use or is it a risk. > Thanks. The same changes that you grabbed from 6-CURRENT were made to 5-STABLE a few days ago, so you can just go ahead and update your whole system. 5.3-RELEASE has other bugs in >4GB handling that I've also fixed in 5-STABLE, and the AMR fixes rely on these fixes. But to answer your question, the driver is very stable under load now. Scott