From owner-freebsd-stable@FreeBSD.ORG Mon Apr 3 06:41:18 2006 Return-Path: X-Original-To: freebsd-stable@FreeBSD.org 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 738B016A420; Mon, 3 Apr 2006 06:41:18 +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 DC88443D4C; Mon, 3 Apr 2006 06:41:17 +0000 (GMT) (envelope-from scottl@samsco.org) Received: from [192.168.254.14] (imini.samsco.home [192.168.254.14]) (authenticated bits=0) by pooker.samsco.org (8.13.4/8.13.4) with ESMTP id k336fErw036529; Mon, 3 Apr 2006 00:41:15 -0600 (MDT) (envelope-from scottl@samsco.org) Message-ID: <4430C38A.2010806@samsco.org> Date: Mon, 03 Apr 2006 00:41:14 -0600 From: Scott Long User-Agent: Mozilla/5.0 (Macintosh; U; PPC Mac OS X Mach-O; en-US; rv:1.7.7) Gecko/20050416 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Matthew Jacob References: <000001c656e0$d6da1f80$0201a8c0@win2k> <4430BD3B.9040802@samsco.org> <20060402232236.Q33976@ns1.feral.com> In-Reply-To: <20060402232236.Q33976@ns1.feral.com> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=-1.4 required=3.8 tests=ALL_TRUSTED autolearn=failed version=3.1.0 X-Spam-Checker-Version: SpamAssassin 3.1.0 (2005-09-13) on pooker.samsco.org Cc: 'Ganbold' , freebsd-stable@FreeBSD.org, mjacob@FreeBSD.org, 'Kris Kennaway' Subject: Re: contigmalloc() lameness (Re: boot problem in HP Proliant ML370 G4) X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 03 Apr 2006 06:41:18 -0000 Matthew Jacob wrote: > > > On Mon, 3 Apr 2006, Scott Long wrote: > >> Matthew Jacob wrote: >> >>> I must have missed something here. What's the problem that causes >>> contigmalloc to be called here? If this is to do with > 4GB of >>> memory, that >>> was fixed in -CURRENT over a month ago. >>> >> >> He's using 6.0-RELEASE. >> > > A reason to allow an MFC ? :-) > I'm fully intending for it to get MFC'd, I just want a chance to test it in our FC environment first so that any problems don't become emergencies. Scott