Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-02-08 Thread Ronald Klop
On Mon, 07 Feb 2011 01:22:36 +0100, Pyun YongHyeon pyu...@gmail.com wrote: On Sun, Feb 06, 2011 at 11:54:49PM +0100, Ronald Klop wrote: On Sat, 22 Jan 2011 00:01:47 +0100, Ronald Klop ronald-freeb...@klop.yi.org wrote: On Tue, 18 Jan 2011 09:38:04 +0100, sth...@nethelp.no wrote: So, does

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-02-06 Thread Ronald Klop
On Sat, 22 Jan 2011 00:01:47 +0100, Ronald Klop ronald-freeb...@klop.yi.org wrote: On Tue, 18 Jan 2011 09:38:04 +0100, sth...@nethelp.no wrote: So, does anyone have an idea why the IP length field would be set to 0 for these TCP/IP packets? Here's some info from Ronald w.r.t. his

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-02-06 Thread Pyun YongHyeon
On Sun, Feb 06, 2011 at 11:54:49PM +0100, Ronald Klop wrote: On Sat, 22 Jan 2011 00:01:47 +0100, Ronald Klop ronald-freeb...@klop.yi.org wrote: On Tue, 18 Jan 2011 09:38:04 +0100, sth...@nethelp.no wrote: So, does anyone have an idea why the IP length field would be set to 0 for

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-21 Thread Ronald Klop
On Tue, 18 Jan 2011 09:38:04 +0100, sth...@nethelp.no wrote: So, does anyone have an idea why the IP length field would be set to 0 for these TCP/IP packets? Here's some info from Ronald w.r.t. his hardware. (All I can think of is that he could try disabling TSO, etc?) Thanks in

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-20 Thread Brandon Gooch
On Wed, Jan 19, 2011 at 5:59 PM, Pyun YongHyeon pyu...@gmail.com wrote: On Tue, Jan 18, 2011 at 07:35:30PM +0100, sth...@nethelp.no wrote: I'm seeing the same problem with Broadcom NetXtreme (bce) cards: bce0@pci0:3:0:0:        class=0x02 card=0x03421014 chip=0x164c14e4 rev=0x12

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-19 Thread Pyun YongHyeon
On Tue, Jan 18, 2011 at 07:35:30PM +0100, sth...@nethelp.no wrote: I'm seeing the same problem with Broadcom NetXtreme (bce) cards: bce0@pci0:3:0:0:class=0x02 card=0x03421014 chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device =

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-18 Thread sthaug
So, does anyone have an idea why the IP length field would be set to 0 for these TCP/IP packets? Here's some info from Ronald w.r.t. his hardware. (All I can think of is that he could try disabling TSO, etc?) Thanks in advance for any help with this, rick It seems that issue

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-18 Thread Pyun YongHyeon
On Tue, Jan 18, 2011 at 09:38:04AM +0100, sth...@nethelp.no wrote: So, does anyone have an idea why the IP length field would be set to 0 for these TCP/IP packets? Here's some info from Ronald w.r.t. his hardware. (All I can think of is that he could try disabling TSO, etc?)

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-18 Thread sthaug
I'm seeing the same problem with Broadcom NetXtreme (bce) cards: bce0@pci0:3:0:0:class=0x02 card=0x03421014 chip=0x164c14e4 rev=0x12 hdr=0x00 vendor = 'Broadcom Corporation' device = 'Broadcom NetXtreme II Gigabit Ethernet Adapter (BCM5708)' class

bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-16 Thread Rick Macklem
Ronald has reported having a problem with the FreeBSD NFS client using 8.2-prerelease. I've redirected it here, since it looks like there is a TCP/IP issue that is causing it. These are the links to the dumps: http://klop.ws/~ronald/nfs-problem/procstat.nolockd

Re: bogus 0 len IP packet, was: Hang in VOP_LOCK1_APV on 8-STABLE with NFS.

2011-01-16 Thread Pyun YongHyeon
On Sun, Jan 16, 2011 at 08:54:59AM -0500, Rick Macklem wrote: Ronald has reported having a problem with the FreeBSD NFS client using 8.2-prerelease. I've redirected it here, since it looks like there is a TCP/IP issue that is causing it. These are the links to the dumps: