Sometimes WLAN detects no SSID after s3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
NetworkManager |
New
|
Undecided
|
Unassigned | ||
OEM Priority Project |
Fix Released
|
Undecided
|
Unassigned | ||
network-manager (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Steps to reproduce]
1. Boot into OS
2. Do s3 a few times
3. Check if wifi is still working after s3
[Expected results]
wifi still working correctly after s3
[Actual results]
1. Wifi shows "disconnected" in network-manager (both in applet and from command "nmcli d status")
2. Only one random SSID is displayed in network-manager applet, but wifi connection cannot be established at all with this SSID. Clicking on the SSID results in pop up window in the comment #2 below
3. "nmcli d wifi rescan" does not resolve issue
4. "iwlist [interface] scan" returns nothing and does not reolve issue
5. "nmcli d wifi connect [any SSID that you know should exist]" results in SSID not found and does not resolve issue
6. "sudo service network-manager restart", warm boot, cold boot resolves issue
[Details]
OS: Xenial based OEM image
WLAN module: Marvel [11ab:2b38]
network-manager:
- 1.2.0-0ubuntu0.
- 1.1.93 (fail rate 1/15)
network-manager applet screenshot when issue occurred:
Wifi is shown as "disconnected" and only one random SSID is displayed