Subject: Re: panic: uvm_vnp_terminate: uvn in unexpected state
To: None <khym@bga.com>
From: Chuck Cranor <chuck@dworkin.wustl.edu>
List: port-i386
Date: 02/18/1998 20:30:35
>When trying to reboot, I got:
>syncing disks... 12 12 5 done
>uvm_vnp_terminate(0xf0539800): warning: object still active with 2 refs
>uvm_vnp_terminate: flags = 0x1, refs=2
>panic: uvm_vnp_terminate: uvn in unexpected state

hi-

  this was fixed in uvm_vnode.c 1.5.   

  it is related to the "forced" umount of "/" that occurs at reboot.
UVM is complaining that it has been asked to terminate a vnode that
has active mappings (usually /sbin/init and /sbin/reboot).   the
semantics of doing this were not clear to me from the vnode code
(which isn't well documented), but i think i've fixed it.

  the panic was due to the fact that "/sbin/init" got unlinked and
and as part of that it gets "uncached" so that it doesn't persist
after the last reference goes.   that happened to set off a sanity
check (panic) that wasn't quite in sync with the BSD vnode code.

chuck