panic: getblk: vnode 0xce889690 has no object!

Matthew Dillon dillon at
Sun Jan 28 21:20:38 PST 2007

:I caught this panic while playing with firefox- (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.

    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


More information about the Bugs mailing list