Re: panic: getblk: vnode 0xce889690 has no object!

[Matthew Dillon <dillon@xxxxxxxxxxxxxxxxxxxx>]

:Hello.
:I caught this panic while playing with firefox-2.0.0.1 (linux binary)
:and flash9 plugin.  The panic was triggered by /bin/ls (not
:/compat/linux/bin/ls), after firefox crashed.  I don't use any filesystems
:other than ufs (not even /proc), yet the trace involves vop_compat_nresolve.
:
:I did `fsck -fy' before this panic, so I believe this is not a panic-long-
:after-an-incomplete-fsck problem.
:
:Regards.

    Could you upload the coredump to leaf?

    This panic occurs when a vnode has no associated VM object.  VM objects
    used to be optional but are now mandatory, so there must have been a
    path where the vnode was created without a VM object (possibly before
    the ls).  Examining the vnode might give me a clue as to how that
    happened.

						-Matt