Panic in a vkernel: getblk: vnode 0x669232e8 has no object!

Rumko rumcic at
Tue Apr 1 01:57:43 PDT 2008

While compiling kde inside a vkernel a panic occured. The vkernel should be
from the latest source while the real kernel is from about Feb 7 (well there
is a possibility that the real kernel is too old right?).

Making all in kio
panic: getblk: vnode 0x669232e8 has no object!
Trace beginning at frame 0x672d4870
panic(672d4894,206d5938,669232e8,669232e8,672d48b8) at 0x80a1767
panic(81d7f84,669232e8,0,672d48cc,63be2ca8) at 0x80a1767
getblk(669232e8,fbfc8000,ffffffbf,4000,0) at 0x80d996e
ffs_balloc(ffffffff,2,672d4974,0,0) at 0x818b5ac
ffs_truncate(669232e8,0,0,0,0) at 0x818c215
ufs_inactive(672d4a58,672d4a74,80f001e,672d4a58,8209db0) at 0x81969b7
ufs_vnoperate(672d4a58,8209db0,5ee91fd0,66964418,0) at 0x8199569
vop_inactive(5ee91fd0,669232e8,669232f8,672d4a9c,808260a) at 0x80f001e
vget(669232e8,672d4b1c,669232f8,672d4ab0,80e7e97) at 0x80e803b
_sysref_put(669232f8,672d4b5c,66964418,672d4af8,80df8a0) at 0x808260a
vrele(669232e8,672d4b5c,669232e8,66580228,0) at 0x80e7e97
vop_compat_nresolve(672d4b1c,672d4b10,8199569,672d4b1c,672d4b40) at 0x80df8a0
vop_defaultop(672d4b1c,672d4b40,80f0323,672d4b1c,8209e40) at 0x80df3eb
ufs_vnoperate(672d4b1c,8209e40,5ee91fd0,672d4b94,66964418) at 0x8199569
vop_nresolve(5ee91fd0,672d4b5c,66580228,63b08878,63b67b60) at 0x80f0323
cache_resolve(672d4b8c,63b08878,672d4c38,0,672d4c38) at 0x80dc678
nlookup(672d4c38,0,672d4c38,672d4ca0,672d4c78) at 0x80e3e6d
kern_stat(672d4c38,672d4bd0,1,672d4c2c,bfbff000) at 0x80eba9f
sys_lstat(672d4ca0,6,0,0,671fb740) at 0x80ebb47
syscall2(672d4d40,2,6,0,0) at 0x81bd64f
user_trap(672d4d40,620cc700,81bd451,0,81bdcec) at 0x81bd822
go_user(672d4d38,0,0,7b,0) at 0x81bdba1
Stopped at      0x81bb269:      movb    $0,0x82a08d4

P.S.: I still have no idea how to get a coredump of a vkernel (it's currently
in the debugger and I'll leave it like that for now), so how would I get more
usable info/dump?

More information about the Bugs mailing list