From owner-freebsd-stable  Wed Jan 14 23:20:42 1998
Return-Path: <owner-freebsd-stable>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id XAA08104
          for stable-outgoing; Wed, 14 Jan 1998 23:20:42 -0800 (PST)
          (envelope-from owner-freebsd-stable)
Received: from pop.uniserve.com (pop.uniserve.com [204.244.156.3])
          by hub.freebsd.org (8.8.8/8.8.8) with SMTP id XAA08057
          for <freebsd-stable@freebsd.org>; Wed, 14 Jan 1998 23:20:14 -0800 (PST)
          (envelope-from tom@uniserve.com)
Received: from shell.uniserve.com [204.244.186.218] 
	by pop.uniserve.com with smtp (Exim 1.73 #1)
	id 0xsjb1-0003ZE-00; Wed, 14 Jan 1998 23:20:11 -0800
Date: Wed, 14 Jan 1998 23:20:07 -0800 (PST)
From: Tom <tom@uniserve.com>
To: Chris Caputo <ccaputo@alt.net>
cc: freebsd-stable@freebsd.org
Subject: Re: network performance problems (de0) (resend)
In-Reply-To: <Pine.BSI.3.93.980114091654.11982A-100000@baklava.alt.net>
Message-ID: <Pine.BSF.3.96.980114231821.15740D-100000@shell.uniserve.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Wed, 14 Jan 1998, Chris Caputo wrote:

>    de0: enabling 100baseTX port
>    de0: enabling Full Duplex 100baseTX port
...
> Any thoughts or suggestions on how to debug this further? 

  Check the network first.  Is the switch port that the machine is
connected to set to fullduplex?

  The de driver never used to be capable of fullduplex, so I suspect this
is the source of your problems.

> Chris

Tom