Date: Sun, 06 Feb 2011 23:54:49 +0100 From: "Ronald Klop" <ronald-freebsd8@klop.yi.org> To: pyunyh@gmail.com, sthaug@nethelp.no, "Ronald Klop" <ronald-freebsd8@klop.yi.org> Cc: freebsd-net@freebsd.org, rmacklem@uoguelph.ca Subject: Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS. Message-ID: <op.vqh69nx08527sy@212-123-145-58.ip.telfort.nl> In-Reply-To: <op.vpokw9c58527sy@pinky> References: <op.vpekz9uz8527sy@212-123-145-58.ip.telfort.nl> <708793006.292748.1295186099577.JavaMail.root@erie.cs.uoguelph.ca> <20110117005524.GA1305@michelle.cdnetworks.com> <20110118.093804.74673434.sthaug@nethelp.no> <op.vpokw9c58527sy@pinky>
next in thread | previous in thread | raw e-mail | index | archive | help
On Sat, 22 Jan 2011 00:01:47 +0100, Ronald Klop =20 <ronald-freebsd8@klop.yi.org> wrote: > On Tue, 18 Jan 2011 09:38:04 +0100, <sthaug@nethelp.no> wrote: > >>> > So, does anyone have an idea why the IP length field would be set t= o =20 >>> 0 >>> > for these TCP/IP packets? >>> > >>> > Here's some info from Ronald w.r.t. his hardware. (All I can think = =20 >>> of is >>> > that he could try disabling TSO, etc?) >>> > >>> > Thanks in advance for any help with this, rick >>> > >>> >>> It seems that issue came from TSO. Driver will set ip_len and >>> ip_sum field to 0 before passing the TCP segment to controller. >>> The failed length were 4446, 5858, 3034 and 4310 and the total >>> number of such frames are more than 35k within 90 seconds. Since >>> failed length 4310 is continuously repeated I guess there is edge >>> case where em(4) didn't free failed TCP segment for TSO. >>> I remember there was commit to HEAD(r217295) which could be related >>> with this issue. >> >> I'm seeing the same problem with Broadcom NetXtreme (bce) cards: >> >> bce0@pci0:3:0:0: class=3D0x020000 card=3D0x03421014 chip=3D0x16= 4c14e4 =20 >> rev=3D0x12 hdr=3D0x00 >> vendor =3D 'Broadcom Corporation' >> device =3D 'Broadcom NetXtreme II Gigabit Ethernet Adapter =20 >> (BCM5708)' >> class =3D network >> subclass =3D ethernet >> >> This is with 8.2-PRERELEASE. Turning off TSO (ifconfig bce0 -tso) >> removes the problem. >> >> Steinar Haug, Nethelp consulting, sthaug@nethelp.no >> _______________________________________________ >> freebsd-net@freebsd.org mailing list >> http://lists.freebsd.org/mailman/listinfo/freebsd-net >> To unsubscribe, send any mail to "freebsd-net-unsubscribe@freebsd.org" > > I tried -tso and -txcsum in various combinations, but it didn't solve =20 > the problem. I wil look for another brand of network card to try. But =20 > this has to wait till monday when I'm at the office again. I also used another network card (rl0) and it has the same problem with =20 NFS. I'm going to change some network cables to see if that helps. I have= =20 some hints that there might be something wrong with that. Ronald.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?op.vqh69nx08527sy>