From owner-freebsd-current  Tue May 21 18:49:21 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id SAA24724
          for current-outgoing; Tue, 21 May 1996 18:49:21 -0700 (PDT)
Received: from phaeton.artisoft.com (phaeton.Artisoft.COM [198.17.250.211])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id SAA24719
          for <current@freebsd.org>; Tue, 21 May 1996 18:49:19 -0700 (PDT)
Received: (from terry@localhost) by phaeton.artisoft.com (8.6.11/8.6.9) id SAA02815; Tue, 21 May 1996 18:44:10 -0700
From: Terry Lambert <terry@lambert.org>
Message-Id: <199605220144.SAA02815@phaeton.artisoft.com>
Subject: Re: Possible problem with new VM code?
To: sysseh@devetir.qld.gov.au (Stephen Hocking)
Date: Tue, 21 May 1996 18:44:10 -0700 (MST)
Cc: toor@dyson.iquest.net, current@freebsd.org
In-Reply-To: <199605220045.AAA01916@netfl15a.devetir.qld.gov.au> from "Stephen Hocking" at May 22, 96 10:45:35 am
X-Mailer: ELM [version 2.4 PL24]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

> After installing the latest patches to vm_object.c (ctm src-cur 1809) I am now 
> getting a new sort of panic!
> 
> panic: cleaned vnode isn't
> 
> _getnewvnode(1,f0932600,f0909800,efbffdac,efbffe08) at _getnewvnode+0x10d
> _ffs_vget(f0932600,2,efbffdc8,f01bb980,0) at _ffs_vget+0xa3
> _ufs_root(f0932600,efbffe08,f091aa80,efbfff94,efbffea0) at _ufs_root+0x1c
> _lookup(,efbfff94,f0a60000,efbfff94,100) at _lookup+0x463
> _namei(efbffea0,efbfff94,f0a60000,0,10540) at _namei+0x183
> _stat(f0a60000,efbfff94,efbfff84,807d060,efbfdb78) at _stat+0x44
> _syscall(10027,efbf0027,10540,efbfdb78,efbfdbd8) at _syscall+0x19c
> _Xsyscall() at _Xsyscall+0x35
> 
> --- syscall 188, eip = 0x806b7f1, ebp = 0xefbfdbd8

Look at my original vget/vclean patch for this and see if it helps;
I was pretty sure that the fix the went in for this avoided the
problem instead of fixing it.

My patch was a kludge, but it addressed the actual problem location.

It should be in the -current list archives (look for "free vnode isn't").


					Terry Lambert
					terry@lambert.org
---
Any opinions in this posting are my own and not those of my present
or previous employers.