[Bug 1585863] Re: WiFi malfunction after suspend & resume stress

[Mathieu Trudel-Lapierre]

That seems wrong. This change was done because you might otherwise get
stray SCAN_DONE signals when the scan is in progress -- we should still
be getting a SCAN_DONE signal later from the supplicant when we get the
scan results. The issue here is that the scan may not be done correctly
on return from suspend, but I doubt that forcing a SCAN_DONE to look at
the scan results again is the right way to go about fixing this.

Since the issue can be resolved by asking the driver to scan again (via
wpa or via iw dev wlan0 scan) and only seems to apply for iwlwifi (as
far as I've heard), it would probably really point to either a driver or
a wpasupplicant bug.

Tony, what are your thoughts on this? I know you recently spent a lot of
time looking at the scanning/scan results logic?

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1585863

Title:
  WiFi malfunction after suspend & resume stress

Status in NetworkManager:
  New
Status in OEM Priority Project:
  New
Status in OEM Priority Project xenial series:
  New
Status in network-manager package in Ubuntu:
  New

Bug description:
  Description:    Ubuntu Yakkety Yak (development branch)                                                                                                                                                                                
  Release:        16.10
  Packages:
  libnm-glib-vpn1:amd64   1.2.2-0ubuntu2                                                                                                                                                                                                 
  libnm-glib4:amd64       1.2.2-0ubuntu2
  libnm-util2:amd64       1.2.2-0ubuntu2
  libnm0:amd64    1.2.2-0ubuntu2
  network-manager 1.2.2-0ubuntu2

  Reproduce steps:
  1. Install fwts by `sudo apt-get install fwts`.
  2. Run the suspend & resume stress test.
  sudo fwts s3 --s3-multiple=30 --s3-min-delay=10 --s3-max-delay=10 --s3-delay-delta=5

  Expected result:
  The WiFi still functioned.

  Actual result:
  The WiFi can not connect to any access point and we have to execute `sudo wpa_cli scan` manually to make it work again.

  P.S. Ubuntu 16.04 also has the same issue.

To manage notifications about this bug go to:
https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions