I managed to panic my 8.0-CURRENT i386 box (kernel built from csup as
of 4/1/2008).
At the time I had just issued a "reboot" when the panic occurred.
Here is the kgdb output, and after that the backtrace, finally
followed by the dmesg.
I haven't been able to reproduce it, unfortunately.
Regards,
Josh
root@dev:/usr/obj/usr/src/sys/DEV# kgdb kernel.debug /var/crash/vmcore.0
[GDB will not be able to debug user-mode threads:
/usr/lib/libthread_db.so: Undefined symbol "ps_pglobal_lookup"]
GNU gdb 6.1.1 [FreeBSD]
Copyright 2004 Free Software Foundation, Inc.
GDB is free software, covered by the GNU General Public License, and you are
welcome to change it and/or distribute copies of it under certain conditions.
Type "show copying" to see the conditions.
There is absolutely no warranty for GDB. Type "show warranty" for details.
This GDB was configured as "i386-marcel-freebsd".
Reading symbols from /boot/kernel/coretemp.ko...Reading symbols from
/boot/kernel/coretemp.ko.symbols...done.
done.
Loaded symbols for /boot/kernel/coretemp.ko
Unread portion of the kernel message buffer:
<118>Apr 2 03:03:14 dev syslogd: exiting on signal 15
Waiting (max 60 seconds) for system process `vnlru' to stop...done
Wa
iStyinncgi n(gm adxi s6k0s ,s evcnoonddess) rfeomra isnyisntge.m.
.p2r ocess `syncer' to stop...2 0 1 1 0 0 done
Waiting (max 60 seconds) for system process `bufdaemon' to stop...done
All buffers synced.
lock order reversal:
1st 0xc4f1f29c vfslock (vfslock) @ /usr/src/sys/kern/vfs_mount.c:1250
2nd 0xc4f38ce4 syncer (syncer) @ /usr/src/sys/kern/vfs_subr.c:2144
KDB: stack backtrace:
db_trace_self_wrapper(c07ced1b,e77e3adc,c05f958e,c07d1233,c4f38ce4,...)
at db_trace_self_wrapper+0x26
kdb_backtrace(c07d1233,c4f38ce4,c07d7f9a,c07d7f9a,c07d76ef,...) at
kdb_backtrace+0x29
witness_checkorder(c4f38ce4,9,c07d76ef,860,0,...) at witness_checkorder+0x6de
_lockmgr_args(c4f38ce4,20002,c4f38d14,0,ffffffff,...) at ...
