From owner-freebsd-net@freebsd.org Wed Sep 28 15:40:30 2016 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 32445C01A59 for ; Wed, 28 Sep 2016 15:40:30 +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 21DC8242 for ; Wed, 28 Sep 2016 15:40:30 +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 u8SFeTFi037050 for ; Wed, 28 Sep 2016 15:40:30 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 213015] openvswitch and vnet jails - panic when bridge is destroyed and recreated Date: Wed, 28 Sep 2016 15:40:30 +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-STABLE X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: akoshibe@gmail.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: 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: Wed, 28 Sep 2016 15:40:30 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D213015 --- Comment #7 from akoshibe@gmail.com --- (In reply to akoshibe from comment #5) Looking more closely, the panic is during the first time ovs-vsctl is calle= d in the script (after a previous uneventful run). The last lines I see in dmesg prior to a panic are: epair0a: Ethernet address: 02:ff:50:00:03:0a epair0b: Ethernet address: 02:ff:a0:00:05:0b <5>epair0a: link state changed to UP <5>epair0b: link state changed to UP epair1a: Ethernet address: 02:ff:50:00:06:0a epair1b: Ethernet address: 02:ff:a0:00:07:0b <5>epair1a: link state changed to UP <5>epair1b: link state changed to UP <6>epair1a: permanently promiscuous mode enabled <6>epair0a: permanently promiscuous mode enabled tap1: Ethernet address: 00:bd:4e:02:f9:01 <5>tap1: link state changed to UP <6>tap1: changing name to 'vbr0' <6>vbr0: permanently promiscuous mode enabled and current process points to ovs-vswitchd. --=20 You are receiving this mail because: You are the assignee for the bug.=