From owner-freebsd-current  Wed May 22 17:19:49 1996
Return-Path: owner-current
Received: (from root@localhost)
          by freefall.freebsd.org (8.7.3/8.7.3) id RAA13112
          for current-outgoing; Wed, 22 May 1996 17:19:49 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au (pp@bunyip.cc.uq.oz.au [130.102.2.1])
          by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id RAA13104
          for <current@freebsd.org>; Wed, 22 May 1996 17:19:44 -0700 (PDT)
Received: from bunyip.cc.uq.oz.au by bunyip.cc.uq.oz.au 
          id <26972-0@bunyip.cc.uq.oz.au>; Thu, 23 May 1996 10:19:22 +1000
Received: from netfl15a.devetir.qld.gov.au 
          by pandora.devetir.qld.gov.au (8.6.10/DEVETIR-E0.3a) with ESMTP 
          id KAA17653; Thu, 23 May 1996 10:19:58 +1000
Received: from localhost by netfl15a.devetir.qld.gov.au (8.6.8.1/DEVETIR-0.1) 
          id AAA26735; Thu, 23 May 1996 00:20:41 GMT
Message-Id: <199605230020.AAA26735@netfl15a.devetir.qld.gov.au>
X-Mailer: exmh version 1.6.5 12/11/95
To: Terry Lambert <terry@lambert.org>
cc: toor@dyson.iquest.net, current@freebsd.org
Subject: Re: Possible problem with new VM code?
In-reply-to: Your message of "Tue, 21 May 1996 18:44:10 MST." <199605220144.SAA02815@phaeton.artisoft.com>
X-Face: 3}heU+2?b->-GSF-G4T4>jEB9~FR(V9lo&o>kAy=Pj&;oVOc<|pr%I/VSG"ZD32J>5gGC0N 
        7gj]^GI@M:LlqNd]|(2OxOxy@$6@/!,";-!OlucF^=jq8s57$%qXd/ieC8DhWmIy@J1AcnvSGV\|*! 
        >Bvu7+0h4zCY^]{AxXKsDTlgA2m]fX$W@'8ev-Qi+-;%L'CcZ'NBL!@n?}q!M&Em3*eW7,093nOeV8 
        M)(u+6D;%B7j\XA/9j4!Gj~&jYzflG[#)E9sI&Xe9~y~Gn%fA7>F:YKr"Wx4cZU*6{^2ocZ!YyR
Mime-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Date: Thu, 23 May 1996 10:20:40 +1000
From: Stephen Hocking <sysseh@devetir.qld.gov.au>
Sender: owner-current@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk

I had hoped that this was a FS corruption, but it appears not to be. I've 
newfs'd & restored from tape, but I can still reliably reproduce the problem 
(when mtree is run with BSD.root.dist on /). I deleted all my mail archives 
recently and as a result no longer have the patch  in question floating about. 
I'm very willing to work with you guys on this so that a fix can be found & 
committed ASAP. It appears as if each new revision of the VM subsystem seems 
to flush out bugs elsewhere...



          Stephen
> > 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.

-- 
The views expressed above are not those of the Worker's Compensation Board of
Queensland, Australia.