From owner-freebsd-current@FreeBSD.ORG Fri Jun 17 19:33:25 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 AD23616A41C; Fri, 17 Jun 2005 19:33:25 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (trang.nuxi.com [66.93.134.19]) by mx1.FreeBSD.org (Postfix) with ESMTP id 798FD43D53; Fri, 17 Jun 2005 19:33:25 +0000 (GMT) (envelope-from obrien@NUXI.com) Received: from dragon.NUXI.org (obrien@localhost [127.0.0.1]) by dragon.NUXI.org (8.13.4/8.13.4) with ESMTP id j5HJXI8c015723; Fri, 17 Jun 2005 12:33:18 -0700 (PDT) (envelope-from obrien@dragon.NUXI.org) Received: (from obrien@localhost) by dragon.NUXI.org (8.13.4/8.13.1/Submit) id j5HJXH4s015722; Fri, 17 Jun 2005 12:33:17 -0700 (PDT) (envelope-from obrien) Date: Fri, 17 Jun 2005 12:33:17 -0700 From: "David O'Brien" To: Robert Watson Message-ID: <20050617193317.GA15570@dragon.NUXI.org> Mail-Followup-To: obrien@freebsd.org, Robert Watson , Eric Anderson , alc@freebsd.org, freebsd-current@freebsd.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> <20050617123954.W56734@fledge.watson.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20050617123954.W56734@fledge.watson.org> X-Operating-System: FreeBSD 6.0-CURRENT Organization: The NUXI BSD Group X-Pgp-Rsa-Fingerprint: B7 4D 3E E9 11 39 5F A3 90 76 5D 69 58 D9 98 7A X-Pgp-Rsa-Keyid: 1024/34F9F9D5 User-Agent: Mutt/1.5.9i Cc: alc@FreeBSD.org, freebsd-current@FreeBSD.org, Eric Anderson Subject: Re: Reboot while booting with new per-CPU allocator X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list Reply-To: obrien@FreeBSD.org 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 19:33:25 -0000 On Fri, Jun 17, 2005 at 12:40:50PM +0100, 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. The sys/dev/atkbdc commit is what pushed me over the limit, not the malloc changes. I am loading 15 modules. -- -- David (obrien@FreeBSD.org)