From owner-freebsd-net@freebsd.org  Wed Mar 15 02:40:17 2017
Return-Path: <owner-freebsd-net@freebsd.org>
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 92F80D0A86A
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed, 15 Mar 2017 02:40: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 82FD2149E
 for <freebsd-net@FreeBSD.org>; Wed, 15 Mar 2017 02:40:17 +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 v2F2eH9X078485
 for <freebsd-net@FreeBSD.org>; Wed, 15 Mar 2017 02:40:17 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: Wed, 15 Mar 2017 02:40:17 +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: <bug-217606-2472-iELuwV9j0U@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-217606-2472@https.bugs.freebsd.org/bugzilla/>
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 <freebsd-net.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-net/>
List-Post: <mailto:freebsd-net@freebsd.org>
List-Help: <mailto:freebsd-net-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-net>,
 <mailto:freebsd-net-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Wed, 15 Mar 2017 02:40:17 -0000

https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D217606

--- Comment #5 from Kristof Provost <kp@freebsd.org> ---
Right, that confirms we're not dealing with a memory leak.
I've had a quick look at the ixgbe/if_ix code. It resets the hardware if you
bring it down, so one possible explanation is that there's something wrong =
in
the ix driver itself, which causes this.

I might be missing it, but I don't see anything in the bridge code that
responds to bringing a member interface up/down, so right now I consider th=
e ix
driver to be the most likely suspect. I'm afraid I don't know anything about
that hardware.

It might be useful to have a look in dmesg to see if there's anything obvio=
us,
as well as list the exact hardware you have.

--=20
You are receiving this mail because:
You are the assignee for the bug.=