From owner-freebsd-current@FreeBSD.ORG Thu May 1 17:08:12 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 906B037B401 for ; Thu, 1 May 2003 17:08:12 -0700 (PDT) Received: from pcat.heimat.gr.jp (catv-129-243.tees.ne.jp [202.216.129.243]) by mx1.FreeBSD.org (Postfix) with ESMTP id B54F543FA3 for ; Thu, 1 May 2003 17:08:08 -0700 (PDT) (envelope-from nakaji@tutrp.tut.ac.jp) Received: from xa12.heimat.gr.jp (xa12.heimat.gr.jp [202.216.136.35]) by pcat.heimat.gr.jp (8.12.9/8.12.9) with ESMTP id h42085tV074946 for ; Fri, 2 May 2003 09:08:05 +0900 (JST) (envelope-from nakaji@tutrp.tut.ac.jp) Sender: nakaji@xa12.heimat.gr.jp To: freebsd-current@freebsd.org References: <20030501135011.GA568@wombat.fafoe> From: NAKAJI Hiroyuki In-Reply-To: <20030501135011.GA568@wombat.fafoe> (Stefan Farfeleder's message of "Thu, 1 May 2003 15:50:11 +0200") MIME-Version: 1.0 (generated by SEMI 1.14.5 - "Awara-Onsen") Content-Type: text/plain; charset=US-ASCII Date: Fri, 02 May 2003 09:08:03 +0900 Message-ID: <86r87ixlb0.fsf@xa12.heimat.gr.jp> User-Agent: T-gnus/6.15.19 (based on Oort Gnus v0.19) SEMI/1.14.5 (Awara-Onsen) FLIM/1.14.5 (Demachiyanagi) APEL/10.4 Emacs/21.3 (i386--freebsd) MULE/5.0 (SAKAKI) X-Virus-Scanned: by AMaViS-perl11-milter (http://amavis.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:08:12 -0000 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. -- NAKAJI Hiroyuki