From mboxrd@z Thu Jan 1 00:00:00 1970 From: Justin Schoeman Date: Mon, 16 Oct 2006 14:09:50 +0000 Subject: Re: [LARTC] Ethernet packet loss - frame errors Message-Id: <453392AE.6020009@expertron.co.za> List-Id: References: <452F4DA6.8030505@expertron.co.za> In-Reply-To: <452F4DA6.8030505@expertron.co.za> MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: lartc@vger.kernel.org OK - Just finished more testing, and it seems to be a bug in the sky2 driver... ping -s 1450 -f xxx.xxx.xxx.xxx works perfectly, but ping -s 1500 -f xxx.xxx.xxx.xxx fails 100% with all packets being logged as frame errors. -justin Justin Schoeman wrote: > Hi all, > > I have the following problem. A Linux box configured as a bridge. One > interface connects to the router via a crossover cable, the other > connects to a switch via the cable that used to go to the router. > > Now I get the following: > > [root@localhost net]# ifconfig eth3 > eth3 Link encap:Ethernet HWaddr 00:03:2D:07:61:5D > UP BROADCAST MULTICAST MTU:1500 Metric:1 > RX packets:1969134 errors:0 dropped:0 overruns:0 frame:176459 > TX packets:2186662 errors:0 dropped:0 overruns:0 carrier:0 > collisions:0 txqueuelen:1000 > RX bytes:492595115 (469.7 Mb) TX bytes:579725462 (552.8 Mb) > Interrupt:17 > > eth3 is the interface that connects to the switch. As you can see, 1 in > 10 rx packets are framing errors. > > What are possible causes for this? The cable is a constant, so is not > likely to cause problems, so what else can possibly cause such a high > number of frame errors? > > Any help appreciated. > > Thanks, > > Justin > > _______________________________________________ > LARTC mailing list > LARTC@mailman.ds9a.nl > http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc _______________________________________________ LARTC mailing list LARTC@mailman.ds9a.nl http://mailman.ds9a.nl/cgi-bin/mailman/listinfo/lartc