From owner-freebsd-questions@FreeBSD.ORG Thu Sep 23 16:10:45 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 0D86C16A4CE for ; Thu, 23 Sep 2004 16:10:45 +0000 (GMT) Received: from skoda.sockpuppet.org (skoda.sockpuppet.org [192.148.252.238]) by mx1.FreeBSD.org (Postfix) with SMTP id 5DCC543D2D for ; Thu, 23 Sep 2004 16:10:44 +0000 (GMT) (envelope-from kdulzo@sockpuppet.org) Received: (qmail 9234 invoked by uid 133); 23 Sep 2004 16:10:25 -0000 Date: Thu, 23 Sep 2004 12:10:25 -0400 From: kdulzo@skoda.sockpuppet.org To: Stefan Bethke Message-ID: <20040923161025.GA5507@skoda.sockpuppet.org> References: <20040922192034.GA25689@skoda.sockpuppet.org> <8C289822-0D66-11D9-95D2-000A95C893E4@lassitu.de> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <8C289822-0D66-11D9-95D2-000A95C893E4@lassitu.de> User-Agent: Mutt/1.3.25i cc: freebsd-questions@freebsd.org Subject: Re: 5.3-BETA5 PAE Panic/Problems X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Reply-To: kdulzo@sockpuppet.org List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Sep 2004 16:10:45 -0000 On Thu, Sep 23, 2004 at 03:43:27PM +0200, Stefan Bethke wrote: > Am 22.09.2004 um 21:20 schrieb kdulzo@skoda.sockpuppet.org: > > > I've been searching around for what I might be doing incorrectly, but > >seem to have come to a dead stop in setting up a HP Proliant DL380G3 > >machine with a PAE enabled 5.3-BETA kernel. I've tried BETAS 3,4, and > >5 > >with no luck. The default PAE configuration file causes the problem > >indicated in the log below. FOO is a copy of PAE config with KDB, DDB, > >and KVA_PAGES=512. Am I incorrect in assuming this should work on 5.3? > > You might want to try to limit the kmem size, if you haven't done so > already: > > options VM_KMEM_SIZE_MAX=419430400 #400MB > > (Kris Kennaways suggestion.) > Thanks for the suggestion, but it leads to the exact same result. Any suggestions for debugging this furthur? -Kevin