|Summary:||iwl4965/Network Manager problem with suspend/resume|
|Product:||[Fedora] Fedora||Reporter:||Joel Eidsath <thras>|
|Component:||kernel||Assignee:||John W. Linville <linville>|
|Status:||CLOSED INSUFFICIENT_DATA||QA Contact:||Fedora Extras Quality Assurance <extras-qa>|
|Version:||9||CC:||cra, dcbw, james, kernel-maint, michael, wtogami|
|Fixed In Version:||Doc Type:||Bug Fix|
|Doc Text:||Story Points:||---|
|Last Closed:||2008-12-18 18:46:07 UTC||Type:||---|
|oVirt Team:||---||RHEL 7.3 requirements from Atomic Host:|
|Cloudforms Team:||---||Target Upstream Version:|
Description Joel Eidsath 2008-05-27 20:28:52 UTC
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. How reproducible: 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. Actual results: Network Manager does not reconnect. It sometimes asks for new secrets. It sometimes does not see most of the available wireless networks. Expected results: Network Manager should reconnect to the original wireless network, or to a new one with higher precedence, if available. Additional Info: I've attached the log file from a session that asked for new secrets. There are several iwl4965 errors.
Comment 1 Joel Eidsath 2008-05-27 20:28:53 UTC
Created attachment 306831 [details] Log of problem (identities changed to protect the innocent)
Comment 2 Dan Williams 2008-05-28 15:26:23 UTC
driver issue it seems
Comment 3 John W. Linville 2008-05-28 16:56:06 UTC
Can you recreate this issue with these kernels? http://koji.fedoraproject.org/koji/buildinfo?buildID=50055
Comment 4 Joel Eidsath 2008-05-28 18:42:38 UTC
Yes, the problem still exists. I updated to the 22.214.171.124-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.
Comment 5 John W. Linville 2008-08-25 20:24:17 UTC
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!
Comment 6 Michael Ekstrand 2008-09-08 16:28:02 UTC
I see similar behavior on 126.96.36.199-97.fc9.x86_64 (188.8.131.52-108.fc9 doesn't even let me connect to WPA networks, so I don't know if this problem is fixed there).
Comment 7 John W. Linville 2008-11-13 15:21:05 UTC
The WPA problem with -108.fc9 was corrected a long time ago. Can you try a current kernel?
Comment 8 John W. Linville 2008-12-18 18:46:07 UTC
Closed due to lack of reponse...