From owner-freebsd-bugs@freebsd.org Thu Jun 1 10:41:08 2017 Return-Path: Delivered-To: freebsd-bugs@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 7CB13AF99BF for ; Thu, 1 Jun 2017 10:41:08 +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 62A4774C7F for ; Thu, 1 Jun 2017 10:41:08 +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 v51Af8GQ095355 for ; Thu, 1 Jun 2017 10:41:08 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-bugs@FreeBSD.org Subject: [Bug 219703] System freeze when creating bridge over vlan over lagg over ixgbe Date: Thu, 01 Jun 2017 10:41:08 +0000 X-Bugzilla-Reason: AssignedTo X-Bugzilla-Type: new 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: topical@gmx.net X-Bugzilla-Status: New X-Bugzilla-Resolution: X-Bugzilla-Priority: --- X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org X-Bugzilla-Flags: X-Bugzilla-Changed-Fields: bug_id short_desc product version rep_platform op_sys bug_status bug_severity priority component assigned_to reporter Message-ID: 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-bugs@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Bug reports List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 01 Jun 2017 10:41:08 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D219703 Bug ID: 219703 Summary: System freeze when creating bridge over vlan over lagg over ixgbe Product: Base System Version: 11.0-RELEASE Hardware: amd64 OS: Any Status: New Severity: Affects Some People Priority: --- Component: kern Assignee: freebsd-bugs@FreeBSD.org Reporter: topical@gmx.net I have an Intel 82599ES card, using standard ixgbe driver (no special parameters). The two ports are combined into a lagg. For virtual machines, a vlan is created on the lagg. This vlan is connected to a bridge. behyve machines shall be connected to this bridge. In my case, there are 3 vlans a= nd bridges, but the problem occurs already on creating the 1st vlan/bridge. The network setup is: cloned_interfaces=3D"lagg0" ifconfig_ix0=3D"up mtu 9000 -lro" ifconfig_ix1=3D"up mtu 9000 -lro" ifconfig_lagg0=3D"laggproto lacp laggport ix0 laggport ix1 10.0.10.17/24" defaultrouter=3D"10.0.10.1" vm-bhyve creates bridges according to following config: switch_list=3D"br4 br7 br8" vlan_br4=3D"4" ports_br4=3D"lagg0" vlan_br7=3D"7" ports_br7=3D"lagg0" vlan_br8=3D"8" ports_br8=3D"lagg0" As soon as vm-bhyve create the first bridge and vlan, the system freezes ha= rd. Sadly, installing a debug kernel doesn't help; the magic sysrequest key combination is ignored. I extracted the network commands executed by vm-bhyve startup script: ifconfig bridge create ifconfig bridge0 description something up ifconfig vlan create <-- system freezes here --> ifconfig vlan0 vlandev lagg0 vlan 4 description something up ifconfig bridge0 addm vlan0 Inserting "sleep 1" after "ifconfig vlan create" seems to fix it. Even minor delays (e.g. a simple echo to the EFI console after each command) seem to f= ix it. Without the delay, changes are about 90% that the system freezes. This problem seems to occur only with the ixgbe driver. In previous tests w= ith a NetXtreme II BCM57810 card and the bxe driver everything worked fine, tho= ugh the bxe driver seems to lack hardware vlan support which was the reason to replace it with the Intel card. It looks like a nasty race condition and I'm not really happy with patching vm-bhyve, hoping that the (blindly inserted) workaround does the trick.=20 The server is a DL380 Gen9. The network cards is an off the shelf Intel 825= 99ES (i.e. not a HP branded one). --=20 You are receiving this mail because: You are the assignee for the bug.=