From owner-freebsd-bugs@freebsd.org  Sat Nov 26 20:14:18 2016
Return-Path: <owner-freebsd-bugs@freebsd.org>
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 39ACAC57B02
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Sat, 26 Nov 2016 20:14:18 +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 28CF98E6
 for <freebsd-bugs@FreeBSD.org>; Sat, 26 Nov 2016 20:14:18 +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 uAQKEH3R024317
 for <freebsd-bugs@FreeBSD.org>; Sat, 26 Nov 2016 20:14:18 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 207633] bce0: Discard frame w/o leading ethernet header (len 0
 pkt len 0) - pfSense 2.2.6 and 2.3 Beta
Date: Sat, 26 Nov 2016 20:14:18 +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: 10.1-RELEASE
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: parwok@gmail.com
X-Bugzilla-Status: Closed
X-Bugzilla-Resolution: Not A Bug
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-bugs@FreeBSD.org
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: resolution
Message-ID: <bug-207633-8-Gxp1SmSsXm@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-207633-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-207633-8@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-bugs@freebsd.org
X-Mailman-Version: 2.1.23
Precedence: list
List-Id: Bug reports <freebsd-bugs.freebsd.org>
List-Unsubscribe: <https://lists.freebsd.org/mailman/options/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-bugs/>
List-Post: <mailto:freebsd-bugs@freebsd.org>
List-Help: <mailto:freebsd-bugs-request@freebsd.org?subject=help>
List-Subscribe: <https://lists.freebsd.org/mailman/listinfo/freebsd-bugs>,
 <mailto:freebsd-bugs-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 26 Nov 2016 20:14:18 -0000

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

Matt <parwok@gmail.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
         Resolution|FIXED                       |Not A Bug

--- Comment #3 from Matt <parwok@gmail.com> ---
I should note that it was a false positive on the fix being related to anyt=
hing
within FreeBSD or pfSense, for the most part:

After using pci-stub on the Linux host for the two NIC's in question, which
prevents the host from loading firmware for the cards (previously wasn't
possible for a variety of reasons), coupled with the wiki entry below, I se=
em
to have this issue no longer.

https://doc.pfsense.org/index.php/Tuning_and_Troubleshooting_Network_Cards#=
Broadcom_bce.284.29_Cards

That saves me buying a dual Intel NIC. I hope this information can help oth=
ers
with similar issues.

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