I see these messages regularly when building releases on my SMP current
box. It happens during the part where the floppies are built. It does not
break the build process and the machine does not panic, so it isn't a big
problem for me. Maybe it rings a bell for someone.
This is with a kernel built yesterday, but it also happened with a kernel
built on Dec 21.
#
unexpected vn driver lock: 0xc9494d00: type VREG, usecount 2, writecount 1, refcount
541, flags (VOBJBUF)
tag VT_UFS, ino 403493, on dev #da/20 (13, 20) lock type inode: EXCL (count 1)
by pid 4
unexpected vn driver lock: 0xc9494d00: type VREG, usecount 2, writecount 1, refcount
322, flags (VOBJBUF)
tag VT_UFS, ino 403493, on dev #da/20 (13, 20) lock type inode: EXCL (count 1)
by pid 4
unexpected vn driver lock: 0xc9580f00: type VREG, usecount 2, writecount 1, refcount
361, flags (VOBJBUF)
tag VT_UFS, ino 382428, on dev #da/20 (13, 20) lock type inode: EXCL (count 1)
by pid 4
unexpected vn driver lock: 0xc90c4d00: type VREG, usecount 2, writecount 1, refcount
541, flags (VOBJBUF)
tag VT_UFS, ino 404067, on dev #da/20 (13, 20) lock type inode: EXCL (count 1)
by pid 4
unexpected vn driver lock: 0xc90c4d00: type VREG, usecount 2, writecount 1, refcount
181, flags (VOBJBUF)
tag VT_UFS, ino 404079, on dev #da/20 (13, 20) lock type inode: EXCL (count 1)
by pid 76048
##
John
--
John Hay -- [EMAIL PROTECTED]
To Unsubscribe: send mail to [EMAIL PROTECTED]
with "unsubscribe freebsd-current" in the body of the message
