From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.8) Gecko/20050513 Galeon/1.3.20
Description of problem:
I've been experiencing intermittent problems with the 8139too on Rawhide kernels.
The network worked fine with Test2, but broke soon after on kernel-2.6.11-1.1286_FC4 and kernel-2.6.11-1.1287_FC4
On kernel-2.6.11-1.1290_FC4 it appeared fine again, but since I've tried kernel-2.6.11-1.1312_FC4+ it has been broken cosistently.
Version-Release number of selected component (if applicable):
Works on kernel-2.6.11-1.1290_FC4
Steps to Reproduce:
1. Boot system wit affected kernel
2. Acquire address with DHCP (which sometimes works)
3. Try to SSH out...
Actual Results: The SSH link hangs.
Snooping the interface shows some other traffic on the link, but I dont see any outgoing traffic from my box.
Expected Results: SSH link should establish, data should flow to and fro my box.
MII claims that the link is up at 100 full duplex, autonegotiated.
In bug 156261, another user found his 8139 problems were alleviated by adding
"tpm_atmel" and "tpm_nsc" in /etc/hotplug/blacklist. Would you mind giving
that a try to see if this has any effect on the problem you are experiencing?
Please report the results here. Thanks!
I've updated to 2.6.11-1.1341_FC4.
It displayed the same symptoms until I added "tpm_atmel" and "tpm_nsc" to the
hotplug blacklist file.
To be honest, only "tpm_atmel" seemed to get itself loaded, so it might have
been sufficient to only add it to the list.
With those modules blacklisted, networking worls like a charm (again).
Interesting...would mind removing those modules from the blacklist, then
trying the kernels here:
They include a patch from the tpm driver maintainer that she believe might be
helpful. Please post the results of using those kernels here. Thanks!
Installed kernel-2.6.11-1.1353.2.1_FC4.jwltest.3.i686.rpm and hashed out
"tpm_atmel" and "tpm_nsc" in /etc/hotplug/blacklist.
Seems to work just fine so far...
Excellent! Thanks for the quick response!
Closing as DUPLICATE of 156261...(presuming that issue is fixed as well...)
*** This bug has been marked as a duplicate of 156261 ***