Date: Mon, 16 May 2005 08:23:31 -0500 From: jmc <jcagle@gmail.com> To: Doug White <dwhite@gumbysoft.com> Cc: freebsd-stable@freebsd.org Subject: Re: 5.4 weird transmit problem Message-ID: <6863f0c905051606236955420f@mail.gmail.com> In-Reply-To: <20050513152838.E30976@carver.gumbysoft.com> References: <6863f0c905051209432a3afcb9@mail.gmail.com> <20050513152838.E30976@carver.gumbysoft.com>
next in thread | previous in thread | raw e-mail | index | archive | help
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
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?6863f0c905051606236955420f>