From owner-freebsd-current@FreeBSD.ORG Thu Jan 8 00:26:29 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 52B6116A4CE; Thu, 8 Jan 2004 00:26:29 -0800 (PST) Received: from cs.rice.edu (cs.rice.edu [128.42.1.30]) by mx1.FreeBSD.org (Postfix) with ESMTP id 48DDB43D1D; Thu, 8 Jan 2004 00:26:28 -0800 (PST) (envelope-from alc@cs.rice.edu) Received: from localhost (localhost [127.0.0.1]) by cs.rice.edu (Postfix) with ESMTP id C87D34AA58; Thu, 8 Jan 2004 02:26:27 -0600 (CST) Received: from cs.rice.edu ([127.0.0.1]) by localhost (cs.rice.edu [127.0.0.1]) (amavisd-new, port 10024) with LMTP id 18495-02-29; Thu, 8 Jan 2004 02:26:26 -0600 (CST) Received: by cs.rice.edu (Postfix, from userid 19572) id 149894AA66; Thu, 8 Jan 2004 02:26:26 -0600 (CST) Date: Thu, 8 Jan 2004 02:26:25 -0600 From: Alan Cox To: Yu-Shun Wang Message-ID: <20040108082625.GK7891@cs.rice.edu> References: <200312220101.hBM11WgL071526@repoman.freebsd.org> <3FFCA854.7040707@isi.edu> <20040108053827.GJ7891@cs.rice.edu> <3FFCFBF8.3050502@isi.edu> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <3FFCFBF8.3050502@isi.edu> User-Agent: Mutt/1.3.28i X-Virus-Scanned: by amavis-20030616-p5 at rice.edu cc: Alan Cox cc: current@freebsd.org Subject: Re: Immediate reboot after memory probe 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: Thu, 08 Jan 2004 08:26:29 -0000 On Wed, Jan 07, 2004 at 10:43:04PM -0800, Yu-Shun Wang wrote: > ... > Just to clarify, you meant changing the value directly > in sys/vm/uma_int.h, or is it something I can set as > some tunables or hints? You'll have to modify the #define in sys/vm/uma_int.h. > Hmm, now that you mentioned, it's a bit much. The previous > sys admin (just graduated & left) set those up, they are now > under my care. :-) > AFAIK, we've been running with these modules and tracking > current for quite a while without this problem. I am > wondering what changed; or maybe we've been close to > the edage and were just lucky? Is there a way to find out? There is nothing really wrong with your configuration. It just caused more of a certain object type to be allocated during early initialization than I anticipated. > Thanks again, I'll let you know if it works. You are welcome. Alan