Red Hat Bugzilla – Bug 206901
Hangs when initiating TCP/network connection(s).
Last modified: 2007-11-30 17:11:43 EST
Description of problem:
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Initiate a number of outbound connections. E.g. Open firefox, go to
www.directcanada.com, or start azureus with a number of active torrents.
The whole computer hangs.
Everything should behave smoothly.
Tested with older kernel kernel-smp.i686 2.6.17-1.2174_FC5 and those things
don't happen. The only other newly installed package that might have done this
is the ati fglrx driver although I doubt the ati driver causes the whole
computer to hang (usually just X and can be killed using Ctrl-Alt-Backspace).
*** Bug 206902 has been marked as a duplicate of this bug. ***
Same problem on my computer, but works without problem on collegaue's computer.
I can tell, that I am not using fglrx driver, only standard radeon driver
(without 3D support).
It hangs on incomming connections too, but not all connenction hangs my
computer. I can't connect from home to work computer, but I can connect from one
server to work. Computer hangs after initializing for example ssh/tcp or
With my collegaue we have nearly same hardware, but I can't kill it's computer. :-)
I think, it is a software problem. May be some iptables rules or selinux rules?
Probably related to the forcedeth driver. I think it's the same as bug 206744.
A new kernel update has been released (Version: 2.6.18-1.2200.fc5)
based upon a new upstream kernel release.
Please retest against this new kernel, as a large number of patches
go into each upstream release, possibly including changes that
may address this problem.
This bug has been placed in NEEDINFO state.
Due to the large volume of inactive bugs in bugzilla, if this bug is
still in this state in two weeks time, it will be closed.
Should this bug still be relevant after this period, the reporter
can reopen the bug at any time. Any other users on the Cc: list
of this bug can request that the bug be reopened by adding a
comment to the bug.
In the last few updates, some users upgrading from FC4->FC5
have reported that installing a kernel update has left their
systems unbootable. If you have been affected by this problem
please check you only have one version of device-mapper & lvm2
installed. See bug 207474 for further details.
If this bug is a problem preventing you from installing the
release this version is filed against, please see bug 169613.
If this bug has been fixed, but you are now experiencing a different
problem, please file a separate bug for the new problem.
I've not seen this happening with 2.6.18-1.2200.fc5smp kernel. I think it's safe
to close this bug.