Seems to me that if NM stalls due to a race condition, then restarting NM *is* a workaround, so yes, adding additional scripts to systemd is a solution, but not the "answer".
derek On Fri, Feb 3, 2017 at 1:11 AM, Tony Espy <1585...@bugs.launchpad.net> wrote: > @Kevin > > NetworkManager already has code to monitor system signals related to > suspend/resume, so no adding additional scripts to /usr/lib/systemd > /system-sleep isn't the answer. > > @Dan > > Different bug... this bug is caused by NetworkManager's WiFi scanning > logic stalling due to a race condition. You can tell this by running > 'sudo wpa_cli' and watching for scan events. If you don't see any, then > you've hit the bug. > > I've also unfortunately confirmed that dropping the original patch from > 1.2.6 doesn't fix the problem either. I tried a cycle of 100 with my > version of 1.2.6 with the original ScanDone patch dropped and I still > tripped the bug. > > -- > 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/oem-priority/+bug/1585863/+subscriptions > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. 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 -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
