Bugzilla – Bug 1897
Wireless connection can't auto recover after resume from S3/S4
Last modified: 2009-05-12 20:06:41
You need to log in before you can comment on or make changes to this bug.
Test Environment: =============================================== Platform : Intel SDV M3M31/M3X15/M3M41 Wireless Card : Intel(R) WiFi Link 4965/3945/5100/5300 OS : Redhat Fedora release 10 (Cambridge) 32/64bit AP : Cisco 1250 uCode : iwlwifi-4965-2.ucode 228.57.2.23 iwlwifi-3945-2.ucode 15.28.2.8 iwlwifi-5000-1.ucode 5.4.1.16 iwlwifi-5000-1.ucode 7.10.1.88 Source : commit f7c63e2fa7f0fcbf87bef267811df7ef428989a4 1c5aa89e92c47f73bf11003824db95200b0ea5cf(5300 card) issue: 4965/5100 cards can't get ping packets after suspend to RAM; 3945/5300 cards will lose connection after suspend to RAM. Steps to Reproduce: 1. reload driver 2. ifconfig wlan0 up 3. iwconfig wlan0 channel <CHAN> essid <ESSID> 4. ifconfig wlan0 <IP_ADDR> 5. ping <IP_SERVER> 6. echo -n mem > /sys/power/state 7. iwconfig wlan0 ----> verify lose connection 8. ping <IP_SERVER> again ----> 100% lose ping packets
miss step between step 6 and 7, resume from RAM suspend.
retested on commit c899ae03fd264e58f034bb9b7938c8a23165efaf with Intel(R) WiFi Link 4965. after resuming from disk or memory, need to rerun "iwconfig wlan0 essid <SSID>" to reconnect with AP.
3945/4965/5100/5300 cards also lose connection after resume from S4 on the latest development tree. source: commit 4185209098052218256d7f57cf2d98e14815328d (3945/5300) commit 37c528166103f362138eac869f0ea68d36046275 (4965) commit c899ae03fd264e58f034bb9b7938c8a23165efaf (5100)
NetworkManager: If use NetworkManager & can’t auto recover, please report a NM bug. There is a manual way as workaround. Command line: 1. after resume from S3, please reset channel, essid … to associate with AP again. 2. after resume from S4, please reset channel, essid … to associate with AP again. If fail, do step3. 3. If it can’t work, please down & up interface, then reset it to associate with AP. If fail, do step4. 4. reload driver and reset channel, essid … to associate with AP. Since auto recovery is an unsupported feature now, it is supported by mac80211. Downgrade the priority to P2.
when I was testing on 2.6.27-rc2 with 3945 card, wireless connection did not lost after resuming from S3/S4. ping to AP worked fine. dmesg: ... Restarting tasks ... done. PM: Basic memory bitmaps freed e1000e: eth0 NIC Link is Up 100 Mbps Full Duplex, Flow Control: None 0000:02:00.0: eth0: 10/100 speed: disabling TSO wlan0: deauthenticated (Reason: 2) wlan0: direct probe to AP 00:1d:70:93:91:70 try 1 wlan0: direct probe to AP 00:1d:70:93:91:70 try 2 wlan0 direct probe responded wlan0: authenticate with AP 00:1d:70:93:91:70 wlan0: authenticated wlan0: associate with AP 00:1d:70:93:91:70 wlan0: RX ReassocResp from 00:1d:70:93:91:70 (capab=0x421 status=0 aid=1) wlan0: associated wlan0: deauthenticated (Reason: 1) wlan0: direct probe to AP 00:1d:70:93:91:70 try 1 wlan0 direct probe responded wlan0: authenticate with AP 00:1d:70:93:91:70 wlan0: authenticated wlan0: associate with AP 00:1d:70:93:91:70 wlan0: RX ReassocResp from 00:1d:70:93:91:70 (capab=0x421 status=0 aid=1) wlan0: associated
sorry, it should be linux kernel 2.6.30-rc2 in comment#5.
What are the contents of /etc/pm/config.d/suspend_modules?
We've tried on 3945, 4965, 5100, 5300,with different source code after 2.6.30-rc2, this issue was fixed. mark it as verified.
Abhijeet, I saw nothing under /etc/pm/config.d/.