From owner-freebsd-current@FreeBSD.ORG Fri Jun 17 11:59:47 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 D1B9816A470; Fri, 17 Jun 2005 11:59:47 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from mh2.centtech.com (moat3.centtech.com [207.200.51.50]) by mx1.FreeBSD.org (Postfix) with ESMTP id 01BA543D4C; Fri, 17 Jun 2005 11:59:46 +0000 (GMT) (envelope-from anderson@centtech.com) Received: from [10.177.171.220] (neutrino.centtech.com [10.177.171.220]) by mh2.centtech.com (8.13.1/8.13.1) with ESMTP id j5HBxjEx007374; Fri, 17 Jun 2005 06:59:46 -0500 (CDT) (envelope-from anderson@centtech.com) Message-ID: <42B2BB31.7000809@centtech.com> Date: Fri, 17 Jun 2005 06:59:45 -0500 From: Eric Anderson User-Agent: Mozilla/5.0 (X11; U; FreeBSD i386; en-US; rv:1.7.8) Gecko/20050603 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Robert Watson 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> <20050617123954.W56734@fledge.watson.org> In-Reply-To: <20050617123954.W56734@fledge.watson.org> Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit Cc: 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:59:48 -0000 Robert Watson wrote: > > 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. For me, it was the recent lack of apathy - finally getting around to trying some combos for suspending my laptop, I noticed that having apic+smp in my kernel made me crash on boot. Maybe it's some of the modules that have changed - the ones that caused the problems for me were: snd_pcm snd_ich sound vkbd If those weren't loaded via loader.conf, I was fine. Maybe the change is inside one of those. As I've said before, I'm no coder, so take all that with a grain of salt - but hopefully it's helpful to someone. Eric -- ------------------------------------------------------------------------ Eric Anderson Sr. Systems Administrator Centaur Technology A lost ounce of gold may be found, a lost moment of time never. ------------------------------------------------------------------------