Bug 251072 - NetworkManager and ipw suspend/resume flakyness
Summary: NetworkManager and ipw suspend/resume flakyness
Alias: None
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: NetworkManager
Version: 5.0
Hardware: All
OS: Linux
Target Milestone: ---
: ---
Assignee: Dan Williams
QA Contact: desktop-bugs@redhat.com
Depends On:
TreeView+ depends on / blocked
Reported: 2007-08-06 21:35 UTC by Daniel Riek
Modified: 2008-09-30 02:01 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2008-09-30 02:01:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

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.

Note You need to log in before you can comment on or make changes to this bug.