Date: Mon, 31 Mar 2003 12:58:35 -0600 From: "Jack L. Stone" <jackstone@sage-one.net> To: David Kelly <dkelly@hiwaay.net> Cc: FreeBSD-Questions@freebsd.org Subject: Re: Interface collisions Message-ID: <3.0.5.32.20030331125835.013dc868@sage-one.net> In-Reply-To: <20030331182046.GC61524@grumpy.dyndns.org> References: <3.0.5.32.20030331103405.013e5298@sage-one.net> <20030331143804.GG322@ns1.webwarrior.net> <3.0.5.32.20030331082034.01414bf8@sage-one.net> <20030331143804.GG322@ns1.webwarrior.net> <3.0.5.32.20030331103405.013e5298@sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:20 PM 3.31.2003 -0600, David Kelly wrote: >On Mon, Mar 31, 2003 at 10:34:05AM -0600, Jack L. Stone wrote: >[...] >> >> Also, I agree that the collisions are very small and were cached by the >> switch, not lost necessarily. However, the sudden appearance over the past >> 2-3 days indicates a change that is not for the better and more concerned >> about the trend. > >Not "cached by the switch" else your rl driver would not have known >about it. The rl driver logged the "collision" because it started >sending a packet and was not able to copy it 100% in real time so it >concluded somebody else was transmitting at the same time. > >If the card is configured in full duplex mode it should not be verifying >copy of its own data when sending, by definition. Unless there is some >sort of out-of-band communications between ethernet ports operating via >full duplex. > >-- >David Kelly N4HHE, dkelly@hiwaay.net 1) I changed cables - NO fix 2) I switched switches - NO fix 3) I set the NIC to full-duplex "on the fly" - YES - Fixed Setting the interface to full-duplex "on the fly" has now stopped all collisions on this NIC. And, you are right of course about where the caching is occurring with this symptom. Many thanks again.... Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20030331125835.013dc868>