From owner-freebsd-current@FreeBSD.ORG Fri Mar 5 07:52:25 2004 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 75F2916A4CE for ; Fri, 5 Mar 2004 07:52:25 -0800 (PST) Received: from oahu.WURLDLINK.NET (oahu.wurldlink.net [66.193.144.7]) by mx1.FreeBSD.org (Postfix) with ESMTP id E5B0243D31 for ; Fri, 5 Mar 2004 07:52:24 -0800 (PST) (envelope-from vince@oahu.WURLDLINK.NET) Received: from oahu.WURLDLINK.NET (vince@localhost.WURLDLINK.NET [127.0.0.1]) by oahu.WURLDLINK.NET (8.12.9/8.12.9) with ESMTP id i25FpVqQ034456; Fri, 5 Mar 2004 05:51:46 -1000 (HST) Received: from localhost (vince@localhost)i25FpUY8034453; Fri, 5 Mar 2004 05:51:30 -1000 (HST) Date: Fri, 5 Mar 2004 05:51:30 -1000 (HST) From: Vincent Poy To: Andrew Gallatin In-Reply-To: <16456.34812.997224.366345@grasshopper.cs.duke.edu> Message-ID: <20040305054923.I8264-100000@oahu.WURLDLINK.NET> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII cc: current@freebsd.org Subject: Re: -CURRENT kernel panic X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 05 Mar 2004 15:52:25 -0000 On Fri, 5 Mar 2004, Andrew Gallatin wrote: > Vincent Poy writes: > > > real memory = 2147360768 (2047 MB) > > > avail memory = 2095669248 (1998 MB) > > > > > > > Just add vm.kmem_size=VALUE to /boot/loader.conf. That way you don't > > > > need to rebuild a kernel. I run with vm.kmem_size=429391872 > > > > Just tried what you mentioned and the kernel panics at the same spot above > > on vm_kern.c. I'm glad I cloned my drives on a nightly basis so I booted > > What is the panic message? No idea what it was but it panics as soon as it gets to the memory portion at the bootup. I guess it's the same panic one gets if one sets maxusers=512 in the kernel and tries this. > BTW, that's why hardcoding is not good, and why the defaults should > work.. Yeah but the problem is the defaults don't work. It used to work fine on my September 23, 2003 -CURRENT but when I went with February 28, 2004 and later -CURRENT, they all had this problem. Cheers, Vince - vince@WURLDLINK.NET - Vice President ________ __ ____ Unix Networking Operations - FreeBSD-Real Unix for Free / / / / | / |[__ ] WurldLink Corporation / / / / | / | __] ] San Francisco - Honolulu - Hong Kong / / / / / |/ / | __] ] HongKong Stars/Gravis UltraSound Mailing Lists Admin /_/_/_/_/|___/|_|[____] Almighty1@IRC - oahu.DAL.NET Hawaii's DALnet IRC Network Server Admin