From owner-freebsd-current@FreeBSD.ORG Fri Jun 24 20:56:28 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 DCDCF16A41C for ; Fri, 24 Jun 2005 20:56:28 +0000 (GMT) (envelope-from silby@silby.com) Received: from relay01.pair.com (relay01.pair.com [209.68.5.15]) by mx1.FreeBSD.org (Postfix) with SMTP id 7BCD743D4C for ; Fri, 24 Jun 2005 20:56:28 +0000 (GMT) (envelope-from silby@silby.com) Received: (qmail 61730 invoked from network); 24 Jun 2005 20:56:26 -0000 Received: from unknown (HELO localhost) (unknown) by unknown with SMTP; 24 Jun 2005 20:56:26 -0000 X-pair-Authenticated: 209.68.2.70 Date: Fri, 24 Jun 2005 15:56:11 -0500 (CDT) From: Mike Silbersack To: Thierry Herbelot In-Reply-To: <200506242237.30270.thierry@herbelot.com> Message-ID: <20050624155218.D83036@odysseus.silby.com> References: <20050624145923.P83036@odysseus.silby.com> <20050624202505.GA17245@peter.osted.lan> <200506242237.30270.thierry@herbelot.com> MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII; format=flowed Cc: freebsd-current@freebsd.org Subject: Re: new panics 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, 24 Jun 2005 20:56:29 -0000 On Fri, 24 Jun 2005, Thierry Herbelot wrote: > I did not get the panic within minutes of testing (I ususually first sync the > sources from a local CVS mirror, then build the tree). The panic occurred > during the "buildworld" phase. > > TfH That makes some sense, because we may not be getting around to the modified memory until we hit some heavy memory usage. Also, one backtrace showed the panic happening when uma_reclaim was called from the vm pageout daemon. Sounds like I should throw something in to (optionally) call uma_reclaim on a regular basis so that we might catch this more quickly. Mike "Silby" Silbersack