From owner-freebsd-net@FreeBSD.ORG Sun Jan 18 19:15:51 2015 Return-Path: Delivered-To: freebsd-net@FreeBSD.org Received: from mx1.freebsd.org (mx1.freebsd.org [8.8.178.115]) (using TLSv1.2 with cipher AECDH-AES256-SHA (256/256 bits)) (No client certificate requested) by hub.freebsd.org (Postfix) with ESMTPS id 355A4BEE for ; Sun, 18 Jan 2015 19:15:51 +0000 (UTC) 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 042692C7 for ; Sun, 18 Jan 2015 19:15:51 +0000 (UTC) Received: from bugs.freebsd.org ([127.0.1.118]) by kenobi.freebsd.org (8.14.9/8.14.9) with ESMTP id t0IJFoEL092911 for ; Sun, 18 Jan 2015 19:15:50 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 195859] Reproduceble panic with VIMAGE + if_bridge Date: Sun, 18 Jan 2015 19:15:50 +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-CURRENT X-Bugzilla-Keywords: X-Bugzilla-Severity: Affects Only Me X-Bugzilla-Who: rodrigc@FreeBSD.org X-Bugzilla-Status: New X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org X-Bugzilla-Target-Milestone: --- X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: Message-ID: In-Reply-To: References: Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit 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.18-1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 18 Jan 2015 19:15:51 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=195859 --- Comment #6 from Craig Rodrigues --- Herbert found by creating VNET jails and then stopping them, he could reproduce the problem. Here are the steps he used to reproduce the problem: /etc/rc.conf: hostname="beastie.home.lan" ifconfig_em0="inet 192.168.1.25 netmask 0xffff0000" defaultrouter="192.168.1.255" cloned_interfaces="bridge0" ifconfig_bridge0="inet 10.0.0.1 netmask 0xff000000" sshd_enable="YES" fsck_y_enable="YES" background_fsck="NO" syslogd_flags="-ss" gateway_enable="YES" pf_enable="NO" pflog_enable="NO" jail_enable="NO" jail_list="jail01 jail02 jail03 jail04" devfs_load_rulesets="YES" /etc/jail.conf: jail01 { name = "jail01"; path = /usr/local/jails/jail01; mount.devfs; host.hostname = jail01.home.lan; vnet = "new"; vnet.interface = "epair0b"; persist; exec.prestart = "ifconfig epair0 create"; exec.prestart += "ifconfig bridge0 addm epair0a"; exec.prestart += "ifconfig epair0a up"; exec.start = ""; #exec.start = "/bin/sh /etc/rc"; exec.poststart = "jexec $name ifconfig epair0b 10.0.0.10 netmask 255.0.0.0 up"; exec.poststart += "jexec $name route add default 10.0.0.1"; exec.poststart += "jexec $name sh /etc/rc"; exec.stop = "/bin/sh /etc/rc.shutdown"; exec.poststop = "ifconfig bridge0 deletem epair0a"; exec.poststop += "ifconfig epair0a destroy"; } /etc/rc.conf in jail01: hostname="jail01.home.lan" sshd_enable="YES" sendmail_enable="NONE" Starting jail with "/etc/rc.d/jail onestart jail01" or "jail -c jail01". Stopping jail with "/etc/rc.d/jail onestop jail01" or "jail -r jail01". -- You are receiving this mail because: You are the assignee for the bug.