From owner-freebsd-stable@FreeBSD.ORG  Mon May 16 13:23:32 2005
Return-Path: <owner-freebsd-stable@FreeBSD.ORG>
Delivered-To: freebsd-stable@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP id D974616A4CE
	for <freebsd-stable@freebsd.org>;
	Mon, 16 May 2005 13:23:32 +0000 (GMT)
Received: from rproxy.gmail.com (rproxy.gmail.com [64.233.170.197])
	by mx1.FreeBSD.org (Postfix) with ESMTP id 747CE43D1F
	for <freebsd-stable@freebsd.org>;
	Mon, 16 May 2005 13:23:32 +0000 (GMT)
	(envelope-from jcagle@gmail.com)
Received: by rproxy.gmail.com with SMTP id a41so700418rng
	for <freebsd-stable@freebsd.org>;
	Mon, 16 May 2005 06:23:32 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
	s=beta; d=gmail.com;
	h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
	b=ZAGl9Kol6fgivITtEZqIfr+gf5JCmCzvSofCxcRTCk9rWIVyPuyfmvMVddJqjvV0jwE/L70VDyOugjfT4aLMiOjLpu3mqiE/nl+o1e309+Ibg0GjQfxjw25DYZmOa2ANpxCMaupZ7E8oATtIjw1Vw7f1/PtceEtunNg13XHIC7o=
Received: by 10.38.152.1 with SMTP id z1mr2917206rnd;
        Mon, 16 May 2005 06:23:32 -0700 (PDT)
Received: by 10.38.90.72 with HTTP; Mon, 16 May 2005 06:23:31 -0700 (PDT)
Message-ID: <6863f0c905051606236955420f@mail.gmail.com>
Date: Mon, 16 May 2005 08:23:31 -0500
From: jmc <jcagle@gmail.com>
To: Doug White <dwhite@gumbysoft.com>
In-Reply-To: <20050513152838.E30976@carver.gumbysoft.com>
Mime-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <6863f0c905051209432a3afcb9@mail.gmail.com>
	 <20050513152838.E30976@carver.gumbysoft.com>
cc: freebsd-stable@freebsd.org
Subject: Re: 5.4 weird transmit problem
X-BeenThere: freebsd-stable@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
Reply-To: jmc <jcagle@gmail.com>
List-Id: Production branch of FreeBSD source code
	<freebsd-stable.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-stable>
List-Post: <mailto:freebsd-stable@freebsd.org>
List-Help: <mailto:freebsd-stable-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-stable>,
	<mailto:freebsd-stable-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Mon, 16 May 2005 13:23:33 -0000

On 5/13/05, Doug White <dwhite@gumbysoft.com> wrote:
> On Thu, 12 May 2005, jmc wrote:
>=20
> > I've got 5.4 amd64 installed on an Opteron server and I cannot get it t=
o
> > reliably transmit packets larger than 80 bytes using the bge driver (on=
 a
> > BCM5703 NIC). It receives large packets without any problem, but it jus=
t
> > won't transmit them. (I can tcpdump all day long without a problem - bi=
g and
> > small packets.)
> >
> > For example, I can "ping -s 38 <ip>" and it works fine. But if I try "p=
ing
> > -s 39 <ip>" (or any size larger than 38) it does not work. A 38 byte pi=
ng
> > creates an 80 byte Ethernet packet.
>=20
> Random guesses:
>=20
> 1. Make sure your switch agrees with the speed and duplex setting.
> Auto-neg problems are common.
>=20
> 2. Replace the cable.
>=20
> 3. Back-to-back two systems and try to reproduce.
>=20

Hey Doug,

Thanks for the tips.  Eventually I discovered that it was a Cisco
switch problem -- I was trying to use it "out of the box" without
configuring anything.  As soon as I set the time & timezone, and
password, everything else started working perfectly.  I can't explain
why it would have been in such a weird state -- only allowing small
frames through.  I tried to reproduce the problem with another switch,
but it never got in this "confused" state.

Thanks,
John