Date: Fri, 2 May 2003 13:43:34 -0700 (PDT) From: Don Lewis <truckman@FreeBSD.org> To: marcus@marcuscom.com Cc: current@FreeBSD.org Subject: Re: More on the blkfree panic Message-ID: <200305022043.h42KhYM7016128@gw.catspoiler.org> In-Reply-To: <1051903332.568.37.camel@gyros>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?200305022043.h42KhYM7016128>