Red Hat Bugzilla – Bug 50940
(NET PCNET32) AMD 79c972 based fiber nic will not recover link when disconnected
Last modified: 2013-07-02 22:04:21 EDT
Description of Problem:
Allied Telesyn 2700FX NICs will not recover link after being disconnected
for any reason. Reboot is the only thing have found that will bring the
connection back up. As this is an AMD 79c972 based card Both anaconda and
kudzu install it using the pcnet32 driver.
The card works fine on 2.2.16-22.
I can find no log messages anywhere that indicate where the problem is.
Bringing the interface down and backup ising ifdown eth1 and ifup eth1 have
no effect. The link light is lost and is not to be found again.
If I rmmod pcnet32 and then try to bring the interface up I get an Oops. I
will attach a listing to this bug. The oops part may be a dup but it is
definetly not fixed in 2.4.3-12 from the updates dir. Same thing if I try
to insmod or modprobe manually
The same thing happens whether I connect to our D-Link DES-5200 fiber
switch or to another 2700 NIC in the 2.2.16-22 box.
Steps to Reproduce:
1. boot machine
2. remove incoming fiber line (link light goes out)
3. reconnect fiber line
link light (and connection) goes out but does not come back on
link light goes out but comes back on when fiber is reinstalled
Created attachment 26293 [details]
transcript of session that locks machine
Created attachment 26294 [details]
output of lspci -vv
lspci will lock the machine at any time after rmmod pcnet32. See attached
If I disconnect the fiber, causing the link light to go out, reconnect it (no
link light at this point) and then try to ping the switch of course nothing
happens. I do notice however that ifconfig reports the TX packets and an error
for each one. The CARRIER field is also incremented by this number ( the number
of ping packets sent).
I could really use some help on this.
Thanks for the bug report. However, Red Hat no longer maintains this version of
the product. Please upgrade to the latest version and open a new bug if the problem
The Fedora Legacy project (http://fedoralegacy.org/) maintains some older releases,
and if you believe this bug is interesting to them, please report the problem in
the bug tracker at: http://bugzilla.fedora.us/