[Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.

[Tony Espy]

@taiebot65

Thanks.  I'll take a look.

Regarding this bug, it turns out that when I was testing my version of
NM with the dropped 'ScanDone' patch (wifi-Signal-on-the-wifi-
device...), I'd been doing so on top of the newly re-based 1.2.6, and it
turns out there was an actual fix in 1.2.6 which seems to fix the bug:

https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?h=nm-1-2&id=b749f7d31b7e5f57f18026a14b6a444e59a488cf

This new version of NM hasn't yet been SRU'd for xenial, as version
1.2.4-0ubuntu0.16.04.1 is still in -proposed.  I'll see if maybe we can
expedite this landing and skip 1.2.4 altogether.

Note, I've managed to run 200 cycles of S3 on my Thinkpad without
hitting the bug.  This included about 25 cycles of manual
suspend/resume, and 175 iterations using fwts.

-- 
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 - sudo wpa_cli scan
  required to fix it.

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

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=5 --s3-max-delay=5 --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/oem-priority/+bug/1585863/+subscriptions