From owner-freebsd-current@FreeBSD.ORG Thu Jun 16 17:42:05 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 A066516A41C; Thu, 16 Jun 2005 17:42:05 +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 7380643D55; Thu, 16 Jun 2005 17:42:05 +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 1D8EE46B45; Thu, 16 Jun 2005 13:42:05 -0400 (EDT) Date: Thu, 16 Jun 2005 18:44:18 +0100 (BST) From: Robert Watson X-X-Sender: robert@fledge.watson.org To: "Stephane E. Potvin" In-Reply-To: <42B1B784.8010405@videotron.ca> Message-ID: <20050616184127.L27625@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> 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: Thu, 16 Jun 2005 17:42:05 -0000 On Thu, 16 Jun 2005, Stephane E. Potvin wrote: >>> I did a binary search to find the offending commit. Reverting the changes >>> to kern_malloc.c and malloc.h locally did fix the problem. That's what >>> I'm >>> currently using to type this message. I also had to revert the changes to >>> vmstat to make the world compile. >>> >>> Using head sources from yesterday (Jun 15) exhibit the same problem >>> unfortunately. >> >> Hmm.. It looks like Alan Cox just committed the attached patch to >> uma_int.h to modify UMA_BOOT_PAGES following a report of a panic at a >> similar point in the boot process. Could you try updating to the latest >> uma_int.h or trying the patch below to see if it makes a difference? >> > > Great :) It did the trick. The laptop is happily booting with the new > allocator now. Thanks a lot to you and Alan Cox. Looks like what basically happened is this these kern_malloc.c changes increase the memory burden on UMA as statistics structures for malloc types now get allocated from UMA. It looks like, from your dmesg, you have a fair number of modules loaded, so the storage for the statistics comes out of the early UMA page pool, whereas before it came out of BSS. We'll see if further tuning is required or not with large numbers of modules. The thing that surprised me, though, is the unclean failure mode. The other report saw a clean panic which presumably made debugging it much easier... Robert N M Watson