[Bug 219901] [Panic] [VIMAGE] [if_bridge] panic when destroying interface on bridge over time
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Sat Jun 10 07:12:45 UTC 2017
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=219901
Bug ID: 219901
Summary: [Panic] [VIMAGE] [if_bridge] panic when destroying
interface on bridge over time
Product: Base System
Version: CURRENT
Hardware: amd64
OS: Any
Status: New
Severity: Affects Only Me
Priority: ---
Component: kern
Assignee: freebsd-bugs at FreeBSD.org
Reporter: reshadpatuck1 at gmail.com
Created attachment 183373
--> https://bugs.freebsd.org/bugzilla/attachment.cgi?id=183373&action=edit
core.txt for crash on 2017-06-10 r319591
While testing vnet jails over time and bringing about 20 of them up and down
about 10-20 times a day I get this panic (bridge_set_ifcap).
I have attached the core.txt for the panic to this post.
The issue seems to be during the tear-down of an interface on an if_bridge,
while setting the interface capabilities on the bridge.
This is the third time the same panic has occurred and this occurs after some
time (~5 days).
I have tried running a script that ups and downs the vnet jails in a loop and
have not been able to recreate the panic.
I have crash dumps and core.txt for all three of them, but the trace back is
almost identical so am attaching the most recent one.
Pleas let me know if there is any other information you require.
Thanks
---
(kgdb) #0 doadump (textdump=0) at pcpu.h:232
#1 0xffffffff803a308b in db_dump (dummy=<value optimized out>,
dummy2=<value optimized out>, dummy3=<value optimized out>,
dummy4=<value optimized out>) at /usr/src/sys/ddb/db_command.c:546
#2 0xffffffff803a2e7f in db_command (cmd_table=<value optimized out>)
at /usr/src/sys/ddb/db_command.c:453
#3 0xffffffff803a2bb4 in db_command_loop ()
at /usr/src/sys/ddb/db_command.c:506
#4 0xffffffff803a5c7f in db_trap (type=<value optimized out>,
code=<value optimized out>) at /usr/src/sys/ddb/db_main.c:248
#5 0xffffffff80a98b23 in kdb_trap (type=9, code=0, tf=<value optimized out>)
at /usr/src/sys/kern/subr_kdb.c:654
#6 0xffffffff80ef6532 in trap_fatal (frame=0xfffffe104379d430, eva=0)
at /usr/src/sys/amd64/amd64/trap.c:796
#7 0xffffffff80ef5b3d in trap (frame=0xfffffe104379d430) at counter.h:85
#8 0xffffffff80ed88e1 in calltrap ()
at /usr/src/sys/amd64/amd64/exception.S:236
#9 0xffffffff82e7620f in bridge_set_ifcap (sc=0xfffff8002866bc00,
bif=<value optimized out>, set=8) at /usr/src/sys/net/if_bridge.c:940
#10 0xffffffff82e75f0d in bridge_delete_member (sc=0xfffff8002866bc00,
bif=0xfffff8083d54ea00, gone=0) at /usr/src/sys/net/if_bridge.c:1065
#11 0xffffffff82e73dca in bridge_clone_destroy (ifp=0xfffff80251155000)
at /usr/src/sys/net/if_bridge.c:733
#12 0xffffffff80b510c7 in if_clone_destroyif (ifc=0xfffff8000efd2c80,
ifp=<value optimized out>) at /usr/src/sys/net/if_clone.c:719
#13 0xffffffff80b50e29 in if_clone_destroy (name=0xfffffe104379d780 "igb1br")
at /usr/src/sys/net/if_clone.c:284
#14 0xffffffff80b4c283 in ifioctl (so=0xfffff80251beb000,
cmd=<value optimized out>, data=<value optimized out>,
td=<value optimized out>) at /usr/src/sys/net/if.c:2802
#15 0xffffffff80abd72d in kern_ioctl (td=<value optimized out>,
fd=<value optimized out>, com=<value optimized out>,
data=<value optimized out>) at file.h:323
#16 0xffffffff80abd3ef in sys_ioctl (td=<value optimized out>,
uap=0xfffffe104379d930) at /usr/src/sys/kern/sys_generic.c:745
#17 0xffffffff80ef6fd9 in amd64_syscall (td=0xfffff80251001000, traced=0)
at subr_syscall.c:136
#18 0xffffffff80ed8bcb in Xfast_syscall ()
at /usr/src/sys/amd64/amd64/exception.S:396
#19 0x0000000800fdc4ca in ?? ()
Previous frame inner to this frame (corrupt stack?)
Current language: auto; currently minimal
(kgdb)
---
# uname -a
FreeBSD v3dev-20-7 12.0-CURRENT FreeBSD 12.0-CURRENT #9 r319591: Sun Jun 4
23:01:11 UTC 2017 root at pkgbase:/usr/obj/usr/src/sys/VNET amd64
---
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-bugs
mailing list