Bug 377491
| Summary: | Networking locks up after random time | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Huub <huubvanniekerk> | ||||||||||
| Component: | kernel | Assignee: | Kernel Maintainer List <kernel-maint> | ||||||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||||||
| Severity: | medium | Docs Contact: | |||||||||||
| Priority: | low | ||||||||||||
| Version: | 8 | CC: | chris.brown, madko, romieu, sergio, tomek, wbachman | ||||||||||
| Target Milestone: | --- | ||||||||||||
| Target Release: | --- | ||||||||||||
| Hardware: | x86_64 | ||||||||||||
| OS: | Linux | ||||||||||||
| Whiteboard: | |||||||||||||
| Fixed In Version: | 2.6.23.15-137.fc8 | Doc Type: | Bug Fix | ||||||||||
| Doc Text: | Story Points: | --- | |||||||||||
| Clone Of: | Environment: | ||||||||||||
| Last Closed: | 2008-02-14 22:39:46 UTC | Type: | --- | ||||||||||
| Regression: | --- | Mount Type: | --- | ||||||||||
| Documentation: | --- | CRM: | |||||||||||
| Verified Versions: | Category: | --- | |||||||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||||||
| Embargoed: | |||||||||||||
| Attachments: |
|
||||||||||||
|
Description
Huub
2007-11-12 10:51:39 UTC
Can you please attach /var/log/dmesg to this bugzilla? Created attachment 256341 [details]
/var/log/dmesg
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? Appears on: kernel-2.6.23.1-49.fc8 kernel-2.6.23.1-42.fc8 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 ? -- Ueimor I've got exactly the same problem as the reporter. Architecture and NIC match, kernel also matches. Simply starting thunderbird or firefox kills network. 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. Tomasz :
> 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 ?
--
Ueimor
As the reporter: r8169 on amd64 with kernel-2.6.23.1-49.fc8. My working f7 kernel is: kernel-2.6.23.1-21.fc7.i686 My problem also looks like bug #377721 so i will try to boot with the noapic kernel option (answering Tomasz) It looks like a kernel config difference (broken DAC again ?). Can you attach the three kernel dmesgs please ? kernel-2.6.23.1-49.fc8 and kernel-xen-2.6.21-2950.fc8.x86_64 could be enough but the fc7 one will not hurt. -- Ueimor 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]
kernel-2.6.23.1-49.fc8.x86_64 dmesg
Created attachment 262811 [details]
kernel-2.6.23.1-49.fc8.x86_64 with noapic option dmesg
Created attachment 262821 [details]
kernel-xen-2.6.21-2950.fc8.x86_64 dmesg
Same thing here... AMD64 card 1: RTL-8169 card 2: VT6102 [Rhine-II] kernel-2.6.23.1-42.fc8 Hello, I'm reviewing this bug as part of the kernel bug triage project, an attempt to isolate current bugs in the Fedora kernel. http://fedoraproject.org/wiki/KernelBugTriage 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 kernel-2.6.23.15-137.fc8.x86_64 Thanks Tomasz. Would be good to get feedback from the original reporter as well. Huub? It indeed seems that the latest kernel doesn't have the problem anymore. |