From owner-freebsd-net@freebsd.org Thu Sep 14 21:23: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 F3CE3E0CF01 for ; Thu, 14 Sep 2017 21:23:16 +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 E2E4C6A404 for ; Thu, 14 Sep 2017 21:23: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 v8ELNFph080681 for ; Thu, 14 Sep 2017 21:23:16 GMT (envelope-from bugzilla-noreply@freebsd.org) From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 217606] Bridge stops working after some days Date: Thu, 14 Sep 2017 21:23:15 +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: kp@freebsd.org 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: Thu, 14 Sep 2017 21:23:17 -0000 https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606 --- Comment #22 from Kristof Provost --- (In reply to punkt.de Hosting Team from comment #21) That should tell us if the problem is specific to the ix cards, or not. If = it's not it's most likely a bridge issue. It might be worth taking a look at what happens in the bridge code once it'= s in that state: sudo dtrace -n fbt:if_bridge:: That looks like this, on my nearly idle bridge: dtrace: description 'fbt:if_bridge::' matched 108 probes CPU ID FUNCTION:NAME 6 63915 bridge_transmit:entry 6 63814 bridge_broadcast:entry 6 63824 bridge_enqueue:entry 6 63825 bridge_enqueue:return 6 63824 bridge_enqueue:entry 6 63825 bridge_enqueue:return 6 63815 bridge_broadcast:return 6 63916 bridge_transmit:return 3 63915 bridge_transmit:entry ... --=20 You are receiving this mail because: You are the assignee for the bug.=