Bug 251072

Summary:	NetworkManager and ipw suspend/resume flakyness
Product:	Red Hat Enterprise Linux 5	Reporter:	Daniel Riek <riek>
Component:	NetworkManager	Assignee:	Dan Williams <dcbw>
Status:	CLOSED CURRENTRELEASE	QA Contact:	desktop-bugs <desktop-bugs>
Severity:	high	Docs Contact:
Priority:	high
Version:	5.0	CC:	jrb
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:	2008-09-30 02:01:47 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 Daniel Riek 2007-08-06 21:35:33 UTC

When suspending/resuming a system with RHEL5, Network manager often does not see
anymore Networks Interfaces after resume. This has been reproduced with ipw2100,
2200 and 3945 based wireless cards in Thinkpad laptops with 5.0 and 5.1 Beta.

It failed in 6 of 10 cases (tested approx. 40 cases).

While it at this point is unclear whether the problem is in NetworkManager or in
the wireless drivers, the fact that it also does not see the ethernet interface
suggests that it is NetworkManager. Restarting NetworkManager IS a workaround
that helped in every case during the test. At least in the caes tested for this,
also deactivating networking in the NetworkManager menue and then re-activating
it helped.

So a short term solution might be to add a NetworkManager restart to the
gnome-powermanagement quirks.

Comment 1 Christopher Aillon 2007-08-07 17:45:53 UTC

So, notting just ran into this issue as well and adding "sleep 2" just before
the dbus-send call fixes this.  Looks like a race...

Comment 2 Dan Williams 2008-03-28 18:10:03 UTC

This should be fixed in 5.2 by a combination of #215720 and #362421.  Can you
test with the version of NM in 5.2 Beta (0.6.4-7.el5) ?

Comment 3 Dan Williams 2008-09-30 02:01:47 UTC

This was fixed in 5.2 and fix will also be present in NM rebase in 5.3.