NETDEV errors with FC2 eth1

[Cr0n_J0b]

I keep seeing these errors every few seconds on my internal network card.

Jul 3 10:51:35 ip68-231-208-189 kernel: NETDEV WATCHDOG: eth1: transmit timed out
Jul 3 10:51:35 ip68-231-208-189 kernel: eth1: transmit timed out, tx_status 00 status e000.
Jul 3 10:51:35 ip68-231-208-189 kernel: diagnostics: net 0cc0 media 8802 dma 00000000 fifo 8800
Jul 3 10:51:35 ip68-231-208-189 kernel: Flags; bus-master 1, dirty 1(1) current 17(1)
Jul 3 10:51:35 ip68-231-208-189 kernel: Transmit list 00000000 vs. 18d312a0.
Jul 3 10:51:35 ip68-231-208-189 kernel: 0: @18d31200 length 8000006e status 8000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 1: @18d312a0 length 80000046 status 00000046
Jul 3 10:51:35 ip68-231-208-189 kernel: 2: @18d31340 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 3: @18d313e0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 4: @18d31480 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 5: @18d31520 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 6: @18d315c0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 7: @18d31660 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 8: @18d31700 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 9: @18d317a0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 10: @18d31840 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 11: @18d318e0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 12: @18d31980 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 13: @18d31a20 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 14: @18d31ac0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 15: @18d31b60 length 8000006e status 8000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: eth1: Transmit error, Tx status register 90.
Jul 3 10:51:35 ip68-231-208-189 kernel: Flags; bus-master 1, dirty 1(1) current 17(1)
Jul 3 10:51:35 ip68-231-208-189 kernel: Transmit list 16d31340 vs. 18d312a0.
Jul 3 10:51:35 ip68-231-208-189 kernel: 0: @18d31200 length 8000006e status 8000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 1: @18d312a0 length 80000046 status 00000046
Jul 3 10:51:35 ip68-231-208-189 kernel: 2: @18d31340 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 3: @18d313e0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 4: @18d31480 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 5: @18d31520 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 6: @18d315c0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 7: @18d31660 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 8: @18d31700 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 9: @18d317a0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 10: @18d31840 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 11: @18d318e0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 12: @18d31980 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 13: @18d31a20 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 14: @18d31ac0 length 8000006e status 0000006e
Jul 3 10:51:35 ip68-231-208-189 kernel: 15: @18d31b60 length 8000006e status 8000006e


Any thoughts?

I have:

eth0 VIA chipset ether port
eth1 Kingston 100TX Tulip card
eth2 3Com Boomerang
eth3 3Com Boomerang

IFCONFIG.

eth0 Link encap:Ethernet HWaddr 00:0A:E6:E9C:B5
inet addr:68.231.208.189 Bcast:68.231.211.255 Mask:255.255.252.0
inet6 addr: fe80::20a:e6ff:fee9:dcb5/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:12094899 errors:0 dropped:0 overruns:0 frame:0
TX packets:2489624 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:2269799182 (2164.6 Mb) TX bytes:146541727 (139.7 Mb)
Interrupt:5 Base address:0xd00

eth1 Link encap:Ethernet HWaddr 00:60:972:76:4E
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::260:97ff:fec2:764e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:18441 dropped:0 overruns:18443 carrier:18443
collisions:0 txqueuelen:1000
RX bytes:32125 (31.3 Kb) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe800

eth2 Link encap:Ethernet HWaddr 00:A0:248:5D:E6
inet addr:192.168.1.22 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2a0:24ff:fed8:5de6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:12 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:2 carrier:2
collisions:0 txqueuelen:1000
RX bytes:32125 (31.3 Kb) TX bytes:0 (0.0 b)
Interrupt:10 Base address:0xe400

eth3 Link encap:Ethernet HWaddr 000:F0:30:0E:A6
inet addr:192.168.1.23 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::2c0:f0ff:fe30:ea6/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1465866 errors:3 dropped:0 overruns:0 frame:0
TX packets:808103 errors:2 dropped:0 overruns:2 carrier:0
collisions:0 txqueuelen:1000
RX bytes:988013911 (942.2 Mb) TX bytes:575624529 (548.9 Mb)
Interrupt:10 Base address:0xcf80

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:2965 errors:0 dropped:0 overruns:0 frame:0
TX packets:2965 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:1846675 (1.7 Mb) TX bytes:1846675 (1.7 Mb)

vmnet8 Link encap:Ethernet HWaddr 00:50:560:00:08
inet addr:172.16.56.1 Bcast:172.16.56.255 Mask:255.255.255.0
inet6 addr: fe80::250:56ff:fec0:8/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:309 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)


mii-tool

eth0: negotiated 100baseTx-FD flow-control, link ok
eth1: negotiated 100baseTx-FD, link ok
eth2: no autonegotiation, 100baseTx-FD, link ok
eth3: negotiated 100baseTx-FD, link ok


thanks

[maxut]

eth1 Link encap:Ethernet HWaddr 00:60:972:76:4E
inet addr:192.168.1.1 Bcast:192.168.1.255 Mask:255.255.255.0
inet6 addr: fe80::260:97ff:fec2:764e/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:18441 dropped:0 overruns:18443 carrier:18443
collisions:0 txqueuelen:1000
RX bytes:32125 (31.3 Kb) TX bytes:0 (0.0 b)
Interrupt:11 Base address:0xe800

something wrong with eth1. maybe cables, maybe drivers, maybe wrong configs. if i were u, i would change the cable and RJ-45 connectors first. if it stil keep collisions, i would change that NIC card.

[Cr0n_J0b]

Well I switched the cables...but I'm worried it's software related.

I'd hate to have to go get another card.

[crackers]

Swap the Tulip card with one of the 3Coms (in the slots) - they should "switch" between eth1 and eth2. That'll aid in determining if the card is bad or not. You might also be having a conflict between the drivers (doubtful, though). I've used different chipset cards before and not had problems (granted, this was non-FC, but it should still apply unless the kernel developers have really broken something bad - also doubtful, but possible).

[Cr0n_J0b]

I have a feeling that it was the cable...I'm checking the logs and I'm not getting the constant messages....I had it hooked with a CAT 3 cable...don't know why...

We'll see if this is a real fix or just a short term bandaid.

[daddyr]

I am getting this same problem, except that it did not start until yesterday when I upgraded from RH 9 to FC 2, so I'm pretty sure its not a hardware or cable problem.

[uNstAbLe]

Take a look to this thread:

http://www.scyld.com/pipermail/vorte...st/002428.html

The problem should be related to kudzu, disabling it in my case solved the problem:

> IIRC, kudzu from Fedora did not play nice with the 3c59x driver, trying to get some
> data that needed hardware access while the hardware was still in sleep
> state. Some cards were disturbed by this and did not function
> afterward; some others (like Tornado/905C) were not disturbed. Alan
> Cox submitted a fix at some point, but, as I have lost track of the
> issue, I don't know if it actually fixed the problem.

> So, my suggestion is to disable kudzu ('chkconfig kudzu off') then
> reboot. If the network starts functioning, then you had this problem.
> An update of the kernel and/or kudzu (if available) might provide the
> fix and will allow using the network while still keeping kudzu on.