From owner-freebsd-stable@FreeBSD.ORG Fri Dec 10 10:18:43 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 125A316A4CE for ; Fri, 10 Dec 2004 10:18:43 +0000 (GMT) Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.193]) by mx1.FreeBSD.org (Postfix) with ESMTP id B469E43D5A for ; Fri, 10 Dec 2004 10:18:42 +0000 (GMT) (envelope-from vamosl@gmail.com) Received: by rproxy.gmail.com with SMTP id z35so409372rne for ; Fri, 10 Dec 2004 02:18:42 -0800 (PST) DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=beta; d=gmail.com; h=received:message-id:date:from:reply-to:to:subject:mime-version:content-type:content-transfer-encoding; b=i5/eYmCJfX/5qqI+cBXWIYzvz7lcTn9y4dQBE2oQCIknZgMM66JAyED3LH+0bvmpJL4e1rU4CcPywG04ZXvdTwlZGgE1hTGRZ5XDG5+68LE3VuqvEfjWT1DorMX6jU3xQeF6OSsqBsIOoASR9yMnR5vlj+SYT6uOakRTEnynaBI= Received: by 10.38.104.13 with SMTP id b13mr385674rnc; Fri, 10 Dec 2004 02:18:41 -0800 (PST) Received: by 10.38.11.31 with HTTP; Fri, 10 Dec 2004 02:18:41 -0800 (PST) Message-ID: <9a1d931704121002183d3b2886@mail.gmail.com> Date: Fri, 10 Dec 2004 10:18:41 +0000 From: L G To: freebsd-stable@freebsd.org Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Subject: Perc 4e/di amr driver X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: L G 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 10:18:43 -0000 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.