eth0 will not restart. Errors in /var/log/messages

I have a small network comprised of one computer running Fedora Core 2 and another running Windows 2000 Pro. Both are connected to a D-link router and that is connected to my cable modem.

Note: I have completely disabled iptables and any other network security that I know of, so I know that is not the problem (at least I think I know that).

When I restart the Linux box, the Internet and network connections work fine, but after a short while, I can't access anything network-related through the Linux machine. I tried to restart the "network" service and got this result (fyi: "homer" is the local host name):

[root@homer root]# service network restart
Shutting down interface eth0:                              [  OK  ]
Shutting down loopback interface:                          [  OK  ]
Setting network parameters:                                [  OK  ]
Bringing up loopback interface:                            [  OK  ]
Bringing up interface eth0:
Determining IP information for eth0...PING 192.168.0.1 (192.168.0.1) 56(84) bytes of data.
 
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 received, +3 errors, 100% packet loss, time 1999ms
, pipe 4
 failed.
                                                           [FAILED]

Upon looking at the /var/log/mesages file, I found this error:

Jun  5 09:48:04 homer kernel: NETDEV WATCHDOG: eth0: transmit timed out
Jun  5 09:48:04 homer kernel: eth0: transmit timed out, tx_status 00 status e000.
Jun  5 09:48:04 homer kernel:   diagnostics: net 0cd8 media 8c80 dma 000000a0 fifo 8000
Jun  5 09:48:04 homer kernel:   Flags; bus-master 1, dirty 1328(0) current 1344(0)
Jun  5 09:48:04 homer kernel:   Transmit list 2059c200 vs. 2259c200.

I don't know what this means, but if anyone can help me nail this down I would greatly appreciate it.

Thanks!

I would check out what watchdog is... sounds like a firewall blocking thing to me. Everytime you restart you would be flushing the firewall rules, allowing you to connect, then after a few connections you may be getting blocked.

Just an idea...

you dont by chance have portsentry running do you?

I do not have portsentry running (that I know of).

How did you disable iptables?

If you do

#iptables -L

Does anything come up?

Here's what comes up:

[root@homer root]# iptables -L
Chain INPUT (policy ACCEPT)
target     prot opt source               destination
 
Chain FORWARD (policy ACCEPT)
target     prot opt source               destination
 
Chain OUTPUT (policy ACCEPT)
target     prot opt source               destination

however, that was immediately, after a restart, so maybe it would be different after the thing starts failing....

exactly...

try it again after it has failed, and see if it any different.

Also keep an eye on /etc/hosts.deny

Lucas

I will do that and post when I sotice something of interest. Thanks for your help!

Watchdogs are logic built into some chips to guard against infinite loops and hangs. Normally, they will reset the device or escape from a process running at the logic level.

Either you have a hardware problem, driver issue, or it could not like the D-Link router it is connected to. Oh yeah, this could be an APIC issue as well.

I have entertianed the idea that it could be an APIC issue, thank to the help of someone on another thread. I have disabled all power management within Linux and at BIOS level-- no dice.