From owner-freebsd-current@FreeBSD.ORG  Fri May  2 13:43:42 2003
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
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 AD22A37B401
	for <current@FreeBSD.org>; Fri,  2 May 2003 13:43:42 -0700 (PDT)
Received: from gw.catspoiler.org (217-ip-163.nccn.net [209.79.217.163])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 0979B43FD7
	for <current@FreeBSD.org>; Fri,  2 May 2003 13:43:42 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Received: from FreeBSD.org (scratch.catspoiler.org [192.168.101.3])
	by gw.catspoiler.org (8.12.9/8.12.9) with ESMTP id h42KhYM7016128;
	Fri, 2 May 2003 13:43:38 -0700 (PDT)
	(envelope-from truckman@FreeBSD.org)
Message-Id: <200305022043.h42KhYM7016128@gw.catspoiler.org>
Date: Fri, 2 May 2003 13:43:34 -0700 (PDT)
From: Don Lewis <truckman@FreeBSD.org>
To: marcus@marcuscom.com
In-Reply-To: <1051903332.568.37.camel@gyros>
MIME-Version: 1.0
Content-Type: TEXT/plain; charset=us-ascii
cc: current@FreeBSD.org
Subject: Re: More on the blkfree panic
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Fri, 02 May 2003 20:43:43 -0000

On  2 May, Joe Marcus Clarke wrote:
> This panic started happening to me after I cvsup'd and rebuilt
> yesterday.  Prior to that I never had the problem with a -CURRENT from
> 04/26 (using the same steps listed below).  Now I can reliably reproduce
> the crash on:
> 
> FreeBSD bulgogi.cisco.com 5.0-CURRENT FreeBSD 5.0-CURRENT #2: Fri May 2
> 14:08:06 EDT 2003   
> marcus@bulgogi.cisco.com:/usr/obj/usr/src/sys/BULGOGI  i386

I haven't seen it on my 4/26 machine, though I haven't done anything
disc intensive (other than the daily cron jobs) since then. The reports
of this problem started showing up on 4/27, so I went hunting for
commits during the likely window using cvs diff.  There were a number of
vm locking changes made during that time, including some changes to
vfs_bio.c.  That's about as close as anything came to touching the
filesystem code.