Using a debug kernel, the machine came up quickly with this LOR
after the reboot:
lock order reversal:
1st 0xc077078c tcp (tcp) @ /usr/src/sys/netinet/tcp_input.c:625
2nd 0xc4f18180 pf task mtx (pf task mtx) @
/usr/src/sys/modules/pf/../../contrib/pf/net/pf.c:6386
KDB: stack backtrace:
kdb_backtrace(0,ffffffff,c072fcd0,c072e1c8,c06f6124,...) at
kdb_backtrace+0x29
witness_checkorder(c4f18180,9,c4f1536e,18f2) at witness_checkorder+0x578
_mtx_lock_flags(c4f18180,0,c4f1536e,18f2,c4f18180,...) at
_mtx_lock_flags+0x78
pf_test(2,c4bdec00,e35c5ac4,0,0,...) at pf_test+0x81
pf_check_out(0,e35c5ac4,c4bdec00,2,0) at pf_check_out+0x3d
pfil_run_hooks(c0770340,e35c5b40,c4bdec00,2,0,...) at
pfil_run_hooks+0xc9
ip_output(c50c8200,0,e35c5b0c,0,0,0) at ip_output+0x83a
tcp_respond(0,c4f85810,c4f85824,c50c8200,0,7a481ad6,4) at
tcp_respond+0x3e1
tcp_input(c50c8200,14,1,93d306d9,0,...) at tcp_input+0x3124
ip_input(c50c8200) at ip_input+0x785
netisr_processqueue(c076dfd8) at netisr_processqueue+0x6e
swi_net(0) at swi_net+0xc2
ithread_execute_handlers(c4afca78,c4b4b180) at
ithread_execute_handlers+0xe6
ithread_loop(c4adb990,e35c5d38,c4adb990,c0505918,0,...) at
ithread_loop+0x67
fork_exit(c0505918,c4adb990,e35c5d38) at fork_exit+0xa0
fork_trampoline() at fork_trampoline+0x8
--- trap 0x1, eip = 0, esp = 0xe35c5d6c, ebp = 0 ---
Expensive timeout(9) function: 0xc0528fb4(0) 0.002565972 s
Is it a known LOR?
`uname -a'
FreeBSD ... 6.2-RELEASE-p5 FreeBSD 6.2-RELEASE-p5 #0: Fri May 25
12:34:43 CEST 2007 [EMAIL PROTECTED]:/usr/obj/usr/src/sys/GwMbg.debug i386
I'll keep watching this machine now it has debug functionality in
kernel.
Volker
_______________________________________________
freebsd-stable@freebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-stable
To unsubscribe, send any mail to "[EMAIL PROTECTED]"
