From owner-freebsd-stable@FreeBSD.ORG Fri Jan 15 23:51:04 2010 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 515FF106566C for ; Fri, 15 Jan 2010 23:51:04 +0000 (UTC) (envelope-from alan.bryan@yahoo.com) Received: from web50505.mail.re2.yahoo.com (web50505.mail.re2.yahoo.com [206.190.38.81]) by mx1.freebsd.org (Postfix) with SMTP id E7FFC8FC1A for ; Fri, 15 Jan 2010 23:51:03 +0000 (UTC) Received: (qmail 53799 invoked by uid 60001); 15 Jan 2010 23:51:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1263599460; bh=gZ6vav8Vaj8q/rXCZ/SY6rDDVsyno4ANHPRtPjiGW+M=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=HkSpNrswBbWUHvpJKtreNkbO+0G13SslycGlI62JhZArVlOE3RdZ8mngQGac9E8krgyC1k7oB4NLdvN9bwrUU71xpNjsAVb6DFxHf2ZBt/xybdNPva1OG3clah3ymG76HscYBO/I5LK8FCCGMeSHYxqgiI7VliOyhkP/ArlhK90= DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:Cc:In-Reply-To:MIME-Version:Content-Type:Content-Transfer-Encoding; b=by5j1PafzhTe8OB7+4J9lTIfCVadYZ0Kmx3iMIlc9Cy6e6tuqoR3+K5FKWnEI967v+Al2IKs/qsvjfws7iebd7A9kxibT0dEj8j80fuC1vJzimBef5yuXxwDNpGZyUpsvj5tkKodyyspxa668768vB6altq3gipLI4k2M4TMwNA=; Message-ID: <709036.53645.qm@web50505.mail.re2.yahoo.com> X-YMail-OSG: nydDp68VM1nclvAMfDIlbPGtd8wAqi3YHUuFR8KGtg8k8qSrktwWKFQQJTN033gV9U3QeZ1zhkvWy8i30u4uBEP4nGwF9QL8ZvMu8UR.AqduY3AG_vAb4nvelMoPKJizRZwWte67YQb8azdMYREhqXX5x5xJ56hV4lTC.d2x6L2_i6Cp3ewc.9an.2zRx1LDfQkkC4LDY5f4B8Awmtr12bv.S0sNhlKwxvVAUEMYQl049fmZ..9wyAC4JU.U1Lqc0PKK5WGzDZTi0.LTC797gz0l.3OR4eULbwKRIuaA4R71BypkNUie15Y0rpWulqekkjPW58Gq02bLpfszu0fRvuV8oI8y7xrHHsfD29cglvXZIWLFZFtL90A- Received: from [99.24.6.121] by web50505.mail.re2.yahoo.com via HTTP; Fri, 15 Jan 2010 15:51:00 PST X-Mailer: YahooMailClassic/9.0.20 YahooMailWebService/0.8.100.260964 Date: Fri, 15 Jan 2010 15:51:00 -0800 (PST) From: alan bryan To: pyunyh@gmail.com In-Reply-To: <20100115193235.GH1228@michelle.cdnetworks.com> MIME-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: quoted-printable Cc: freebsd-stable@freebsd.org Subject: Re: General problems with checksums (txcsum/rxcsum) on FreeBSD 8.0? 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: Fri, 15 Jan 2010 23:51:04 -0000 --- On Fri, 1/15/10, Pyun YongHyeon wrote:=0A=0A> From: = Pyun YongHyeon =0A> Subject: Re: General problems with ch= ecksums (txcsum/rxcsum) on FreeBSD 8.0?=0A> To: "alan bryan" =0A> Cc: freebsd-stable@freebsd.org=0A> Date: Friday, January 15, 2= 010, 11:32 AM=0A> On Fri, Jan 15, 2010 at 11:12:43AM=0A> -0800, alan bryan = wrote:=0A> > I just read a different thread about problems with=0A> checksu= ms on vge (and nfe in the replies).=0A> > =0A> > I'll just chime in here wi= th some more information - I=0A> have a couple other message threads going = about some weird=0A> high packet volumes on my new FreeBSD 8.0-Release NFS= =0A> server.=A0 I thought it might be an issue with the igb=0A> driver so I= put in a new card using em instead and got the=0A> exact same behavior.=A0= I'm currently sifting through a=0A> tcpdump in wireshark and there are all= sorts of messages in=0A> there about checksums being incorrect - both TCP = and=0A> UDP.=A0 This is for communications between this client=0A> machine = (FreeBSD 7.0-Release) and any of the 8.0 machines I=0A> have.=A0 The packet= s going to non-8.0 machines (at least=0A> so far) appear to be fine.=0A> > = =0A> > I'll defer to those who know more than I about the=0A> networking co= de, but is there perhaps an issue in general=0A> with the checksuming and n= ot specific to one card or driver=0A> - is that even possible?=A0 That's no= w 4 different=0A> drivers all with various checksum problem reports.=0A> > = =0A> > I'm going to be working on this all day today (and=0A> likely over t= he weekend) so if I can help by supplying=0A> information please let me kno= w what you need.=0A> > =0A> =0A> If you are seeing bad checksum reported by= =0A> tcpdump/wireshark for TX=0A> frames on checksum capable controller, it= 's normal. bpf(4)=0A> just=0A> sees TX frames before inserting checksum com= puted by=0A> hardware so=0A> tcpdump/wireshark reports invalid checksum. Yo= u can safely=0A> ignore=0A> that. If you want to verify whether sending hos= t generated=0A> correct=0A> checksum, you should capture the frame on recei= ve side. If=0A> tcpdump/=0A> wireshark reports bad checksummed frame on rec= eived frames=0A> it's=0A> real bad checksummed frame.=0A=0A=0AThanks for th= e help. After looking deeper into this issue today I'm now sure that I'm s= tuck in some NFS write/fail/retry loop. I'm still not sure if the trigger = to get to that state is NFS, ZFS, or networking code.=0A=0ATo try to get mo= re information to act on, I'm going to change my client mount options and s= ee what happens.=0A=0AThanks everyone.=0A=0A=0A