Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
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 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/ > NetworkManagerRestartWorkaroundForBug1380480.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 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 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:amd641.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 -- 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
Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
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 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 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 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 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:amd641.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 -- 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
Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
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:amd641.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
Re: [Desktop-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
You can try having the script do "modprobe -r" and "modprobe" on your wifi module. That should always work, but seemed like overkill in my case. In any case, these are workarounds, not fixes. On 4 Aug 2016 6:01 a.m., "Aleve Sicofante" wrote: > @auspex: Your script doesn't work here. I just created it and gave it > execution permissions, rebooted and tried a sleep/resume cycle. No dice. > > I'm just amazed no one from Canonical is chiming in. This has been > happening from the very moment I installed 16.04 on its release day and > it happens in the two laptops I use (Lenovo T400 and Dell Studio 1537, > both with Intel wireless cards). It's so obvious I didn't even try to > file a bug understanding it would be naturally solved by 16.04.1 at the > latest... I'm truly amazed in the worst sense. > > -- > 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 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 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:amd641.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 -- 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
