Pesky transmit time out

Stephen Host
Thu Dec 30 15:01:59 1999

I run a Masq server for my housemates. It has been up for 56 days now but,
unfortunately, one of my netcards (the primary intranet card) has decided
to hang completely on me.  I noticed this 2 weeks ago, when my quake 3
server behing my firewall would stop recieving packets for about 3
It turns out the tramit problem would  surface on this particular DEC
21041 card and re-set itself.
Currently, it is re-setting consistantly and NOT allowing any packets
through this segment of my network. (thus the problem has worsened)

My hardware is:
3 X D-link  w/Dec 21041 cards. Both the other cards are solid (seemingly)
as there are no errors associated with eth0/eth2 since last reboot.

Relevant software: Kernel 2.2.10, Tulip version 0.91, Redhat 5.X upgraded.

Here is some possible information that could be helpful..

eth1: 21041 transmit timed out, status fc260010, CSR12 000050c8, CSR13 ffffef09,
 CSR14 fffff7fd, resetting...
eth1: 21041 transmit timed out, status fc260010, CSR12 000000c8, CSR13 ffffef05,
 CSR14 ffffff3f, resetting...
[toast-@darkwing toast]$                                                       

/sbin/ifconfig eth1
eth1      Link encap:Ethernet  HWaddr 00:80:C8:F6:EF:86
          inet addr:  Bcast:  Mask:
          RX packets:60480489 errors:679 dropped:0 overruns:0
          TX packets:0 errors:2140872330 dropped:75892738 overruns:29850
          Interrupt:10 Base address:0x6100                   

I'm aware that re-booting may be a solution but in the quest for a stable
server rebooting is not an option unless the very last issue =)

Further, since only one card is affected, it seems this could be a
hardware issue, but i'd like to nail down a software issue first..

Thanks for your help!

Steve Host - Engineering Systems & Computing Student, University of Guelph -

To unsubscribe send a message body containing "unsubscribe"