[Bug 216304] Adding xn0 to bridge0 causes kernel panic

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Thu Jan 26 21:06:17 UTC 2017


https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=216304

nvass at gmx.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |nvass at gmx.com

--- Comment #5 from nvass at gmx.com ---
Hi,

I am getting something similar and I am not sure whether it's related.

> panic: _mtx_lock_sleep: recursed on non-recursive mutex if_bridge @ /usr/src/sys/modules/if_bridge/../../net/if_bridge.c:2117
> 
> cpuid = 1
> KDB: stack backtrace:
> db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00954a3260
> vpanic() at vpanic+0x186/frame 0xfffffe00954a32e0
> kassert_panic() at kassert_panic+0x126/frame 0xfffffe00954a3350
> __mtx_lock_sleep() at __mtx_lock_sleep+0x3e2/frame 0xfffffe00954a33d0
> __mtx_lock_flags() at __mtx_lock_flags+0x116/frame 0xfffffe00954a3430
> bridge_transmit() at bridge_transmit+0x61/frame 0xfffffe00954a3470
> ether_output() at ether_output+0x703/frame 0xfffffe00954a3510
> arprequest() at arprequest+0x413/frame 0xfffffe00954a3620
> arp_ifinit() at arp_ifinit+0x56/frame 0xfffffe00954a3660
> arp_handle_ifllchange() at arp_handle_ifllchange+0x3d/frame 0xfffffe00954a3680
> bridge_ioctl_add() at bridge_ioctl_add+0x3b4/frame 0xfffffe00954a36d0
> bridge_ioctl() at bridge_ioctl+0x29f/frame 0xfffffe00954a3770
> ifioctl() at ifioctl+0xbc8/frame 0xfffffe00954a37f0
> kern_ioctl() at kern_ioctl+0x2b0/frame 0xfffffe00954a3850
> sys_ioctl() at sys_ioctl+0x13f/frame 0xfffffe00954a3930
> amd64_syscall() at amd64_syscall+0x2f9/frame 0xfffffe00954a3ab0
> Xfast_syscall() at Xfast_syscall+0xfb/frame 0xfffffe00954a3ab0
> --- syscall (54, FreeBSD ELF64, sys_ioctl), rip = 0x800fd5aaa, rsp = 0x7fffffffe1f8, rbp = 0x7fffffffe2a0 ---
> KDB: enter: panic
> [ thread pid 770 tid 100560 ]
> Stopped at      kdb_enter+0x3b: movq    $0,kdb_why

-- 
You are receiving this mail because:
You are the assignee for the bug.


More information about the freebsd-net mailing list