[Bug 219901] [Panic] [if_bridge] panic when destroying interface on bridge over time

bugzilla-noreply at freebsd.org bugzilla-noreply at freebsd.org
Mon Dec 2 03:39:23 UTC 2019


--- Comment #2 from Reshad Patuck <reshadpatuck1 at gmail.com> ---
(In reply to Bjoern A. Zeeb from comment #1)


I know it has been long, but I recently have seen similar failure on 12.1 (and
I think on one of my 12.0 systems too).
I do have the crash dump vmcore files if you would like me to run some other

This happens when I am trying to teardown the networking across multiple vimage
jails (by calling ifconfig commands in parallel).
>From the backtrace this looks specific to removing an epair from a bridge (once
again using ifconfig in parallel).
I am not sure that the issue I am facing here is exactly the same as the one I
saw when creating this issue, but it looks very similar.

Here is the backtrace from kgdb for what I am seeing.
I am using the latest 12.1 release and have attached an output of uname for the
exact release version.

Any help either getting to a route cause or even a workaround for this would be
much appreciated as I have seen 6 crashes in the last week

root at build-1:~ # uname -a
FreeBSD build-1 12.1-RELEASE-p1 FreeBSD 12.1-RELEASE-p1 r354729 GENERIC  amd64

(kgdb) backtrace 
#0  __curthread () at /usr/src/sys/amd64/include/pcpu.h:234
#1  doadump (textdump=<optimized out>) at /usr/src/sys/kern/kern_shutdown.c:371
#2  0xffffffff80bd01c8 in kern_reboot (howto=260) at
#3  0xffffffff80bd0629 in vpanic (fmt=<optimized out>, ap=<optimized out>) at
#4  0xffffffff80bd0423 in panic (fmt=<unavailable>) at
#5  0xffffffff810a7dcc in trap_fatal (frame=0xfffffe001c730380, eva=1040) at
#6  0xffffffff810a7e19 in trap_pfault (frame=0xfffffe001c730380, usermode=0) at
#7  0xffffffff810a740f in trap (frame=0xfffffe001c730380) at
#8  <signal handler called>
#9  __mtx_lock_sleep (c=0xfffff80066f6fa30, v=<optimized out>) at
#10 0xffffffff82be048e in bridge_mutecaps (sc=0xfffff80066f6fa00) at
#11 0xffffffff82be017a in bridge_delete_member (sc=0xfffff80066f6fa00,
bif=0xfffff80028463000, gone=1) at /usr/src/sys/net/if_bridge.c:1033
#12 0xffffffff82be07eb in bridge_ifdetach (arg=<optimized out>,
ifp=0xfffff80004900800) at /usr/src/sys/net/if_bridge.c:1829
#13 0xffffffff80ccde5a in if_detach_internal (ifp=<optimized out>, vmove=0,
ifcp=0x0) at /usr/src/sys/net/if.c:1187
#14 0xffffffff80ccd36e in if_detach (ifp=0xfffff80066f6fa30) at
#15 0xffffffff83055c4c in epair_clone_destroy (ifc=0xfffff800209a8300,
ifp=0xfffff80004900800) at /usr/src/sys/net/if_epair.c:972
#16 0xffffffff80cd5b7d in if_clone_destroyif (ifc=0xfffff800209a8300,
ifp=0xfffff80004900800) at /usr/src/sys/net/if_clone.c:330
#17 0xffffffff80cd5a0e in if_clone_destroy (name=0xfffffe001c7308c0
"epair205a") at /usr/src/sys/net/if_clone.c:288
#18 0xffffffff80cd2915 in ifioctl (so=0xfffff800207d3000, cmd=2149607801,
data=0xfffffe001c7308c0 "epair205a", td=<optimized out>) at
#19 0xffffffff80c3b55e in fo_ioctl (fp=<optimized out>, com=<optimized out>,
data=0xfffff8005f459000, active_cred=0x1, td=<optimized out>) at
#20 kern_ioctl (td=0xfffff8005f459000, fd=<optimized out>, com=2149607801,
data=0xfffff8005f459000 "") at /usr/src/sys/kern/sys_generic.c:804
#21 0xffffffff80c3b22d in sys_ioctl (td=0xfffff8005f459000,
uap=0xfffff8005f4593c0) at /usr/src/sys/kern/sys_generic.c:712
#22 0xffffffff810a8984 in syscallenter (td=0xfffff8005f459000) at
#23 amd64_syscall (td=0xfffff8005f459000, traced=0) at
#24 <signal handler called>
#25 0x0000000800473e4a in ?? ()
Backtrace stopped: Cannot access memory at address 0x7fffffffe308

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

More information about the freebsd-net mailing list