On Fri, 7 Dec 2001, James Stevenson wrote: > Hi > > from what i can tell is the overun is because you have had a > buffer overrun on the network card > eg more data has been sent to the card from another computer than > the computer can process. > > except you should not get 1 on the TX stats. > > these are more common on a 486sx33 or so :) > > eth0 Link encap:Ethernet HWaddr 00:A0:24:83:2E:15 > inet addr:192.168.1.6 Bcast:255.255.255.0 Mask:255.255.255.0 > inet6 addr: fe80::2a0:24ff:fe83:2e15/10 Scope:Link > UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 > RX packets:838304 errors:219 dropped:0 overruns:227 frame:219 > TX packets:758826 errors:0 dropped:0 overruns:0 carrier:4 > collisions:1443 txqueuelen:100 > RX bytes:224044357 (213.6 Mb) TX bytes:124675867 (118.9 Mb) > Interrupt:5 Base address:0x220 > > > > > ----- Original Message ----- > From: "Casey Carter" <Casey@Carter.net> > To: <linux-net@vger.kernel.org> > Sent: Friday, December 07, 2001 7:45 PM > Subject: Re: How do I find the cause of these errors? > > > > That's one of the cool things about us Linux geeks. Show me a Windows > > user who will put effort into tracing down the source of 1 error in 11 > > million packet transmissions... > > > > Kenneth Stephen wrote: > > > Hi, > > > > > > Here is the output of my ifconfig : > > > > > > James, Casey, 1. Dont be overly self-congratulatory : the correct way to look at these errors is to see that it has lost 1 packet in 1 day of running (I rebooted about a day ago). Over a period of a month, I've seen the errors mount upto 200 - 300 packets lost. To my mind, the percentage lost isnt whats important - its the magnitude of the loss that matters. BTW, I use WinXX too (not that I'm ecstatic about it, but still...). 2. Can a buffer overrun be compensated for by tuning kernel / card settings / driver parameters? 3. I dont follow what you mean by "..should not get 1 on the TX stats.". Where else would an overrun be reported? Thanks, Kenneth - : send the line "unsubscribe linux-net" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html
