From owner-freebsd-stable@FreeBSD.ORG Mon Oct 10 21:16:36 2011 Return-Path: Delivered-To: freebsd-stable@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 135061065674; Mon, 10 Oct 2011 21:16:36 +0000 (UTC) (envelope-from louie@transsys.com) Received: from droid.transsys.com (droid.transsys.com [144.202.0.11]) by mx1.freebsd.org (Postfix) with ESMTP id E04E98FC15; Mon, 10 Oct 2011 21:16:35 +0000 (UTC) Received: from lmamakos-imac-wired.private.transsys.com (pa-67-234-243-231.dhcp.embarqhsd.net [67.234.243.231]) (using TLSv1 with cipher AES128-SHA (128/128 bits)) (No client certificate requested) (Authenticated sender: louie) by droid.transsys.com (Postfix) with ESMTPSA id 6279B64F; Mon, 10 Oct 2011 16:57:22 -0400 (EDT) Mime-Version: 1.0 (Apple Message framework v1244.3) Content-Type: text/plain; charset=iso-8859-1 From: Louis Mamakos In-Reply-To: <4E933BBF.6070209@lerctr.org> Date: Mon, 10 Oct 2011 16:57:21 -0400 Content-Transfer-Encoding: quoted-printable Message-Id: <36C97D31-5D01-4AC2-8E48-9A8B04B98F91@transsys.com> References: <201110101147.30558.jhb@freebsd.org> <4E933BBF.6070209@lerctr.org> To: Larry Rosenman X-Mailer: Apple Mail (2.1244.3) Cc: freebsd-stable@freebsd.org, John Baldwin Subject: Re: rsync corrupted MAC X-BeenThere: freebsd-stable@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Production branch of FreeBSD source code List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 10 Oct 2011 21:16:36 -0000 On Oct 10, 2011, at 2:38 PM, Larry Rosenman wrote: > On 10/10/2011 10:47 AM, John Baldwin wrote: >> On Sunday, October 09, 2011 5:06:26 pm Larry Rosenman wrote: >>> Any ideas on which side or what might be broke here? >>>=20 >>> ler/MAIL-ARCHIVE/2008/12/INBOX >>> Corrupted MAC on input. >>> Disconnecting: Packet corrupt >>> rsync: connection unexpectedly closed (33845045 bytes received so = far) >> [receiver] >>> rsync error: error in rsync protocol data stream (code 12) at = io.c(605) >> [receiver=3D3.0.9] >>> rsync: connection unexpectedly closed (1450 bytes received so far) >> [generator] >>> rsync error: unexplained error (code 255) at io.c(605) = [generator=3D3.0.9] >> I've had somewhat similar issues (ssh getting corruption in its data = stream) >> when a NIC in my netbook was corrupting packet data when it ran at 1G = (it >> worked fine at 10/100). Pyun eventually fixed the issue by applying = enough >> workarounds (it was likely a hardware bug in the NIC's chipset). = However, it >> wasn't easy to debug unfortunately. :( >>=20 > Any ideas on where to start? >=20 > from the 8.2 box (tbh.lerctr.org in the script): >=20 > 8.2->PIX->Provider->Internet->Motorola SBG6580 (Time-Warner)->Trendnet = TEG-160WS Gig switch->9.0 box (borg.lerctr.org). >=20 > So, where do I start? I'd turn off IP / TCP / UDP checksum offloading on your NIC if it = supports it, and see if you are getting network layer checksum errors. = If the IP checksum is wrong, then it happened on the last hops between = the NIC and memory or across the previous network hop.