panic: getblk: vnode 0xce889690 has no object!
qhwt+dfly at les.ath.cx
Mon Jan 29 03:13:05 PST 2007
On Sun, Jan 28, 2007 at 09:10:07PM -0800, Matthew Dillon wrote:
> :I caught this panic while playing with firefox-220.127.116.11 (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
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).
More information about the Bugs