Date: Thu, 8 Jan 2004 02:26:25 -0600 From: Alan Cox <alc@cs.rice.edu> To: Yu-Shun Wang <yushunwa@ISI.EDU> Cc: current@freebsd.org Subject: Re: Immediate reboot after memory probe Message-ID: <20040108082625.GK7891@cs.rice.edu> In-Reply-To: <3FFCFBF8.3050502@isi.edu> References: <200312220101.hBM11WgL071526@repoman.freebsd.org> <3FFCA854.7040707@isi.edu> <20040108053827.GJ7891@cs.rice.edu> <3FFCFBF8.3050502@isi.edu>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20040108082625.GK7891>