From owner-freebsd-current Wed Dec 22 19:30:22 1999 Delivered-To: freebsd-current@freebsd.org Received: from mailman.cs.ucla.edu (Mailman.CS.UCLA.EDU [131.179.128.30]) by hub.freebsd.org (Postfix) with ESMTP id 417B31586A for ; Wed, 22 Dec 1999 19:29:48 -0800 (PST) (envelope-from scottm@CS.UCLA.EDU) Received: from mordred.cs.ucla.edu (mordred.cs.ucla.edu [131.179.192.128]) by mailman.cs.ucla.edu (8.9.1/UCLACS-5.0) with ESMTP id TAA18058; Wed, 22 Dec 1999 19:30:27 -0800 (PST) Received: from localhost (localhost.cs.ucla.edu [127.0.0.1]) by mordred.cs.ucla.edu (8.9.3/UCLACS-5.0) with ESMTP id TAA00830; Tue, 30 Nov 1999 19:29:45 -0800 (PST) Date: Tue, 30 Nov 1999 19:29:44 -0800 (PST) From: "B. Scott Michel" To: Jonathan Lemon Cc: Matthew Dillon , Brad Knowles , Joe Abley , Poul-Henning Kamp , Garrett Wollman , freebsd-current@freebsd.org Subject: Re: Odd TCP glitches in new currents In-Reply-To: <19991222141208.07062@right.PCS> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Wed, 22 Dec 1999, Jonathan Lemon wrote: > On Dec 12, 1999 at 11:37:42AM -0800, Matthew Dillon wrote: > I had a Netgear FS509 switch here that would eat packets transmitted > through the GigE port under certain conditions. Netgear shipped me > a new one, and I've been happy with it, until the same problem started > happening again this morning. There's some oddities in the 3.3 and 3.4 kernels as well -- I've actually nailed down the plexicity and speed on both the Accellar and my humble PC, and yet, I'm looking at weird TCP lockups from time to time. Mostly seems to be related to NFSv3, but will also happen when doing cvsup. There's no magic number of how many bytes are queued waiting to go out the interface. And it seems to be limited to specific connections, i.e. an NFS TCP connection can be jammed and yet I can be happily talking to cvsup3 doing an update. The interface in question is a NetGear: pn0: <82c169 PNIC 10/100BaseTX> rev 0x20 int a irq 11 on pci0.9.0 What is odd is that the output error metric from netstat -in monotonically increases. Yes, I could post my configuration, etc., and I could go back to running -current, but I have a PhD to make progress on. And I'm willing to wait to try out the consolidated 2x040/PNIC driver when 4.0 finally rolls out. -scooter To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message