From owner-freebsd-current  Fri May 31 17:12:28 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.5/8.7.3) id RAA25389
          for current-outgoing; Fri, 31 May 1996 17:12:28 -0700 (PDT)
Received: from Root.COM (implode.Root.COM [198.145.90.17])
          by freefall.freebsd.org (8.7.5/8.7.3) with ESMTP id RAA25375;
          Fri, 31 May 1996 17:12:26 -0700 (PDT)
Received: from localhost (localhost [127.0.0.1]) by Root.COM (8.7.5/8.6.5) with SMTP id RAA24111; Fri, 31 May 1996 17:12:24 -0700 (PDT)
Message-Id: <199606010012.RAA24111@Root.COM>
X-Authentication-Warning: implode.Root.COM: Host localhost [127.0.0.1] didn't use HELO protocol
To: Stephen Hocking <sysseh@devetir.qld.gov.au>
cc: dyson@freebsd.org, current@freebsd.org
Subject: Re: Latest VM fixes are holding up 
In-reply-to: Your message of "Fri, 31 May 1996 16:15:14 +1000."
             <199605310615.GAA04339@netfl15a.devetir.qld.gov.au> 
From: David Greenman <davidg@Root.COM>
Reply-To: davidg@Root.COM
Date: Fri, 31 May 1996 17:12:23 -0700
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

>	They're holdng up fairly well here too, the only crashes I'm seeing
>(which are entirely reproducible on one machine by doing "make hierarchy") are 
>of the "Panic: cleaned vnode isn't" type. I'm seeing a couple of the a day. If 
>only I had the space to create & install a completely debuggable kernel I'd do 
>it. Now, when is Terry's FS stuff going in?

   Terry apparantly has a kludge for the "free vnode isn't" panic, but the
problem you mention above about "cleaned vnode isn't" is a different problem
altogether. I've never seen this occur here or on any machines I'm responsible
for, so I suspect that the problem is isolated/related to specific code that
you're using that I'm not.

-DG

David Greenman
Core-team/Principal Architect, The FreeBSD Project