From owner-freebsd-current@FreeBSD.ORG Sun Apr 27 23:27:14 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 E265C37B401 for ; Sun, 27 Apr 2003 23:27:14 -0700 (PDT) Received: from smtpout.mac.com (smtpout.mac.com [17.250.248.86]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7058143F3F for ; Sun, 27 Apr 2003 23:27:14 -0700 (PDT) (envelope-from leimy2k@mac.com) Received: from mac.com (smtpin07-en2 [10.13.10.152]) by smtpout.mac.com (Xserve/MantshX 2.0) with ESMTP id h3S6RB1F009842 for ; Sun, 27 Apr 2003 23:27:14 -0700 (PDT) Received: from mac.com (adsl-156-162-249.jan.bellsouth.net [66.156.162.249]) (authenticated bits=0) by mac.com (Xserve/MantshX 2.0) with ESMTP id h3S35QA8020009; Sun, 27 Apr 2003 20:05:27 -0700 (PDT) Date: Sun, 27 Apr 2003 22:08:37 -0500 Content-Type: text/plain; charset=US-ASCII; format=flowed Mime-Version: 1.0 (Apple Message framework v552) To: Don Lewis From: David Leimbach In-Reply-To: <200304280209.h3S29XM7002399@gw.catspoiler.org> Message-Id: Content-Transfer-Encoding: 7bit X-Mailer: Apple Mail (2.552) cc: freebsd-current@FreeBSD.org cc: larse@ISI.EDU cc: flo@einfachsms.de Subject: Re: Kernel panic during portupdrade [ffs_blkfree: freeing free block] 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: Mon, 28 Apr 2003 06:27:15 -0000 Mine was fine yesterday too. Something from this morning is bad. It only seems to happen when I do filesystem intense stuff and its always in a double block free. Dave On Sunday, April 27, 2003, at 09:09 PM, Don Lewis wrote: > On 27 Apr, Lars Eggert wrote: >> David Leimbach wrote: >>> >>> On Sunday, April 27, 2003, at 05:27 PM, Lars Eggert wrote: >>> >>>> Hi, >>>> >>>> I see somthing similar and have a core dump. Below is a backtrace. >>>> This did not happen with a 4/17 kernel, by the way. Please let me >>>> know >>>> if there is any other >>> >>> ^^^^^ >>> Did you mean 4/27? >> >> Nope. It did not happen with a 4/17 kernel but does happen with a 4/27 >> kernel, so something in between must have broken it. > > I updated and rebuilt on 4/16, 4/18, 4/19, 4/22, 4/23, and 4/24 and > didn't have any trouble during that time even though that machine was > getting a lot of use. I'm currently running a version of current from > 4/26 and haven't seen any filesystem panics, though the system hasn't > gotten much exercise since that update.