search for: witness_checkord

...eader kernel: KDB: stack backtrace: messages-Sep 26 02:01:27 leader kernel: db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe0238a8f270 messages-Sep 26 02:01:27 leader kernel: kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe0238a8f320 messages-Sep 26 02:01:27 leader kernel: witness_checkorder() at witness_checkorder+0xd23/frame 0xfffffe0238a8f3b0 messages-Sep 26 02:01:27 leader kernel: _sx_xlock() at _sx_xlock+0x75/frame 0xfffffe0238a8f3f0 messages-Sep 26 02:01:27 leader kernel: ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xfffffe0238a8f430 messages-Sep 26 02:01:27 leader kernel:...

...unt, fsck etc.. Perhaps this might be related: Full dmesg: http://people.freebsd.org/~ariff/misc/dmesg.boot.amd64 [....] acquiring duplicate lock of same type: "vnode interlock" 1st vnode interlock @ kern/vfs_vnops.c:791 2nd vnode interlock @ kern/vfs_subr.c:2018 KDB: stack backtrace: witness_checkorder() at witness_checkorder+0x4da _mtx_lock_flags() at _mtx_lock_flags+0x4a vrefcnt() at vrefcnt+0x31 null_checkvp() at null_checkvp+0x65 null_lock() at null_lock+0x5b VOP_LOCK_APV() at VOP_LOCK_APV+0x81 vn_lock() at vn_lock+0x6b nullfs_root() at nullfs_root+0x4c vfs_donmount() at vfs_donmount+0x1096...

...x_lock_spin_flags+0x123/frame 0xffffff9185023b40 cnputs() at cnputs+0x7a/frame 0xffffff9185023b60 putbuf() at putbuf+0xbf/frame 0xffffff9185023be0 kvprintf() at kvprintf+0x83/frame 0xffffff9185023d20 vprintf() at vprintf+0x85/frame 0xffffff9185024580 printf() at printf+0x67/frame 0xffffff9185024660 witness_checkorder() at witness_checkorder+0x794/frame 0xffffff9185024720 _mtx_lock_spin_flags() at _mtx_lock_spin_flags+0x94/frame 0xffffff9185024760 uart_cnputc() at uart_cnputc+0x3e/frame 0xffffff9185024780 cnputc() at cnputc+0x4c/frame 0xffffff91850247b0 cnputs() at cnputs+0x26/frame 0xffffff91850247d0 putbuf()...

9.2 PRERELEASE (today) / amd64 Hello, I'm seeing a panic while trying to build a poudriere repository. As far I can see it always happens when gam_server is started (ie xfce is running) and under disk load (poudriere bulk build) : (That is something new, the box was pretty stable) the complete crash dump (core.0.txt) is here: http://user.lamaiziere.net/patrick/panic_gam_server.txt Fatal

...1e28 bufwait (bufwait) @ /usr/src/sys/kern/vfs_bio.c:3050 2nd 0xfffff80005b87c00 dirhash (dirhash) @ /usr/src/sys/ufs/ufs/ufs_dirhash.c:284 KDB: stack backtrace: X_db_symbol_values() at X_db_symbol_values+0x10b/frame 0xfffffe012fb8c410 kdb_backtrace() at kdb_backtrace+0x39/frame 0xfffffe012fb8c4c0 witness_checkorder() at witness_checkorder+0xd23/frame 0xfffffe012fb8c550 _sx_xlock() at _sx_xlock+0x75/frame 0xfffffe012fb8c590 ufsdirhash_add() at ufsdirhash_add+0x3b/frame 0xfffffe012fb8c5d0 ufs_direnter() at ufs_direnter+0x688/frame 0xfffffe012fb8c690 ufs_vinit() at ufs_vinit+0x33f3/frame 0xfffffe012fb8c890 VOP...

Two machines (NFS Server: running ZFS / Client: disk-less), both are running FreeBSD r253506. The NFS client starts to deadlock processes within a few hours. It usually gets worse from there on. The processes stay in "D" state. I haven't been able to reproduce it when I want it to happen. I only have to wait a few hours until the deadlocks occur when traffic to the client machine