From owner-freebsd-net@freebsd.org  Wed Nov 11 18:24:55 2015
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 9741FA2C12F
 for <freebsd-net@mailman.ysv.freebsd.org>;
 Wed, 11 Nov 2015 18:24:55 +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 822301F1C
 for <freebsd-net@FreeBSD.org>; Wed, 11 Nov 2015 18:24:55 +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 tABIOtec077957
 for <freebsd-net@FreeBSD.org>; Wed, 11 Nov 2015 18:24:55 GMT
 (envelope-from bugzilla-noreply@freebsd.org)
From: bugzilla-noreply@freebsd.org
To: freebsd-net@FreeBSD.org
Subject: [Bug 202680] Silent data corruption on em(4) interfaces
Date: Wed, 11 Nov 2015 18:24:55 +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.2-STABLE
X-Bugzilla-Keywords: IntelNetworking
X-Bugzilla-Severity: Affects Some People
X-Bugzilla-Who: yaniv@kundas.net
X-Bugzilla-Status: In Progress
X-Bugzilla-Priority: ---
X-Bugzilla-Assigned-To: freebsd-net@FreeBSD.org
X-Bugzilla-Target-Milestone: ---
X-Bugzilla-Flags: 
X-Bugzilla-Changed-Fields: 
Message-ID: <bug-202680-2472-bTMgcVEFGY@https.bugs.freebsd.org/bugzilla/>
In-Reply-To: <bug-202680-2472@https.bugs.freebsd.org/bugzilla/>
References: <bug-202680-2472@https.bugs.freebsd.org/bugzilla/>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: 7bit
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.20
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, 11 Nov 2015 18:24:55 -0000

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

--- Comment #22 from Yaniv Kunda <yaniv@kundas.net> ---
(In reply to Sean Bruno from comment #21)

I've set the value to -1 (in loader.conf), rebooted, and verified the new value
using sysctl.
In contrast to Dmitry, the problem happens for me even right after reboot, and
not only after some uptime.

Copied a bunch of files, and checked MD5's - one of them was wrong - so it is
probably not a symptom of what you described.

p.s. I think the importance of this issue should be raised from "Affects Some
People" - since part of this problem is quiet corruption, I assume a lot of
people with Intel adapters have corrupted data and do not even know.

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