From owner-freebsd-stable  Thu Jan 15 03:03:53 1998
Return-Path: <owner-freebsd-stable>
Received: (from daemon@localhost)
          by hub.freebsd.org (8.8.8/8.8.8) id DAA03354
          for stable-outgoing; Thu, 15 Jan 1998 03:03:53 -0800 (PST)
          (envelope-from owner-freebsd-stable)
Received: from baklava.alt.net (root@baklava.alt.net [207.14.113.9])
          by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id DAA03234
          for <freebsd-stable@FreeBSD.ORG>; Thu, 15 Jan 1998 03:02:29 -0800 (PST)
          (envelope-from ccaputo@alt.net)
Received: from baklava.alt.net (ccaputo@baklava.alt.net [207.14.113.9]) by baklava.alt.net (8.8.5/8.7.3) with SMTP id CAA23655; Thu, 15 Jan 1998 02:41:25 -0800 (PST)
Date: Thu, 15 Jan 1998 02:41:24 -0800 (PST)
From: Chris Caputo <ccaputo@alt.net>
To: David Greenman <dg@root.com>
cc: freebsd-stable@FreeBSD.ORG
Subject: Re: network performance problems (de0) (resend) 
In-Reply-To: <199801151017.CAA13226@implode.root.com>
Message-ID: <Pine.BSI.3.93.980115023520.22831E-100000@baklava.alt.net>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-stable@FreeBSD.ORG
X-Loop: FreeBSD.org
Precedence: bulk

On Thu, 15 Jan 1998, David Greenman wrote:
>    Nonetheless, the 'de' driver has historically been broken for full
> duplex operation and Tom's suggestion is right on the money. I'd try
> setting the device or the switch or both to half duplex to see if the
> problem goes away. 

Respectfully, I wonder if this is because people didn't know the link
settings necessary to activate it on 2.1-STABLE.  On 2.1 we are using

ifconfig_de0="inet x.x.x.x link0 link1 link2 netmask x.x.x.x"

in /etc/sysconfig and it is working like a charm.  The switch reports no
corrupt packets and netstat reports no collisions (implying nominal full
duplex operation). 

I'll keep messing around with 2.2-STABLE and report anything that might be
useful.

Thanks,
Chris