PEPPY: WiFi sometimes fails to come up after suspend on 2.0beta1

[fullerth]

Running 2.0beta1, I didn't have this issue with v1.0 on the same hardware.

After resuming from a suspend caused by closing the lid[1] on my 720 the wifi fails to power up, but only about once per day. Most resumes reconnect with no issues.

Clicking on the wifi icon in the tray shows Enable Networking with a checkbox beside it, but Enable WiFi is no longer displayed.

I've been rebooting to fix the problem, let me know what logs might be helpful to diagnose the issue and I'll collect them next time it happens.

This may be related to #204?

[1] Edit: Turns out it's unlikely related to closing the lid

[fullerth]

This was happening daily, but has not recurred since. Closing for now, I'll reopen if I can figure out a method to reproduce.

[fullerth]

Reopening because something is happening with my machine. I've narrowed this down a bit more, though reproducability is still low. The issue is related to sleep modes, but I don't know exactly what. Recently I've seen the issue when I wake from suspend, not waking from a lid closure.

When it occurs I see the following at the end of dmesg:

[125180.962202] ath: phy0: Failed to allocate tx descriptors: -12
[125180.962439] ath9k 0000:01:00.0: Failed to initialize device
[125180.962764] ath9k: probe of 0000:01:00.0 failed with error -12

Workaround is to close the lid and reopen it. After reopening the lid I sometimes see the double arrow icon of a physical connection instead of the wifi icon.

There may be a relationship between this and my use of USB tethering of a mobile connection, but I haven't yet figured out solid steps to reproduce.

[dragon788]

This actually seems to be a bug with Ubuntu 16.04/Network Manager in general. There are tons of reports of the connection not coming back after suspend/resume, whether through lid close or selecting "suspend" from the menu. I've been able to workaround this by using the nmcli command to enable the wifi and then it will auto reconnect.

[fullerth]

Just had this occur again. I wasn't able to use nmcli as a workaround.

nmcli -p radio shows the wifi is still enabled:

====================================
           Radio switches
====================================
WIFI-HW  WIFI     WWAN-HW  WWAN    
------------------------------------
enabled  enabled  enabled  enabled 

However, nmcli -p device shows only the loopback:

=========================================
            Status of devices
=========================================
DEVICE  TYPE      STATE      CONNECTION 
-----------------------------------------
lo      loopback  unmanaged  --         

Whereas nmcli -p device after reboot shows the wifi device:

=============================================
              Status of devices
=============================================
DEVICE  TYPE      STATE      CONNECTION     
---------------------------------------------
wlp1s0  wifi      connected  KittehPalace 1 
lo      loopback  unmanaged  --             

I'm no nmcli expert, but I wasn't able to get the wifi device to appear, any thoughts?

[dragon788]

Does sudo network-manager restart get the device working again? Or check the syntax for systemd uses to restart.

On Jul 2, 2016, 1:53 PM, at 1:53 PM, Thomas Fuller notifications@github.com wrote:

Just had this occur again. I wasn't able to use nmcli as a
workaround.

nmcli -p radio shows the wifi is still enabled:

====================================
          Radio switches
====================================
WIFI-HW  WIFI     WWAN-HW  WWAN    
------------------------------------
enabled  enabled  enabled  enabled 

However, nmcli -p device shows only the loopback:

=========================================
           Status of devices
=========================================
DEVICE  TYPE      STATE      CONNECTION 
-----------------------------------------
lo      loopback  unmanaged  --         

Whereas nmcli -p device after reboot shows the wifi device:

=============================================
             Status of devices
=============================================
DEVICE  TYPE      STATE      CONNECTION     
---------------------------------------------
wlp1s0  wifi      connected  KittehPalace 1 
lo      loopback  unmanaged  --             

I'm no nmcli expert, but I wasn't able to get the wifi device to
appear, any thoughts?

---

You are receiving this because you commented.
Reply to this email directly or view it on GitHub:
#253 (comment)

[fullerth]

Upgraded to the 2.0 release and still seeing this issue intermittently

sudo network-admin restart does get the interface up and running again, so that's a good workaround.

[phreshbeatz]

This also happens to me on Falco, and has been happening since 1.0.

[dragon788]

If people are still running into this you can add a udev/powerd rule to trigger a restart of network-manager automatically after a wake from suspend, there are a few posts on StackOverflow with the details for Ubuntu.

[ghost]

Take a look at /lib/systemd/system-sleep/wifi.sh in most of the galliumos-device packages. We're already restarting NetworkManager and wpasupplicant when the system wakes from sleep on most devices.