From owner-freebsd-current@FreeBSD.ORG Sat Nov 10 16:07:51 2007 Return-Path: Delivered-To: freebsd-current@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 8010816A419 for ; Sat, 10 Nov 2007 16:07:51 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from smtp.utwente.nl (unknown [IPv6:2001:610:1908:1000:204:23ff:feb5:7e66]) by mx1.freebsd.org (Postfix) with ESMTP id EC3E613C4B2 for ; Sat, 10 Nov 2007 16:07:50 +0000 (UTC) (envelope-from pieter@degoeje.nl) Received: from lux.student.utwente.nl (lux.student.utwente.nl [130.89.170.81]) by smtp.utwente.nl (8.12.10/SuSE Linux 0.7) with ESMTP id lAAG7OUx015180; Sat, 10 Nov 2007 17:07:24 +0100 From: Pieter de Goeje To: Kostik Belousov Date: Sat, 10 Nov 2007 17:07:23 +0100 User-Agent: KMail/1.9.7 References: <200710131857.46963.pieter@degoeje.nl> <200711091304.44766.pieter@degoeje.nl> <20071109122628.GF37471@deviant.kiev.zoral.com.ua> In-Reply-To: <20071109122628.GF37471@deviant.kiev.zoral.com.ua> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-15" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200711101707.23910.pieter@degoeje.nl> X-UTwente-MailScanner-Information: Scanned by MailScanner. Contact helpdesk@ITBE.utwente.nl for more information. X-UTwente-MailScanner: Found to be clean X-UTwente-MailScanner-From: pieter@degoeje.nl X-Spam-Status: No Cc: Rolf Witt , freebsd-current@freebsd.org, avleeuwen@piwebs.com, Ken Smith , Tim Bishop Subject: Re: panic: ffs_blkfree: freeing free block 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: Sat, 10 Nov 2007 16:07:51 -0000 On Friday 09 November 2007, Kostik Belousov wrote: > On Fri, Nov 09, 2007 at 01:04:44PM +0100, Pieter de Goeje wrote: > > > Is anyone who had been able to trigger this panic still having problems > > > with recent kernels (and soft updates turned on)? I've checked with a > > > few people who had been experiencing the panic and they can no longer > > > trigger it. > > > > > > It's at least a tiny bit possible some of the VM fixes that have gone > > > in addressed this problem. We'd like to find out if anyone can still > > > trigger this. > > > > I can no longer reproduce it any more. > > Could anybody who was able to trigger the panic with relative ease, do > the binary search for the dates that > A. started the problem > B. eliminated it > > There is uneasy feeling for the bug that did such appearance and still > not tracked. Doing a binary search now. Might take some time though. Pieter de Goeje