Excessive NIC Errors?

Excessive NIC Errors?

Post by Richard Pett » Thu, 05 Oct 2000 13:16:09



I'm running Red Hat 6.2 on a 486/33 with 28Meg of RAM. I'm using two
NE2000 ISA Ethernet cards. The computer is acting as a router for my
home LAN and seems to be doing a great job of it.

Almost immediately after setting it up, though, I noticed a lot of
collisions and dropped packets. In fact, I could actually see it
occuring on on the error lights of my Ethernet switch and hub.

I'd never seem them blink before, but now, especially when I'm
downloading a big file from a very fast Internet host, my switch's
collision/error lights blink regularly.

eth0
 Link encap:Ethernet  HWaddr 00:E0:29:71:DA:A7  
 inet addr:24.93.51.77 Bcast:255.255.255.255 Mask:255.255.255.0
 UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
 RX packets:8465167 errors:54 dropped:3331 overruns:0 frame:973
 TX packets:4463068 errors:0 dropped:0 overruns:0 carrier:0
 collisions:99849 txqueuelen:100
 Interrupt:3 Base address:0x300

eth1
 Link encap:Ethernet  HWaddr 00:E0:29:41:54:04  
 inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
 UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
 RX packets:7888036 errors:2 dropped:724 overruns:0 frame:240
 TX packets:10336604 errors:0 dropped:0 overruns:0 carrier:0
 collisions:103868 txqueuelen:100
 Interrupt:5 Base address:0x320

I have a lot of errors, but I don't know if I have so many that I should
worry about it. It doesn't not seem to cause any quality or throughput
problems for any of my other systems. I routinely max out my cable
connection.

--Richard

--
Spam deterent: Remove the "BOGUS" part for a correct address.

 
 
 

Excessive NIC Errors?

Post by David K. Mean » Thu, 05 Oct 2000 15:38:43


There are many possibilities here, but the most likely is that
you are using ISA Ethernet cards.  The clue is that the principal
error report on your  eth0  is dropped packets, rather than
other errors.  This is an indication that the receiver cannot keep
up with the incoming packet rate; almost certainly this is due to
the slowth of unloading the packets through the ISA bus.

It is not certain, but a good guess that when a packet gets dropped,
the driver resets the ethernet chip, and *causes* a framing error, if yet
another packet is on its way.

If you can generate controlled traffic rates, you can decide these
questions,
by plotting the number of dropped packets and framing errors as a function
of the offered packet arrival rate.

Or you could just get PCI ethernet cards (about $29 here), and move on to
the
next problem.


Quote:> I'm running Red Hat 6.2 on a 486/33 with 28Meg of RAM. I'm using two
> NE2000 ISA Ethernet cards. The computer is acting as a router for my
> home LAN and seems to be doing a great job of it.

> Almost immediately after setting it up, though, I noticed a lot of
> collisions and dropped packets. In fact, I could actually see it
> occuring on on the error lights of my Ethernet switch and hub.

> I'd never seem them blink before, but now, especially when I'm
> downloading a big file from a very fast Internet host, my switch's
> collision/error lights blink regularly.

> eth0
>  Link encap:Ethernet  HWaddr 00:E0:29:71:DA:A7
>  inet addr:24.93.51.77 Bcast:255.255.255.255 Mask:255.255.255.0
>  UP BROADCAST NOTRAILERS RUNNING  MTU:1500  Metric:1
>  RX packets:8465167 errors:54 dropped:3331 overruns:0 frame:973
>  TX packets:4463068 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:99849 txqueuelen:100
>  Interrupt:3 Base address:0x300

> eth1
>  Link encap:Ethernet  HWaddr 00:E0:29:41:54:04
>  inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
>  UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
>  RX packets:7888036 errors:2 dropped:724 overruns:0 frame:240
>  TX packets:10336604 errors:0 dropped:0 overruns:0 carrier:0
>  collisions:103868 txqueuelen:100
>  Interrupt:5 Base address:0x320

> I have a lot of errors, but I don't know if I have so many that I should
> worry about it. It doesn't not seem to cause any quality or throughput
> problems for any of my other systems. I routinely max out my cable
> connection.

> --Richard

> --
> Spam deterent: Remove the "BOGUS" part for a correct address.


 
 
 

1. Excessive NIC errors - weird throughput

HI!

I have a massive problem with my network...

I'm running a linux box as router/firewall witch
SuSE Linux 7.0
my clients are Win2K connecting to samba 2.0.7

all worked fine with my old 3com EtherlinkIII
adapters and 3com hub
now I switched to 100Mbit and the problems
began...

i use a Nexo 10/100 Mbps NWay Switch witch all
Nexo 100BaseTX NEC-100D
adapters (DEC21143 chipset)
i tried the tulip-driver half-duplex (with
explicit setting to hd in w2k)
and
the de4x5 driver with half and full duplex (fd
with autodetect in w2k)

routing/firewalling runs smoothly - file transfer
between my 2 w2k boxes as
well

and now my problem:
when uploading files to my linux-box (via samba
or ftp) i get a throughput
of 500 KByte/s
when downloading i get horrible 6.2 KByte/s!!

looking at the output of ifconfig i get this:
eth0      Link encap:Ethernet  HWaddr
00:00:1C:B5:DE:48
          inet addr:192.168.0.1
Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::200:1cff:feb5:de48/10
Scope:Link
          inet6 addr: fe80::1cb5:de48/10
Scope:Link
          UP BROADCAST RUNNING MULTICAST
MTU:1500  Metric:1
          RX packets:2598 errors:0 dropped:0
overruns:0 frame:0
          TX packets:5 errors:4596 dropped:0
overruns:1 carrier:3723
          collisions:0 txqueuelen:100
          Interrupt:9 Base address:0x6100

please all you guys out where: HELP!!!

Thanks!

Peter

Sent via Deja.com http://www.deja.com/
Before you buy.

2. growing a RAID-0 linear device (md driver)

3. ifconfig: excessive frame errors

4. really frustrated newbie!

5. Excessive errors using rz

6. Where is Linux?

7. Excessive "send body lost connection to client" errors?

8. Beyond fsck...

9. Athlon X2 oddities: APIC errors and excessive parport0 interrupts

10. Excessive RX Errors on PPP in Synchronous Mode

11. Excessive error messages - Is this a hack?

12. More (other) NIC info/Problem: NIC doesn't work anymore, SIOCIFADDR-errors

13. Working NIC shows 0 tx 100% errors 150% carrier errors