From owner-freebsd-hackers  Mon Aug 11 18:47:36 1997
Return-Path: <owner-freebsd-hackers>
Received: (from root@localhost)
          by hub.freebsd.org (8.8.5/8.8.5) id SAA15624
          for hackers-outgoing; Mon, 11 Aug 1997 18:47:36 -0700 (PDT)
Received: from misery.sdf.com (misery.sdf.com [204.244.210.193])
          by hub.freebsd.org (8.8.5/8.8.5) with SMTP id SAA15618
          for <hackers@freebsd.org>; Mon, 11 Aug 1997 18:47:33 -0700 (PDT)
Received: from tom by misery.sdf.com with smtp (Exim 1.62 #1)
	id 0wy621-0002Hc-00; Mon, 11 Aug 1997 18:45:57 -0700
Date: Mon, 11 Aug 1997 18:45:56 -0700 (PDT)
From: Tom Samplonius <tom@sdf.com>
To: Ben Black <black@zen.cypher.net>
cc: David Greenman <dg@root.com>, hackers@freebsd.org
Subject: Re: fxp driver full duplex packet loss problem 
In-Reply-To: <Pine.BSF.3.95q.970811173800.8572B-100000@misery.sdf.com>
Message-ID: <Pine.BSF.3.95q.970811184359.8572D-100000@misery.sdf.com>
MIME-Version: 1.0
Content-Type: TEXT/PLAIN; charset=US-ASCII
Sender: owner-freebsd-hackers@freebsd.org
X-Loop: FreeBSD.org
Precedence: bulk


On Mon, 11 Aug 1997, Tom Samplonius wrote:

> 
> On Mon, 11 Aug 1997, Ben Black wrote:
> 
> > a good indication of this duplex mismatch is a sudden appearance of FCS 
> > errors and Runts on the cisco interface.  
> 
>   When I switch full duplex on the FreeBSD server, the switch starts
> recording late collision errors on that port (a 10BT port on a Cat 1900).
> I'm not sure what this means.
> 
> Tom

  Actually I do know (now) what that means.  The switch (which is supposed
to auto-negotiate and has no manual setting) is set to half, and card is
set to full.

  I'm guessing the switch doesn't understand devices switching from half
to full on the fly, and only detects this on intial connect.  I will try
turning full duplex on, and them plug it into a different port.

Tom