Date: Tue, 18 Dec 2001 18:29:06 -0500 From: "Michael Meltzer" <mjm@michaelmeltzer.com> To: <freebsd-stable@FreeBSD.ORG> Subject: bad tcp cksum/em intel/1000 pro driver Message-ID: <00da01c1881b$c925d980$34f820c0@ix1x1000>
next in thread | raw e-mail | index | archive | help
[-- Attachment #1 --] I am trying trying to track down a problem with jumbo frames/NFS/rpc.lockd but in stating the tracking I noticed "bad tcp checksum" showing in the tcpdump "-s0 -e -vvv -i em0"(see below), the checksum does not seem to be effecting anything but it is standing out like a read flag. is it a problem?????? BTW I working on a good tcpdump for the problem with NFS/rpc.lockd MJM 18:19:27.252631 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.1270376597 > nf s1-nfs.nfs: 1448 proc-1514986542 (DF) (ttl 64, id 53573, len 1500) 18:19:27.252677 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1 019: . [bad tcp cksum 3682!] 125009:125009(0) ack 22888833 win 1036 <nop,nop,tim estamp 1417206 671470> (DF) (ttl 64, id 33620, len 52) 18:19:27.252694 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1 019: . [bad tcp cksum e676!] 125009:125009(0) ack 22891729 win 1036 <nop,nop,tim estamp 1417206 671470> (DF) (ttl 64, id 33621, len 52) 18:19:27.252704 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1 019: . [bad tcp cksum 3e71!] 125009:125009(0) ack 22893177 win 1036 <nop,nop,tim estamp 1417206 671470> (DF) (ttl 64, id 33622, len 52) 18:19:27.252746 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.635606901 > nfs 1-nfs.nfs: 1448 proc-4267978179 (DF) (ttl 64, id 53574, len 1500) 18:19:27.252755 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.780347664 > nfs 1-nfs.nfs: 1448 proc-1427070815 (DF) (ttl 64, id 53575, len 1500) 18:19:27.252768 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.4175493587 > nf s1-nfs.nfs: 1448 proc-2454832600 (DF) (ttl 64, id 53576, len 1500) 18:19:27.252797 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1 019: . [bad tcp cksum ee65!] 125009:125009(0) ack 22896073 win 1036 <nop,nop,tim estamp 1417206 671470> (DF) (ttl 64, id 33623, len 52) 18:19:27.252806 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1 019: . [bad tcp cksum 4660!] 125009:125009(0) ack 22897521 win 1036 <nop,nop,tim estamp 1417206 671470> (DF) (ttl 64, id 33624, len 52) [-- Attachment #2 --] <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML><HEAD> <META http-equiv=Content-Type content="text/html; charset=iso-8859-1"> <META content="MSHTML 6.00.2600.0" name=GENERATOR> <STYLE></STYLE> </HEAD> <BODY bgColor=#ffffff> <DIV><FONT face=Arial size=2>I am trying trying to track down a problem with jumbo frames/NFS/rpc.lockd but in stating the tracking I noticed "bad tcp checksum" showing in the tcpdump "-s0 -e -vvv -i em0"(see below), the checksum does not seem to be effecting anything</FONT></DIV> <DIV><FONT face=Arial size=2> but it is standing out like a read flag. is it a problem?????? BTW I working on a good tcpdump for the problem with NFS/rpc.lockd</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>MJM</FONT></DIV> <DIV><FONT face=Arial size=2></FONT> </DIV> <DIV><FONT face=Arial size=2>18:19:27.252631 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.1270376597 > nf<BR>s1-nfs.nfs: 1448 proc-1514986542 (DF) (ttl 64, id 53573, len 1500)<BR>18:19:27.252677 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1<BR>019: . [bad tcp cksum 3682!] 125009:125009(0) ack 22888833 win 1036 <nop,nop,tim<BR>estamp 1417206 671470> (DF) (ttl 64, id 33620, len 52)<BR>18:19:27.252694 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1<BR>019: . [bad tcp cksum e676!] 125009:125009(0) ack 22891729 win 1036 <nop,nop,tim<BR>estamp 1417206 671470> (DF) (ttl 64, id 33621, len 52)<BR>18:19:27.252704 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1<BR>019: . [bad tcp cksum 3e71!] 125009:125009(0) ack 22893177 win 1036 <nop,nop,tim<BR>estamp 1417206 671470> (DF) (ttl 64, id 33622, len 52)<BR>18:19:27.252746 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.635606901 > nfs<BR>1-nfs.nfs: 1448 proc-4267978179 (DF) (ttl 64, id 53574, len 1500)<BR>18:19:27.252755 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.780347664 > nfs<BR>1-nfs.nfs: 1448 proc-1427070815 (DF) (ttl 64, id 53575, len 1500)<BR>18:19:27.252768 0:3:ba:6:55:50 0:3:47:71:e9:11 ip 1514: maya-nfs.4175493587 > nf<BR>s1-nfs.nfs: 1448 proc-2454832600 (DF) (ttl 64, id 53576, len 1500)<BR>18:19:27.252797 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1<BR>019: . [bad tcp cksum ee65!] 125009:125009(0) ack 22896073 win 1036 <nop,nop,tim<BR>estamp 1417206 671470> (DF) (ttl 64, id 33623, len 52)<BR>18:19:27.252806 0:3:47:71:e9:11 0:3:ba:6:55:50 ip 66: nfs1-nfs.nfsd > maya-nfs.1<BR>019: . [bad tcp cksum 4660!] 125009:125009(0) ack 22897521 win 1036 <nop,nop,tim<BR>estamp 1417206 671470> (DF) (ttl 64, id 33624, len 52)</FONT></DIV></BODY></HTML>
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?00da01c1881b$c925d980$34f820c0>