From owner-freebsd-bugs  Fri Jul  2 11:26: 2 1999
Delivered-To: freebsd-bugs@freebsd.org
Received: from turtle.franz.com (turtle.franz.com [192.132.95.23])
	by hub.freebsd.org (Postfix) with ESMTP
	id AB5B714CE0; Fri,  2 Jul 1999 11:26:00 -0700 (PDT)
	(envelope-from dancy@franz.com)
Received: from ultra.franz.com (ultra [192.132.95.147])
	by turtle.franz.com (8.9.1a/8.9.0) with SMTP id LAA26037;
	Fri, 2 Jul 1999 11:26:00 -0700
Received: from ultra by ultra.franz.com (SMI-8.6/FI-2.0)
	id LAA12917; Fri, 2 Jul 1999 11:25:59 -0700
Message-Id: <199907021825.LAA12917@ultra.franz.com>
To: hoek@freebsd.org
Cc: freebsd-bugs@freebsd.org
Subject: Re: kern/5991: panic: free vnode isn't 
In-reply-to: Your message of "Fri, 02 Jul 1999 11:24:24 PDT."
             <199907021824.LAA81111@freefall.freebsd.org> 
Date: Fri, 02 Jul 1999 11:25:58 -0700
From: Ahmon Dancy <dancy@franz.com>
Sender: owner-freebsd-bugs@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

>> Synopsis: panic: free vnode isn't
>> 
>> State-Changed-From-To: open->closed
>> State-Changed-By: hoek
>> State-Changed-When: Fri Jul 2 11:22:33 PDT 1999
>> State-Changed-Why: 
>> 3.0 of that time was infamous for free vnode isn't panics.  This seems
>> to be the same panic as reported in kern/4382.  Most of these have been
>> fixed (the free vnode isn't panics).  If you're still experiencing the
>> problem, please saying that so I can make sure at least one of the PRs
>> stays open.

This ultimately turned out to be a hardware problem.  You can
completely delete this problem report if you'd like.



To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-bugs" in the body of the message