I'm not exactly sure what condition is causing this, but I'm getting the occasional LOR while setting up some gif tunnels: lock order reversal: 1st 0xc3bde2b8 rtentry (rtentry) @ netinet6/nd6.c:1930 2nd 0xc3af367c radix node head (radix node head) @ net/route.c:147 KDB: stack backtrace: db_trace_self_wrapper (c08af130,e11b8600,c0662bbe,c08b1592,c3af367c,...) at db_trace_self_wrapper+0x26 kdb_backtrace(c08b1592,c3af367c,c08b15f3,c08b15f3,c08b9ce7,...) at kdb_backtrace+0x29 witness_checkorder(c3af367c,9,c08b9cde,93,e11b8624,...) at witness_checkorder+0x6de _mtx_lock_flags(c3af367c,0,c08b9cde,93,c066160b,...) at _mtx_lock_flags+0xbc rtalloc1(e11b86e0,0,0,0,c3c9d01c,...) at rtalloc1+0x63 nd6_lookup(c3c9d024,0,c39fd800,c3bde258,c3bde258,...) at nd6_lookup+0x55 nd6_is_addr_neighbor(c3c9d01c,c39fd800,c08c1d75,78a,c09a5ed8,...) at nd6_is_addr_neighbor+0x3b nd6_output(c39fd800,c39fd800,c3cf9b00,c3c9d01c,c3bde258,...) at nd6_output+0x10f ip6_output(c3cf9b00,0,e11b88e0,0,0,...) at ip6_output+0x1081 icmp6_reflect(c3cf9b00,28,8,1,c08c96d0,...) at icmp6_reflect+0x42f icmp6_input(e11b8c88,e11b8c70,3a,1d5,0,...) at icmp6_input+0x6dc ip6_input(c3be2900,0,c08b9887,8c,c09a1e24,...) at ip6_input+0xe36 netisr_processqueue(c0955e30,0,c08b9887,f6,c3865a40,...) at netisr_processqueue+0x8b swi_net(0,0,c08a938d,471,c3870364,...) at swi_net+0x9b ithread_loop(c383ac90,e11b8d38,c08a9115,305,c3873000,...) at ithread_loop+0x1b5 fork_exit(c060fbe0,c383ac90,e11b8d38) at fork_exit+0xb8 fork_trampoline() at fork_trampoline+0x8 --- trap 0, eip = 0, esp = 0xe11b8d70, ebp = 0 --- How-To-Repeat: I haven't been able to figure out what steps are necessary to reproduce this LOR.
Responsible Changed From-To: freebsd-bugs->freebsd-net Over to maintainer(s).
For bugs matching the following criteria: Status: In Progress Changed: (is less than) 2014-06-01 Reset to default assignee and clear in-progress tags. Mail being skipped