[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Fresh 16.04.1 install on ThinkPad X1 carbon 3 with stock Intel 7265 (802.11abgn) WiFi here; laptop also has a Sierra Wireless EM7345 4G LTE WWAN integrate USB module. Typical scenario: I use the WWAN when out and about, suspend the laptop, come back to office and expect the laptop to re-connect to WiFi. Typically the WWAN reconnects but the network mgr applet shows a stale list of WiFi access points (looks like they're from when I last suspended the laptop). Kern.log has below notices after resume from sleep regarding the WLAN adapter [1] I tried the following (several times in a row) from the above suggestions to restore my connection (in assumed descending order of "invasion"): 1. sudo wpa_cli scan 2. sudo rfkill block wifi; sleep 3; rfkill unblock wifi 3. sudo systemctl restart network-manager.service #3 did it this time but there was definitely a previous occurrence where it didn't help and only a reboot did. Just in case this helps shed some light on this lengthy thread. Would agree that this isn't Ubuntu's finest hour; sorry I cannot be more constructive. [1] ken.log Jan 6 10:31:49 cinamon5u NetworkManager[1270]: [1483695109.4803] device (wlp4s0): state change: unmanaged -> unavailable (reason 'managed') [10 20 2] Jan 6 10:31:49 cinamon5u kernel: [ 3239.333883] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:31:49 cinamon5u kernel: [ 3239.432191] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:31:49 cinamon5u NetworkManager[1270]: [1483695109.8678] device (wlp4s0): supplicant interface state: starting -> ready Jan 6 10:31:49 cinamon5u NetworkManager[1270]: [1483695109.8679] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jan 6 10:31:49 cinamon5u kernel: [ 3239.721341] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:33:19 cinamon5u NetworkManager[1270]: [1483695199.5763] device (wlp4s0): state change: disconnected -> unavailable (reason 'none') [30 20 0] Jan 6 10:33:23 cinamon5u kernel: [ .131109] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready Jan 6 10:33:23 cinamon5u NetworkManager[1270]: [1483695203.3310] device (wlp4s0): supplicant interface state: starting -> ready Jan 6 10:33:23 cinamon5u NetworkManager[1270]: [1483695203.3311] device (wlp4s0): state change: unavailable -> disconnected (reason 'supplicant-available') [20 30 42] Jan 6 10:33:23 cinamon5u kernel: [ .175963] IPv6: ADDRCONF(NETDEV_UP): wlp4s0: link is not ready -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: 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/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Also further to #60, I have put the following in mine (Thinkpad X1 Carbon 3) and it does indeed seem to fix the problem so far - been testing over a few days: /lib/systemd/system-sleep/wpasupplicant: post) (sleep 3 ; /sbin/wpa_cli resume) & ;; 16.04.1 fresh install, kernel 4.4.0-59; network-manager 1.2.2-0ubuntu0.16.04.3 Anything shorter than 3 seconds seems to be too fast for that race condition; could this suggest this might be better fixed with a systemd dependency? -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: 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/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1585863] Re: WiFi malfunction after suspend & resume stress - sudo wpa_cli scan required to fix it.
Hi @cascagrossa, just to clarify: my impression is that in order to trigger the bug you'll need to suspend somewhere where the WLAN network you want to connect to at resume time isn't available as it's the scan aspect of things that appears to be inhibited. This is evidenced by the fact that he network-mgr UI shows a stale list of WiFi networks when the bug manifests itself; I've don't *think* I've ever had this bug affect me in a stationary suspend/resume scenario. -- You received this bug notification because you are a member of Ubuntu Touch seeded 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: 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/oem-priority/+bug/1585863/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
[Touch-packages] [Bug 1566468] [NEW] systemd-modules-load.service: Failing due to missing module 'ib_iser'
Public bug reported: On a number of VMs using Xenial daily builds 20160330 and 20160403, out of the box (just after booting for the first time), the following appears in dmesg at boot time: systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Load Kernel Modules. systemd[1]: systemd-modules-load.service: Unit entered failed state. systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. The following related complaint appears in /var/log/syslog: ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp' ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser' It looks like 'ib_iser' is some Mellanox-related module, which I don't *think* is something that a stock cloudimg install should attempt to load but I may be wrong; in any case, it's not present (nor is there any similar whingeing) on similar VMs running off 14.04 cloudimg. More info: http://askubuntu.com/questions/753672/xenial-beta2-systemd- modules-load-service-failed-due-to-missing-module-ib-i --- root@testvm4:~# lsb_release -rd Description:Ubuntu Xenial Xerus (development branch) Release:16.04 root@testvm4:~# apt policy systemd systemd: Installed: 229-3ubuntu2 Candidate: 229-3ubuntu2 ** Affects: systemd (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to systemd in Ubuntu. https://bugs.launchpad.net/bugs/1566468 Title: systemd-modules-load.service: Failing due to missing module 'ib_iser' Status in systemd package in Ubuntu: New Bug description: On a number of VMs using Xenial daily builds 20160330 and 20160403, out of the box (just after booting for the first time), the following appears in dmesg at boot time: systemd[1]: systemd-modules-load.service: Main process exited, code=exited, status=1/FAILURE systemd[1]: Failed to start Load Kernel Modules. systemd[1]: systemd-modules-load.service: Unit entered failed state. systemd[1]: systemd-modules-load.service: Failed with result 'exit-code'. The following related complaint appears in /var/log/syslog: ubuntu systemd-modules-load[352]: Inserted module 'iscsi_tcp' ubuntu systemd-modules-load[352]: Failed to find module 'ib_iser' It looks like 'ib_iser' is some Mellanox-related module, which I don't *think* is something that a stock cloudimg install should attempt to load but I may be wrong; in any case, it's not present (nor is there any similar whingeing) on similar VMs running off 14.04 cloudimg. More info: http://askubuntu.com/questions/753672/xenial-beta2-systemd- modules-load-service-failed-due-to-missing-module-ib-i --- root@testvm4:~# lsb_release -rd Description: Ubuntu Xenial Xerus (development branch) Release: 16.04 root@testvm4:~# apt policy systemd systemd: Installed: 229-3ubuntu2 Candidate: 229-3ubuntu2 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1566468/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
