From owner-freebsd-bugs@freebsd.org  Wed Feb 22 05:53:48 2017
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 6A36DCE8124
 for <freebsd-bugs@mailman.ysv.freebsd.org>;
 Wed, 22 Feb 2017 05:53:48 +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 59C361664
 for <freebsd-bugs@FreeBSD.org>; Wed, 22 Feb 2017 05:53:48 +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 v1M5rm8W001249
 for <freebsd-bugs@FreeBSD.org>; Wed, 22 Feb 2017 05:53:48 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-bugs@FreeBSD.org
Subject: [Bug 217287] if_em: "Off by 8" error in network streams under
 -CURRENT as of roughly Feb 1
Date: Wed, 22 Feb 2017 05:53:48 +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: CURRENT
X-Bugzilla-Keywords: 
X-Bugzilla-Severity: Affects Only Me
X-Bugzilla-Who: jeff@baitis.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: 
Message-ID: <bug-217287-8-tiajtDZN4K@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-217287-8@https.bugs.freebsd.org/bugzilla/>
References: <bug-217287-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: Wed, 22 Feb 2017 05:53:48 -0000

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

--- Comment #1 from Jeffrey Baitis <jeff@baitis.net> ---
Upon further inspection, the WORKING kernel was built on Wed Jan 18:

$ uname -a
FreeBSD raid.baitis.home 12.0-CURRENT FreeBSD 12.0-CURRENT #18
4f888bf(drm-next): Wed Jan 18 14:31:26 UTC 2017=20=20=20=20
root@gauntlet:/usr/obj/usr/src/sys/GENERIC  amd64

So, changes in -CURRENT made after Jan 18 and before Feb 1 were likely to h=
ave
precipitated this problem.

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