From owner-freebsd-current@FreeBSD.ORG Fri Jun 17 11:38:31 2005 Return-Path: X-Original-To: freebsd-current@freebsd.org 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 479E016A41C; Fri, 17 Jun 2005 11:38:31 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from cyrus.watson.org (cyrus.watson.org [204.156.12.53]) by mx1.FreeBSD.org (Postfix) with ESMTP id 1A53843D1D; Fri, 17 Jun 2005 11:38:31 +0000 (GMT) (envelope-from rwatson@FreeBSD.org) Received: from fledge.watson.org (fledge.watson.org [204.156.12.50]) by cyrus.watson.org (Postfix) with ESMTP id A6F6846B09; Fri, 17 Jun 2005 07:38:30 -0400 (EDT) Date: Fri, 17 Jun 2005 12:40:50 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: Eric Anderson In-Reply-To: <42B2B4C0.1030504@centtech.com> Message-ID: <20050617123954.W56734@fledge.watson.org> References: <42B18536.3080200@videotron.ca> <20050616151502.X27625@fledge.watson.org> <42B192D2.7000505@videotron.ca> <20050616181820.E27625@fledge.watson.org> <42B1B784.8010405@videotron.ca> <20050616184127.L27625@fledge.watson.org> <20050617110902.C56734@fledge.watson.org> <42B2B4C0.1030504@centtech.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: alc@freebsd.org, freebsd-current@freebsd.org Subject: Re: Reboot while booting with new per-CPU allocator X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 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, 17 Jun 2005 11:38:31 -0000 On Fri, 17 Jun 2005, Eric Anderson wrote: >> Interestingly, there's been a bunch of reports of this in the past few >> days, and there weren't immediately after the malloc commit. I wonder if >> some other recent change has increased the amount of UMA memory allocated >> early in the boot, increasing the level of reports... > > Increase UMA_BOOT_PAGES to prevent a crash during initialization. See > http://docs.FreeBSD.org/cgi/mid.cgi?42AD8270.8060906 for a detailed > description of the crash. Yeah, this is the fix, but I guess I'm wondering what caused a recent spate of problem reports -- was it a delayed response to the malloc change as people gradually upgraded, or some other recent kernel change that caused increase demand for memory. Robert N M Watson