From owner-freebsd-current@FreeBSD.ORG Thu May 1 17:56:23 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 DD56B37B401 for ; Thu, 1 May 2003 17:56:23 -0700 (PDT) Received: from puffin.mail.pas.earthlink.net (puffin.mail.pas.earthlink.net [207.217.120.139]) by mx1.FreeBSD.org (Postfix) with ESMTP id F2CF743FA3 for ; Thu, 1 May 2003 17:56:22 -0700 (PDT) (envelope-from tlambert2@mindspring.com) Received: from pool0223.cvx40-bradley.dialup.earthlink.net ([216.244.42.223] helo=mindspring.com) by puffin.mail.pas.earthlink.net with asmtp (SSLv3:RC4-MD5:128) (Exim 3.33 #1) id 19BOqZ-0006Ca-00; Thu, 01 May 2003 17:56:19 -0700 Message-ID: <3EB1BF31.B96B7A3C@mindspring.com> Date: Thu, 01 May 2003 17:43:29 -0700 From: Terry Lambert X-Mailer: Mozilla 4.79 [en] (Win98; U) X-Accept-Language: en MIME-Version: 1.0 To: NAKAJI Hiroyuki References: <20030501135011.GA568@wombat.fafoe> <86r87ixlb0.fsf@xa12.heimat.gr.jp> Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: 7bit X-ELNK-Trace: b1a02af9316fbb217a47c185c03b154d40683398e744b8a4428c65e409a56b2b1702591ef81fd4f6a2d4e88014a4647c350badd9bab72f9c350badd9bab72f9c cc: freebsd-current@freebsd.org Subject: Re: panic: ffs_blkfree: freeing free frag 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: Fri, 02 May 2003 00:56:24 -0000 NAKAJI Hiroyuki wrote: > I got same panic on my FreeBSD/pc98 -CURRENT box. Under following > situation. > > 1. Building new kernel and running Emacs on another vty, or > 2. Running "portupgrade -a" and running Emacs on another vty > > In both cases, access to my ~/Mail, i.e. /home partition, is resulting > into panic. Fortunately my $HOME is not corrupted yet. :) > > Both kernels on Apr 28 2003 and May 1 2003 got the same panic, but the > kernel on Apr 12 2003 does not. Try my patch (posted previously). -- Terry