Date: Fri, 10 Aug 2018 19:04:24 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 230510] iflib/vlan panic: sleeping thread Message-ID: <bug-230510-227@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D230510 Bug ID: 230510 Summary: iflib/vlan panic: sleeping thread Product: Base System Version: CURRENT Hardware: Any OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: bugzilla.freebsd@omnilan.de If I utilize rc.network(8) to create a vlan(4) child of a iflib em0(4) pare= nt device, I get really a lot of LOR's (most likely all LOR's too fast to read= ).=20 Estimated 500-2000 LOR's before panic. Here's the backtrace: #1 0xffffffff803ecb2b in db_dump (dummy=3D<value optimized out>, dummy2=3D= <value optimized out>, dummy3=3D<value optimized out>,=20 dummy4=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/ddb/db_command.c:574 #2 0xffffffff803ec8f9 in db_command (cmd_table=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/ddb/db_command.c:481 #3 0xffffffff803ec674 in db_command_loop () at /usr/local/share/deploy-tools/HEAD/src/sys/ddb/db_command.c:534 #4 0xffffffff803ef8ff in db_trap (type=3D<value optimized out>, code=3D<va= lue optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/ddb/db_main.c:252 #5 0xffffffff80834923 in kdb_trap (type=3D3, code=3D0, tf=3D<value optimiz= ed out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/subr_kdb.c:693 #6 0xffffffff80b4a3ef in trap (frame=3D0xfffffe00751e8560) at /usr/local/share/deploy-tools/HEAD/src/sys/amd64/amd64/trap.c:605 #7 0xffffffff80b25d95 in calltrap () at /usr/local/share/deploy-tools/HEAD/src/sys/amd64/amd64/exception.S:232 #8 0xffffffff80833ffb in kdb_enter (why=3D0xffffffff80ca81cc "panic", msg= =3D<value optimized out>) at cpufunc.h:65 #9 0xffffffff807e9c00 in vpanic (fmt=3D<value optimized out>, ap=3D0xfffffe00751e86d0) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_shutdown.c:852 #10 0xffffffff807e9c93 in panic (fmt=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_shutdown.c:790 #11 0xffffffff8084bab5 in propagate_priority (td=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/subr_turnstile.c:228 #12 0xffffffff8084c56d in turnstile_wait (ts=3D0xfffff80003089e40, owner=3D0xfffff800035da580, queue=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/subr_turnstile.c:783 #13 0xffffffff807c7cf1 in __mtx_lock_sleep (c=3D0xfffff80003636ee0, v=3D<va= lue optimized out>, opts=3D<value optimized out>,=20 file=3D<value optimized out>, line=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_mutex.c:639 #14 0xffffffff807c7a79 in __mtx_lock_flags (c=3D0xfffff80003636ee0, opts=3D= <value optimized out>, file=3D<value optimized out>,=20 line=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_mutex.c:255 #15 0xffffffff807e3725 in _rm_wlock (rm=3D0xfffff80003636e88) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_rmlock.c:540 #16 0xffffffff807e3a94 in _rm_wlock_debug (rm=3D0xfffff80003636e88,=20 file=3D0xffffffff80cb26fe "/usr/local/share/deploy-tools/HEAD/src/sys/net/if_vlan.c", line=3D1639) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_rmlock.c:605 #17 0xffffffff80904f9b in vlan_link_state (ifp=3D0xfffff80003ba3000) at /usr/local/share/deploy-tools/HEAD/src/sys/net/if_vlan.c:1639 #18 0xffffffff808efd90 in do_link_state_change (arg=3D0xfffff80003ba3000, pending=3D1) at /usr/local/share/deploy-tools/HEAD/src/sys/net/if.c:2332 #19 0xffffffff808484bc in taskqueue_run_locked (queue=3D0xfffff800030b3500) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/subr_taskqueue.c:465 #20 0xffffffff8084832a in taskqueue_run (queue=3D0xfffff800030b3500) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/subr_taskqueue.c:484 #21 0xffffffff807ab180 in ithread_loop (arg=3D<value optimized out>) at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_intr.c:1043 #22 0xffffffff807a8004 in fork_exit (callout=3D0xffffffff807ab040 <ithread_= loop>, arg=3D0xfffff8000359e080, frame=3D0xfffffe00751e8ac0) ---Type <return> to continue, or q <return> to quit--- at /usr/local/share/deploy-tools/HEAD/src/sys/kern/kern_fork.c:1057 #23 0xffffffff80b26d6e in fork_trampoline () at /usr/local/share/deploy-tools/HEAD/src/sys/amd64/amd64/exception.S:990 #24 0x0000000000000000 in ?? () Unfortunately I don't have the source easily accessabele on that system and also no easy way to capture console output. Please tell me if additional info is a prerequisite to analyze the problem, I'll provide the missing parts. Thanks, -harry P.S.: If I manually create the vlan(4) child from multi user shell, there a= re LOR's but _no_ panic happening. Also, the vlan(4) device works afterwards. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-230510-227>