Date: Tue, 9 Jan 2001 13:46:18 -0600 From: Jonathan Lemon <jlemon@flugsvamp.com> To: "Jeroen C. van Gelderen" <jeroen@vangelderen.org> Cc: Jonathan Lemon <jlemon@flugsvamp.com>, stable@freebsd.org Subject: Re: Intel PRO/100+ driver or hardware? (Update) Message-ID: <20010109134618.L29115@prism.flugsvamp.com> In-Reply-To: <89010000.979063602@grolsch.ai> References: <200101081521.f08FLDi31948@prism.flugsvamp.com> <89010000.979063602@grolsch.ai>
next in thread | previous in thread | raw e-mail | index | archive | help
On Tue, Jan 09, 2001 at 02:06:42PM -0400, Jeroen C. van Gelderen wrote: > --On Monday, January 08, 2001 09:21:13 -0600 Jonathan Lemon > <jlemon@flugsvamp.com> wrote: > [...] > > It looks like 'hayek' is refusing to accept one of the segments that > > 'keynes' is transmitting. The segment arrives at the machine, but > > 'hayek' never sends an ACK. > > > > I'd look at 'netstat -s' and see whether any of the 'bad checksum' > > counters are set, if so, then something is corrupting the packets. > > Just the flag I needed :-) As soon as the connection stalls, the > bad-checksum counter goes trough the roof. And *every* re-transmitted > packet seems to have a bad checksum as well. > > The hub is not busy at the moment I tried and none of the other TCP > connections to and from this box are affected when this occurs. It seems > that packets with certain content get mangled so that retransmits will > never solve the problem. I did have a similar problem with an early netgear FS509 switch; it would consistently refuse to transmit certain data patterns. Netgear support confirmed that there was memory problem with certain revisions and sent me a new switch; it's worked fine thereafter. > My conclusion is that the Intel cards I have are broken. They refuse to > work reliably in an otherwise healthy low-end network. I may have a bad > batch or maybe these cards are broken by design. That's possible. The other possibility is that the driver may be at fault; it may need further updating for the 82559 chip variants. > > Does this happen even if you connect the machines back to back (with > > a crossover cable?) > > I don't have a cross-over cable unfortunately, and I won't be able to buy > one where I am :-( I seem to recall however that Intel cards don't like > being connected back2back? Not that I know of; any cards should work with a crossover cable. By doing this, you can at least isolate whether the problem is with the switch/hub, or with the cards themselves. I use a mixture of Intel, 3com and various gigabit cards with no problems. -- Jonathan To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20010109134618.L29115>