Date: Wed, 11 Nov 2015 18:24:55 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-net@FreeBSD.org Subject: [Bug 202680] Silent data corruption on em(4) interfaces 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/>
next in thread | previous in thread | raw e-mail | index | archive | help
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.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-202680-2472-bTMgcVEFGY>