eth0: DC21143
eth0 Link encap:Ethernet HWaddr 00:A0:CC:D3:C1:E7
collisions:295789 txqueuelen:100
!!! You have this nic plugged in to a switch!! 295,789 collisions which
should be 0!
eth1: 3Com 3c905B
eth1 Link encap:Ethernet HWaddr 00:A0:CC:D3:FC:DF
RX packets:2045925 errors:0 dropped:0 overruns:0 frame:0
TX packets:1961416 errors:4631 dropped:0 overruns:2 carrier:0
collisions:0 txqueuelen:100
TX errors, but no RX errors. Hmm.. I would say both of these errors
*could* indicate a faulty card. First though, I would suspect a bad cable
(ie short) for the cable in eth0.
tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED]
de4x5.c:V0.544 1999/5/8 [EMAIL PROTECTED]
3c59x.c:v0.99H 11/17/98 Donald Becker
There may also be newer drivers for your kernel version. These are pretty
old. A new driver may alleviate some of these issues.
Cory
-----Original Message-----
From: Horst Lueck [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, August 14, 2001 12:07 PM
To: [EMAIL PROTECTED]
Subject: [EUG-LUG:2190] NIC: TX errors (ifconfig) -- and what it means?
I have two cards that gives me trouble about twice a week (they hang) on a
RH 6.1 installation; ifconfig shows for eth1:
TX packets:1961416 errors:4631 dropped:0 overruns:2 carrier:0
the relevant dmesg clip and the full ifconfig is at the bottom.
The first question is could the TX error indicate a faulty card?
One card can be reset with:
ifdown eth1; ifup eth1
The other requires
S10network reload
Swapping CAT5 cables and slots in Netgear switchbox didn't un-lock a
locked card (too early to tell if this had a log-term effect). Taking
CAT5 cables in and out while pinging another local machine did not
necessarily add another TX error (see above) but one of the funny cards
did eventually lock during that test and then it did increment the TX
errors (my guess is that different network layers have their own logging
and recovery mechanisms)
Two of the three machines have their eth0 on global IP addresses, and eth1
via Netgear switch box on a local network; 3rd machine has only local IP.
It is odd that the problems only appear on the local cards !?
Has anybody experienced that a switch box can confuse or even damage a
NIC ?
Unfortunately, the downtime has to be kept at a minimum - so just swapping
NICs, rebooting, etc ... should be seen as last resort and justified by
some diagnosis first.
Thanks for any feedback ..................... Horst.
(P.S. I liked Ralph's clip yesterday letting Linus himself expanding on
his NIC preferences)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
DMESG 2:
tulip.c:v0.91g-ppc 7/16/99 [EMAIL PROTECTED]
eth0: Lite-On 82c168 PNIC rev 32 at 0xe800, 00:A0:CC:D3:C1:E7, IRQ 10.
eth0: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth1: Lite-On 82c168 PNIC rev 32 at 0xe400, 00:A0:CC:D3:FC:DF, IRQ 5.
eth1: MII transceiver #1 config 3000 status 7829 advertising 01e1.
eth1: Setting full-duplex based on MII#1 link partner capability of 41e1.
DMESG 2:
eth0: DC21143 at 0x9000 (PCI bus 0, device 11), h/w address
00:48:54:80:00:ee,
and requires IRQ10 (provided by PCI BIOS).
de4x5.c:V0.544 1999/5/8 [EMAIL PROTECTED]
3c59x.c:v0.99H 11/17/98 Donald Becker
http://cesdis.gsfc.nasa.gov/linux/drivers/vortex.html
Cyclone 100baseTx at 0x9400, 00:50:da:1f:1d:3d, IRQ 9
8K byte-wide RAM 5:3 Rx:Tx split, autoselect/Autonegotiate interface.
MII transceiver found at address 24, status 7849.
MII transceiver found at address 0, status 7849.
Enabling bus-master transmits and whole-frame receives.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
IFCONFIG:
eth0 Link encap:Ethernet HWaddr 00:A0:CC:D3:C1:E7
inet addr:xxx.xxx.xxx.108 Bcast:xxx.xxx.xxx.111
Mask:255.255.255.248
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12418814 errors:0 dropped:0 overruns:0 frame:0
TX packets:17719884 errors:0 dropped:0 overruns:0 carrier:0
collisions:295789 txqueuelen:100
Interrupt:10 Base address:0xe800
eth1 Link encap:Ethernet HWaddr 00:A0:CC:D3:FC:DF
inet addr:192.168.1.55 Bcast:192.168.1.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:2045925 errors:0 dropped:0 overruns:0 frame:0
TX packets:1961416 errors:4631 dropped:0 overruns:2 carrier:0
collisions:0 txqueuelen:100
Interrupt:5 Base address:0xe400
lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:3924 Metric:1
RX packets:11977918 errors:0 dropped:0 overruns:0 frame:0
TX packets:11977918 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
