Red Hat Bugzilla – Bug 448610
iwl4965/Network Manager problem with suspend/resume
Last modified: 2008-12-18 13:46:07 EST
Description of problem:
After suspend/resume, Network Manager sometimes fails to reconnect to the
network. Sometimes the list of available networks will be incomplete, and there
is no way to refresh it. Sometimes Network Manager will ask for new secrets to
reconnect to the old network. This may be related to bug 251072 filed for RHEL
5. Several iwl4965 errors appear in the attached log file.
The problem occurs frequently, but not every time.
Steps to Reproduce:
1. Connect to a wireless network using WPA/PSK.
2. Suspend the laptop.
3. Resume the laptop.
4. Wait for Network Manager to reconnect to the network.
Network Manager does not reconnect. It sometimes asks for new secrets. It
sometimes does not see most of the available wireless networks.
Network Manager should reconnect to the original wireless network, or to a new
one with higher precedence, if available.
I've attached the log file from a session that asked for new secrets. There are
several iwl4965 errors.
Created attachment 306831 [details]
Log of problem (identities changed to protect the innocent)
driver issue it seems
Can you recreate this issue with these kernels?
Yes, the problem still exists. I updated to the 220.127.116.11-30.fc9.x86_64 kernel
and booted into it. After closing the laptop to suspend it, I resumed, and it
found the network, although there was a delay before it attempted to connect,
which is unusual. /var/log/messages claimed that the wlan0 link timed out.
Then I repeated the experiment, closing the laptop again. The second time it
requested secrets before connecting, which was the initial problem.
However, all of the iwl4965 errors have now disappeared from the logs. They were
definitely present on the previous kernel.
Similar problems have been reported as gone with more recent kernels. Can you still observe this problem with current kernels? If so, please include the output of 'uname -r'...thanks!
I see similar behavior on 18.104.22.168-97.fc9.x86_64 (22.214.171.124-108.fc9 doesn't even let me connect to WPA networks, so I don't know if this problem is fixed there).
The WPA problem with -108.fc9 was corrected a long time ago. Can you try a current kernel?
Closed due to lack of reponse...