Bug 483288

Summary:	Network Disabled after Suspend
Product:	[Fedora] Fedora	Reporter:	Daryll <daryll>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	10	CC:	carstenblaauw, cbredesen, dcbw, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-02-03 16:49:45 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Daryll 2009-01-30 17:57:07 UTC

My laptop can seems to suspend and restore correctly, but in about 1/3 of the cases after the resume NetworkManager will indicate that networking is disabled. If I then do a 'server NetworkManager restart' NetworkManager recognizes that the networking is enabled and finds the wireless correctly. It seems like a race condition where during a resume NetworkManager will sometimes check too early and find that networking has not yet been enabled.

NetworkManager-0.7.0-1.git20090102.fc10.i386
Linux ninja 2.6.27.9-159.fc10.i686 #1 SMP Tue Dec 16 15:12:04 EST 2008 i686 i686 i386 GNU/Linux

Comment 1 Chris Bredesen 2009-01-31 22:19:05 UTC

I'm experiencing this as well on my Dell D620.

0c:00.0 Network controller: Intel Corporation PRO/Wireless 3945ABG Network Connection (rev 02)
NetworkManager-0.7.0-1.git20090102.fc10.i386
Linux interlagos 2.6.27.12-170.2.5.fc10.i686 #1 SMP Wed Jan 21 02:09:37 EST 2009 i686 i686 i386 GNU/Linux

When I re-enable networking, it usually takes several seconds (up to a minute) to re-detect my WiFi access point.  But the main issue is that networking is disabled.  I'm happy to provide any extra logging you need to diagnose this.

Comment 2 Dan Williams 2009-02-03 16:49:45 UTC


*** This bug has been marked as a duplicate of bug 477964 ***

Comment 3 cblaauw 2009-02-27 13:44:35 UTC

*** Bug 487062 has been marked as a duplicate of this bug. ***