From owner-freebsd-hackers Thu Jan 2 19:05:57 1997 Return-Path: Received: (from root@localhost) by freefall.freebsd.org (8.8.4/8.8.4) id TAA24626 for hackers-outgoing; Thu, 2 Jan 1997 19:05:57 -0800 (PST) Received: from root.com (implode.root.com [198.145.90.17]) by freefall.freebsd.org (8.8.4/8.8.4) with ESMTP id TAA24621 for ; Thu, 2 Jan 1997 19:05:52 -0800 (PST) Received: from localhost (localhost [127.0.0.1]) by root.com (8.7.6/8.6.5) with SMTP id TAA18683; Thu, 2 Jan 1997 19:05:26 -0800 (PST) Message-Id: <199701030305.TAA18683@root.com> X-Authentication-Warning: implode.root.com: Host localhost [127.0.0.1] didn't use HELO protocol To: robin@intercore.com (Robin Cutshaw) cc: hackers@freebsd.org Subject: Re: tcp problems with 2.1.6.1 In-reply-to: Your message of "Thu, 02 Jan 1997 14:52:09 EST." <199701021952.OAA08144@intercore.com> From: David Greenman Reply-To: dg@root.com Date: Thu, 02 Jan 1997 19:05:26 -0800 Sender: owner-hackers@freebsd.org X-Loop: FreeBSD.org Precedence: bulk >Recently while supping the XFree86 tree, I noticed that one of my boxes >was having timeout problems. It's a P90/64MB/FreeBSD-2.1.6.1 box. I >watched the ethernet and noticed a large number of packets received >that got no ack from the FreeBSD box. This caused a large number >of retransmits. The other boxes on this net don't seem to have >this problem so I thought I'd ask the FreeBSD group if anyone has >seen anything like this. You need to mention what type of ethernet card you're using. The bug isn't likely with the TCP code, but rather a device driver or hardware problem. -DG David Greenman Core-team/Principal Architect, The FreeBSD Project