panic: getblk: vnode 0xce889690 has no object!

[Matthew Dillon]

:...
:> :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.
:
:Done, saved as ~y0netan1/crash/panic-11.tar.gz .  The source code
:is as of just before my last commit to /sys/dev/acpica5/acpi.c (rev 1.30).
:
:Regards.

    Hmm.  Something very odd is going on here.  It is trying to resolve
    the filename "firefox-2.0.0.1" at this path:

	frame 9
	print ap->a_nch->ncp->nc_name			("firefox-2.0.0.1")
	print ap->a_nch->ncp->nc_parent->nc_name	("firefox")
	print *ap->a_nch->mount				("/u")

    So the path is:

	"/u/firefox/firefox-2.0.0.1"

    The problem is that /u/firefox seems to be a softlink.  At least,
    the vnode is marked as being a softlink and that makes the
    namecache entry illegal because it must be a directory (the namecache
    represents the 'real' path, not paths through softlinks).

    The kernel then treats the vnode as a directory even though it is
    a VLNK, tries to do a block lookup on it, and panics.

					-Matt
					Matthew Dillon 
					<dillon at backplane.com>