From owner-freebsd-current@FreeBSD.ORG Thu May 1 23:05:37 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 EA7F737B401 for ; Thu, 1 May 2003 23:05:37 -0700 (PDT) Received: from rutger.owt.com (rutger.owt.com [204.118.6.16]) by mx1.FreeBSD.org (Postfix) with ESMTP id 4E13243F85 for ; Thu, 1 May 2003 23:05:37 -0700 (PDT) (envelope-from kstewart@owt.com) Received: from topaz-out (owt-207-41-94-233.owt.com [207.41.94.233]) by rutger.owt.com (8.11.6p2/8.9.3) with ESMTP id h4265VV09273; Thu, 1 May 2003 23:05:31 -0700 From: Kent Stewart To: "M. Warner Losh" , marcel@xcllnt.net Date: Thu, 1 May 2003 23:05:31 -0700 User-Agent: KMail/1.5.1 References: <20030502035426.GA65366@athlon.pn.xcllnt.net> <20030501.233220.08332249.imp@bsdimp.com> In-Reply-To: <20030501.233220.08332249.imp@bsdimp.com> MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <200305012305.31528.kstewart@owt.com> cc: current@freebsd.org Subject: Re: another one: panic: 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: Fri, 02 May 2003 06:05:38 -0000 On Thursday 01 May 2003 10:32 pm, M. Warner Losh wrote: > In message: <20030502035426.GA65366@athlon.pn.xcllnt.net> > > Marcel Moolenaar writes: > : login: dev = da0p7, block = 600688, fs = /q > : panic: ffs_blkfree: freeing free block > > I get this all the time on my laptop, and have on and off, for the > past two weeks. I posted a traceback, and a me too on a couple of > other tracebacks that matched mine. This is the first bug to get me > really annoyed in quite some time because it is a random killer. > All I have to do is start something like KDE that seems to leave sector as inactive memory. You can start another process such as update the locate database. You can watch inactive memory start to be freed up in top and boom!!. One time, I did 2 locate updates and nothing happened. So, I did a startx and boom!. The block is always the same 567360. On my system it is on ad0s3e (/var). It is random as far as when it happens but you can make it happen in 3 or 4 minutes. Kent -- Kent Stewart Richland, WA http://users.owt.com/kstewart/index.html