Red Hat Bugzilla – Bug 282341
Problem with network after resuming from a hibernation (Fujitsu-Siemens Lifebook)
Last modified: 2008-08-02 19:40:36 EDT
Description of problem:
I have a problem with a wire network connection after resuming from a
hibernation. ICMP works fine, but all new TCP connections have 10 seconds delay
(connection hangs in SYN_WAIT state). If a timeout has a longer value and
connection is able to establish, then (as ENSTABLISHED) works fine (like SSH
I tried network restart and a few other things, but without any result (a
machine restart is needed).
No info in system log. Tested with a few recent kernel from Fedora Core 6. It
happens after every hibernation.
Version-Release number of selected component (if applicable):
kernel-2.6.20-1.2962.fc6 (confirmed also with a few version backward)
Steps to Reproduce:
1. Hibernate laptop
2. Resume from a hibernation
3. Try to use a wire network
10 seconds delay on a new TCP connections
Connection established intermediately
Tested on Fujitsu Siemens Lifebook S-series laptop with a network card:
Marvell Technology Group Ltd. 88E8055 PCI-E Gigabit Ethernet Controller (rev 12)
using sky2 module.
The same problem occurs after resume from suspend (I didn't know about that due
to another bug with suspend mode and a blank screen which partially seems to be
fixed in a current version).
(This is a mass-update to all current FC6 kernel bugs in NEW state)
I'm reviewing this bug list as part of the kernel bug triage project, an attempt
to isolate current bugs in the Fedora kernel.
I am CC'ing myself to this bug, however this version of Fedora is no longer
Please attempt to reproduce this bug with a current version of Fedora (presently
Fedora 8). If the bug no longer exists, please close the bug or I'll do so in a
few days if there is no further information lodged.
Thanks for using Fedora!
Unfortunately I don't have that laptop now (and probably won't have in the
nearest future), so I can't confirm that bug with recent version.
Maybe someone else could check it. If not feel free to close this bug. After all
it could be always reopened if the new facts occurred.