From owner-freebsd-net@freebsd.org Thu Jan 26 21:06:17 2017 Return-Path: Delivered-To: freebsd-net@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 051C6CC1A74 for ; Thu, 26 Jan 2017 21:06:17 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from kenobi.freebsd.org (kenobi.freebsd.org [IPv6:2001:1900:2254:206a::16:76]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id D0ED41D0 for ; Thu, 26 Jan 2017 21:06:16 +0000 (UTC) (envelope-from bugzilla-noreply@freebsd.org) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.15.2/8.15.2) with ESMTP id v0QL6GjN077919 for ; Thu, 26 Jan 2017 21:06:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 216304] Adding xn0 to bridge0 causes kernel panic Date: Thu, 26 Jan 2017 21:06:16 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: changed X-Bugzilla-Watch-Reason: None X-Bugzilla-Product: Base System X-Bugzilla-Component: kern X-Bugzilla-Version: 11.0-RELEASE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Some People X-Bugzilla-Who: nvass@gmx.com X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: cc Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable X-Bugzilla-URL: https://bugs.freebsd.org/bugzilla/ Auto-Submitted: auto-generated MIME-Version: 1.0 X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 26 Jan 2017 21:06:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D216304 nvass@gmx.com changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |nvass@gmx.com --- Comment #5 from nvass@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 >=20 > cpuid =3D 1 > KDB: stack backtrace: > db_trace_self_wrapper() at db_trace_self_wrapper+0x2b/frame 0xfffffe00954= a3260 > 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 0xfffffe00954= a3680 > 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 =3D 0x800fd5aaa, rsp =3D = 0x7fffffffe1f8, rbp =3D 0x7fffffffe2a0 --- > KDB: enter: panic > [ thread pid 770 tid 100560 ] > Stopped at kdb_enter+0x3b: movq $0,kdb_why --=20 You are receiving this mail because: You are the assignee for the bug.=