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

[Tony Espy]

I've reproduced this on a Thinkpad 410s running 16.04 LTS.  The version
of network-manager I used is the latest from xenial-updates:
1.2.2-0ubuntu0.16.04.3.

A few comments:

1) The fwts s3 test uses a low-level API to exercise suspend/resume.
I've been working with the fwts maintainer on an extension to fwts that
allows it to call out to a hook script on each iteration.  This makes it
possible to ensure that scanning is active for each iteration.

2) I've done some preliminary testing of the version of NM in xenial-
proposed (1.2.4-0ubuntu0.16.04.1), and although it looked promising at
first, I was still able to reproduce the bug.

3) We're pretty sure we know which patch [1] caused the issue, and are
working to determine the best way to fix it.  The fix provided in
comment #5 appears to resolve it, but unfortunately it breaks the
original patch's behavior.

@taiebot65

It sounds like you're hitting a different problem, so it'd probably be
best if you filed a new bug.

[1] wifi-Signal-on-the-wifi-device-when-its-supplicant-i.patch

-- 
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:
  New
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