Red Hat Bugzilla – Bug 244683
forcedeth-driven network card totally and irremediably out to lunch
Last modified: 2014-06-29 18:58:39 EDT
Description of problem:
Integrated network card hangs unexpectedly and repeatedly. The card dumps its
registers in var log messages.Cold reboot (unplugging etc) seems mandatory for
the network to come back.
Did unfall straight away after install on a station, and apparently at random on
Version-Release number of selected component (if applicable):
redhat kernel 2.6.9-55 ; forcedeth 0.42-rh
Install and wait (heavy activity not required).
Attached are the snippets of /var/log/message whinings, along with uname -a,
lspci -vvv, dmesg.
The same setup has been successfully and extensively used with a stock U4 install.
Created attachment 157286 [details]
details - uname / logs / dmesg / lspci
I'll profite that i see the case moved forward to 'assigned' to add my latest
* The bug can be reproduced at greatest speed if alot of activity (seems pretty
and more proeminently:
* The bug tends to be very present in the case of half-duplex communication (hubs)
* The bug seems non-existent using a switch (we worked the problem around with
that since the report)
A major update to forcedeth is planned for the next update.
You can always try my latest test kernels (they generally contain experimental
net-driver fixes and are regularly updated):
For this case, you can also check the kernels available here:
Since they contain kernels that are close to the ones that will be released with
the next RHEL4 update.
This bug has seen no activity in quite a while, so I can only presume it is no
longer a problem. If there is still an issue with the latest kernel that needs
to be resolved, please re-open this bug and I will be happy to help resolve it.