Red Hat Bugzilla – Bug 377491
Networking locks up after random time
Last modified: 2008-02-14 17:39:46 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20071025 Firefox/188.8.131.52
Description of problem:
After starting the pc all works well, but after a random time, I notice that the connection with the network is gone. Ping shows '...Destination Host Unreachable' and /var/log/messages shows 'kernel: NETDEV WATCHDOG: eth0: transmit timed out'.
The nic-chipset is RTL-8169.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. start up the pc and log in
2. start any networking program
3. do anything in it until nothing happens anymore except the mouse-cursor keeps busy.
The pc keeps running, without networking contact.
Proceeding with download, positive results with ping.
Can you please attach /var/log/dmesg to this bugzilla?
Created attachment 256341 [details]
I also loose network connection after a couple of hours
Host unreachable in syslog from named, this is on a remote hosted server so when
network is lost i can't do anything more to test... I just know that the kernel
is fine, just the network seems down
Nothing about watchdog here so maybe it's another bug?
The NIC is a "VIA Technologies, Inc. VT6120/VT6121/VT6122 Gigabit Ethernet
Adapter" on an Eden C7 2Ghz motherboard
I'm now back on the last F7 kernel and it works great (for the moment)
Adding cc: for maintainer.
Huub, is there a kernel version that you know is working with your 8169 ?
It would really help me.
Edouard, can you specify the working F7 kernel version ?
I've got exactly the same problem as the reporter. Architecture and
NIC match, kernel also matches. Simply starting thunderbird or firefox
What's interesting is that xen kernel does not seem to have this
problem, I use kernel-xen-2.6.21-2950.fc8.x86_64.
> I've got exactly the same problem as the reporter.
There are two reporters with different hardware (r8169 vs via-velocity).
Which one do you use ?
As the reporter: r8169 on amd64 with kernel-184.108.40.206-49.fc8.
My working f7 kernel is:
My problem also looks like bug #377721 so i will try to boot with the noapic
It looks like a kernel config difference (broken DAC again ?). Can you attach the
three kernel dmesgs please ?
kernel-220.127.116.11-49.fc8 and kernel-xen-2.6.21-2950.fc8.x86_64 could be enough but
the fc7 one will not hurt.
I will attach dmesg's below.
I've tried noapic option as suggested in comment #10 and
it seems to fix the problem (40GiB of traffic passed
through the interface without problem and usually I had
problems after 100-200MiB of traffic).
Created attachment 262801 [details]
Created attachment 262811 [details]
kernel-18.104.22.168-49.fc8.x86_64 with noapic option dmesg
Created attachment 262821 [details]
Same thing here...
card 1: RTL-8169
card 2: VT6102 [Rhine-II]
I'm reviewing this bug as part of the kernel bug triage project, an attempt to
isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug and will try and assist you in resolving it if I can.
There hasn't been much activity on this bug for a while. Could you tell me if
you are still having problems with the latest kernel?
If the problem no longer exists then please close this bug or I'll do so in a
few days if there is no additional information lodged.
This problem seems to be gone in
Thanks Tomasz. Would be good to get feedback from the original reporter as well.
It indeed seems that the latest kernel doesn't have the problem anymore.