Description of problem: http://lkml.org/lkml/2005/8/11/79 Version-Release number of selected component (if applicable): How reproducible: 100% with the specific sequence below. Otherwise, only happens in very specific situation that we cannot reproduce. Steps to Reproduce: As described in the mail above: * have via-rhine NIC * unplug network cable * reboot box * force HDX (I do in with ethtool -s eth0 autoneg off duplex half) * plug cable back * kernel still thinks that carrier is off despite "ethtool eth0" saying that link is detected. Actual results: Communcation via the particular interface does not resume although the link is up and interface status is UP. Expected results: Communication via the particular interface is restored. Additional info: The following patch applies cleanly and fixes the problem: http://git.kernel.org/?p=linux/kernel/git/torvalds/linux-2.6.git;a=commit;h=00b428c2ab35c81905b3e39d673689216dbd4742 This is non issue in RHEL 5.* which already contains this patch.
This request was evaluated by Red Hat Product Management for inclusion in a Red Hat Enterprise Linux maintenance release. Product Management has requested further review of this request by Red Hat Engineering, for potential inclusion in a Red Hat Enterprise Linux Update release for currently deployed products. This request is not yet committed for inclusion in an Update release.
I prepared the kernel packages (for i686 and x86_64) with the bugfix. Could you please try them and put here some test report. Kernel packs are available here: http://people.redhat.com/ivecera/rhel-4-ivtest/
Thank you Ivan. I tested the kernel through the procedure mentioned above on the VIA target machine and the networking restored immediately when the cable was reconnected. It is working perfectly. # uname -a Linux localhost 2.6.9-70.EL.ivtest.1 #1 Fri May 16 09:11:41 EDT 2008 i686 i686 i386 GNU/Linux
Updating PM score.
Committed in 78.9.EL . RPMS are available at http://people.redhat.com/vgoyal/rhel4/
An advisory has been issued which should help the problem described in this bug report. This report is therefore being closed with a resolution of ERRATA. For more information on therefore solution and/or where to find the updated files, please follow the link below. You may reopen this bug report if the solution does not work for you. http://rhn.redhat.com/errata/RHSA-2009-1024.html