[Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
auspex
auspex at pointerstop.ca
Thu Nov 17 14:19:30 UTC 2016
btw, merely restarting Network Manager never worked for me. I have to
remove iwlwifi and reload it.
derek
On Thu, Nov 17, 2016 at 2:18 PM, Derek Broughton <auspex at pointerstop.ca>
wrote:
> We used to have this. I'm sure, a decade ago, I could actually tell
> whatever was managing the hibernate/suspend, in the gui, to remove certain
> kernel modules on suspend and load them on resume. Now we're right back to
> needing it.
>
> derek
>
> On Thu, Nov 17, 2016 at 1:59 PM, Hans Deragon <hans at deragon.biz> wrote:
>
>> This serious issue is dragging to long. People want computers that
>> "just work". If pinpointing the source of the problem is difficult and
>> few resources are available, why not package a workaround that restarts
>> NetworkManager upon resume?
>>
>> Attached is my workaround. Works nicely. Finally, I have a computer
>> that "just works" and it's not a Mac (well, I have other issues but this
>> one is solved).
>>
>> Simple move the script under /lib/systemd/system-sleep and ensure it is
>> executable.
>>
>> ** Attachment added: "Workaround that restarts the NetworkManager upon
>> resume."
>> https://bugs.launchpad.net/ubuntu/+source/network-manager/+
>> bug/1585863/+attachment/4778652/+files/NetworkManagerR
>> estartWorkaroundForBug1380480.sh
>>
>> --
>> You received this bug notification because you are subscribed to a
>> duplicate bug report (1448555).
>> https://bugs.launchpad.net/bugs/1585863
>>
>> Title:
>> WiFi malfunction after suspend & resume stress - sudo wpa_cli scan
>> required to fix it.
>>
>> To manage notifications about this bug go to:
>> https://bugs.launchpad.net/network-manager/+bug/1585863/+subscriptions
>>
>
>
--
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 NetworkManager:
New
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/network-manager/+bug/1585863/+subscriptions
More information about the Ubuntu-sponsors
mailing list