From owner-freebsd-current@FreeBSD.ORG Wed Apr 30 12:52:32 2003 Return-Path: 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 C3B4637B429 for ; Wed, 30 Apr 2003 12:52:32 -0700 (PDT) Received: from bremen.shuttle.de (bremen.shuttle.de [194.95.249.251]) by mx1.FreeBSD.org (Postfix) with ESMTP id 6720143F85 for ; Wed, 30 Apr 2003 12:52:31 -0700 (PDT) (envelope-from schweikh@schweikhardt.net) Received: from bremen.shuttle.de (localhost [127.0.0.1]) by bremen.shuttle.de (Postfix) with ESMTP id 19A5817D7B for ; Wed, 30 Apr 2003 21:52:30 +0200 (CEST) Received: (from uucp@localhost)h3UJqTvH017937 for current@freebsd.org; Wed, 30 Apr 2003 21:52:29 +0200 Received: from hal9000.schweikhardt.net (localhost [127.0.0.1]) h3UJlgts020624 for ; Wed, 30 Apr 2003 21:47:42 +0200 (CEST) (envelope-from schweikh@hal9000.schweikhardt.net) Received: (from schweikh@localhost) by hal9000.schweikhardt.net (8.12.9/8.12.6/Submit) id h3UJlgDY020623 for current@freebsd.org; Wed, 30 Apr 2003 21:47:42 +0200 (CEST) Date: Wed, 30 Apr 2003 21:47:42 +0200 From: Jens Schweikhardt To: current@freebsd.org Message-ID: <20030430194742.GA20357@schweikhardt.net> References: <20030430174441.GA22732@node1.cluster.srrc.usda.gov> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <20030430174441.GA22732@node1.cluster.srrc.usda.gov> User-Agent: Mutt/1.4.1i Subject: Re: kernel crashes and portupgrade X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 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: Wed, 30 Apr 2003 19:52:33 -0000 On Wed, Apr 30, 2003 at 12:44:41PM -0500, Glenn Johnson wrote: # Does any one know if portupgrade has a problem or is it something in # -current that it is interacting with? I get the "panic: freeing free block" (that other people reported) during "make install" in a number of ports under /usr/ports on a freshly installed system. I'm not using portupgrade at all, so it is not portupgrade specific. It's rather something that portupgrade runs doing its job. Could be heavy disk I/O, lots of context switches or whatever. Regards, Jens -- Jens Schweikhardt http://www.schweikhardt.net/ SIGSIG -- signature too long (core dumped)