lock-order problem

From: Takeharu KATO <takeharu1219_at_ybb.ne.jp>
Date: Mon, 14 Mar 2005 07:59:28 +0900
Hi

I met a lock order problem on current(downloaded at 2005/3/13).
This is found in AMD64(opetron) SMP machine.
I show log messages as follows:
--
lock order reversal
 1st 0xffffff00614003d8 rtentry (rtentry) _at_ netinet/if_ether.c:445
 2nd 0xffffffff80c41458 bge0 (network driver) _at_ dev/bge/if_bge.c:3294
KDB: stack backtrace:
witness_checkorder() at witness_checkorder+0x5f1
_mtx_lock_flags() at _mtx_lock_flags+0x4a
bge_start() at bge_start+0x34
ether_output_frame() at ether_output_frame+0x249
ether_output() at ether_output+0x281
arprequest() at arprequest+0x109
arpresolve() at arpresolve+0x345
ether_output() at ether_output+0x317
ip_output() at ip_output+0xb22
icmp_reflect() at icmp_reflect+0x366
icmp_input() at icmp_input+0x2f4
ip_input() at ip_input+0x10f
netisr_processqueue() at netisr_processqueue+0x17
swi_net() at swi_net+0xa8
ithread_loop() at ithread_loop+0xd8
fork_exit() at fork_exit+0xc0
fork_trampoline() at fork_trampoline+0xe
--- trap 0, rip = 0, rsp = 0xffffffffb1dacd00, rbp = 0 ---

Regards,

-- 
Takeharu KATO
Received on Sun Mar 13 2005 - 21:59:31 UTC

This archive was generated by hypermail 2.4.0 : Wed May 19 2021 - 11:38:29 UTC