Red Hat Bugzilla – Bug 392721
Via Rhine II intermittent eth0 interface failure (similar to bug 377721)
Last modified: 2008-02-13 18:25:28 EST
Description of problem:
Ethernet device stops working after use
Version-Release number of selected component (if applicable):
Fedora 8 base install
Steps to Reproduce:
1. Install Fedora 8
2. Transfer a large file by ssh/tar from a locally connected host.
Transfer hangs after a few seconds. User is unable to complete transfer. Locally
connected hosts can no longer be pinged. Interface is non-functional.
Functioning interface may be temporarily restored by /sbin/ifdown eth0 ;
Transfer completes, interface remains functional
I stumbled across this bug doing fresh install of Fedora 8. I tried both the
i386 install and the x86_64 install. On the x86 install, I tried both the i686
and i586 kernels. I tried various boot parameters:
noapic -> causes machine to slow to a crawl - one must even type slowly or else
typed input is dropped.
acpi=noirq -> none of these settings fixed the problem.
When the eth0 device fails, the following messages appear in /var/log/messages:
NETDEV WATCHDOG: eth0: transmit timed out
eth0: Transmit timed out, status 0003, PHY status 786d, resetting ...
eth0: link up, 100Mbps, full duplex, lpa 0x45E1
Interestingly, when I use the install disk in rescue mode, the interface
functions normally - I can transfer large files without the interface hanging.
This bug/behavior is not present on a fresh Fedora Core 7 install. FC7
functions normally and I am able to transfer large files.
Created attachment 265121 [details]
Smolt profile of affected machine
Intro: I'm a Fedora contributer doing some kernel bug triaging. Like you already
say yourself, this seems a dup of bug 377721, is there any particular reason why
you're filing this as a separate bug?
If not please close this one as a dup of 377721.
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 closing this as a duplicate as indicated in comment #2.
*** This bug has been marked as a duplicate of 377721 ***