Red Hat Bugzilla – Bug 436202
ipw3945 on Dell Precision M6300 inconsistently able to reconnect after suspend
Last modified: 2013-02-19 00:14:47 EST
Description of problem:
ipw3945 on Dell Precision M6300 inconsistently able to reconnect after suspend.
As per my comment in bug #362421, I have seen very inconsistent behavior on
actually connecting to a WAP after a suspend, where sometimes it tries three
times, keeps losing the connection, but succeeds on the third try. Other times,
it entirely fails to connect. And this is to a WAP running wpa personal, so
radius is not getting in the way, and another machine is perfectly happily
connected to it.
Hibernate seems to pretty much be able to connect after resuming. Not sure why
suspend cannot always do so.
It is also visibly slower - entirely aside from built in delays to _starting_ to
connect. Or at least it seems so - as compared to on boot or during normal use.
Version-Release number of selected component (if applicable):
Most of the time.
Steps to Reproduce:
1. Get the system specified above, with the relevant NM version.
2. Connect to a WAP.
3. Suspend, then resume.
May or may not be able to connect, at all, or without trying multiple times.
Should just work.
Not a regression. Cannot be, since previously the device was unavailable after
suspend or hibernate.
Not going to get fixed for RHEL5 but shouldn't be a problem in RHEL6.