panic: __lockmgr_args: recursing on non recursive lockmgr ntnode
mi+thun at aldan.algebra.com
Mon Jul 12 20:14:05 UTC 2010
A laptop I'm helping configure (remotely) just crashed under me... Upon
reboot I found the following in the messages file (quite amazed, that
the message got there, actually):
Jul 12 22:06:01 s syslogd: kernel boot file is /boot/kernel/kernel
Jul 12 22:06:01 s kernel: panic: __lockmgr_args: recursing on non
recursive lockmgr *ntnode* @ (null):0
Jul 12 22:06:01 s kernel:
Jul 12 22:06:01 s kernel: cpuid = 0
Jul 12 22:06:01 s kernel: Uptime: 6h10m53s
Jul 12 22:06:01 s kernel: Cannot dump. Device not defined or
Jul 12 22:06:01 s kernel: Automatic reboot in 15 seconds - press a
key on the console to abort
Jul 12 22:06:01 s kernel: Rebooting...
Jul 12 22:06:01 s kernel: cpu_reset: Stopping other CPUs
The system just finished installing a new port of OpenOffice and
cleaning up WRKSRC afterwards (a huge collection of files), and was
running /etc/periodic/weekly/310.locate explicitly, when the crash happened.
Is this something, that's already solved and I just need to upgrade? The
current kernel is: FreeBSD 8.1-PRERELEASE #0: Wed Jul 7 19:04:57 CEST
2010, i386. 4 CPUs (Full dmesg.boot available upon request.)
Does the "ntnode" above point to the NTFS filesystems on this laptop?
The laptop uses Windows' swap-file as its own swap (via md(4)) and uses
Windows' TrueType fonts as well...
More information about the freebsd-stable