[SOLVED] No network connection after suspend

matkam · 2018-03-07 05:44:00

I'm seeing the same issue on my wired Ethernet connection, using the "sky2" driver module (instead of "r8169"). The same modprobe workaround mentioned above works. Thanks for that! It will save having to reboot.

Last edited by matkam (2018-03-07 05:45:23)

Cabbage_c · 2018-03-07 06:36:36

Currently, reload the r8169 module works fine for me.
I run a Arch/Windows10 dual boot on the laptop. But here's the really wired thing. I suspend it to RAM in Arch, then wake it up, and ethernet won't work. Fine, so I REBOOT it to windows directly, and the ethernet won't work in windows as well, tried the hell out of it... However, if I poweroff the laptop then boot it up instead of just do a REBOOT, the ethernet works again, for both Arch and windows!
I thought it was some hardware problem of the ethernet card before this thread. It's really interesting that some kernel/driver bug should do something to even another system! Or maybe reboot itself isn't a real re-boot, some low level info still remains in RAM?

seth · 2018-03-07 08:06:58

REBOOT it to windows directly, and the ethernet won't work in windows as well

Sounds like you've windows fastboot enabled?

Cavsfan · 2018-03-12 20:51:14

seth wrote:

REBOOT it to windows directly, and the ether net won't work in windows as well
Sounds like you've windows fastboot enabled?

I'm curious about that too.

I've got Xubuntu 16.04.4 LTS on my pc and it does not have this problem.

Xubuntu 18.04 LTS in development definitely does and other people have the same problem using the r8169 driver with the 4.15 kernel.

Myself, I have had zero problems with Windows 10 as far as this problem goes. But, this is an old PC and no fastboot.

However I am getting an upgrade soon to a killer PC and fast boot is currently set on that one.

Cabbage_c · 2018-03-13 10:19:08

seth wrote:

REBOOT it to windows directly, and the ethernet won't work in windows as well
Sounds like you've windows fastboot enabled?

No, fastboot is disabled.

razerraz · 2018-03-15 14:11:47

Problem solved with today's NM upgrade (1.10.6-1), at least for me.

Cavsfan · 2018-03-15 22:59:54

I seen that update and was hopeful but, nothing here, still the same thing.

lula · 2018-03-17 14:17:34

I can confirm what razerraz wrote, one of these seems to have fixed it for me too, suspended three times and after reactivating the NM-profile the connection was up again w/o reloading the module

[2018-03-15 19:52] [ALPM] upgraded linux (4.15.8-1 -> 4.15.9-1)
[2018-03-15 19:52] [ALPM] upgraded networkmanager (1.10.5dev+3+g5159c34ea-1 -> 1.10.6-1)

Cavsfan · 2018-03-17 17:02:22

lula wrote:

I can confirm what razerraz wrote, one of these seems to have fixed it for me too, suspended three times and after reactivating the NM-profile the connection was up again w/o reloading the module
[2018-03-15 19:52] [ALPM] upgraded linux (4.15.8-1 -> 4.15.9-1)
[2018-03-15 19:52] [ALPM] upgraded networkmanager (1.10.5dev+3+g5159c34ea-1 -> 1.10.6-1)

My system is totally up to date and I can confirm that with those same updates, my system still loses internet connectivity after a suspend. I just tried it.

What does "reactivating the NM-profile" entail?

lula · 2018-03-18 09:38:01

Probably "reactivating" was kind of misleading, the connection was suspended and i had to reconnect to my wired network e.g. with

nmcli con up id home

I' not sure, if this was the same behaviour as before, i think it was reconnecting automatically

Last edited by lula (2018-03-18 09:39:57)

Cavsfan · 2018-03-18 22:08:15

lula wrote:

Probably "reactivating" was kind of misleading, the connection was suspended and i had to reconnect to my wired network e.g. with
nmcli con up id home
I' not sure, if this was the same behaviour as before, i think it was reconnecting automatically

So, you still have to intervene? Nothing works here except modprobe -r r8169, waiting a few seconds and then modprobe r8169.
Then when it's coming up, the nm-applet in the Xfce panel has a circle going around for probably 5 seconds, then a box pops up and says "connected".

Even seth's fix does not work any more. I was hoping to put that back in and be done with this for a while.

seth · 2018-03-19 08:38:39

https://bbs.archlinux.org/viewtopic.php … 2#p1769792 just automizes

modprobe -r r8169, [waiting a few seconds - this part is not in the script, but you could add a "sleep 5" if it's crucial] and then modprobe r8169

Last edited by seth (2018-03-19 08:39:01)

Cavsfan · 2018-03-19 20:45:14

seth wrote:

https://bbs.archlinux.org/viewtopic.php … 2#p1769792 just automizes
modprobe -r r8169, [waiting a few seconds - this part is not in the script, but you could add a "sleep 5" if it's crucial] and then modprobe r8169

I put sleep 5 in it and that didn't work. I tried typing it in terminal to start it and that didn't work. So, I waited for a while then the command took via terminal finally sudo modprobe r8169.

dmesg:

[  425.504597] Restarting tasks ... done.
[  425.509212] PM: suspend exit
[  425.557476] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  425.562130] r8169 0000:03:00.0 eth0: link down
[  425.562179] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  427.111456] do_IRQ: 1.36 No irq handler for vector
[  429.969243] ata3.00: ACPI cmd ef/03:45:00:00:00:a0 (SET FEATURES) filtered out
[  429.969246] ata3.00: ACPI cmd ef/03:0c:00:00:00:a0 (SET FEATURES) filtered out
[  429.969342] ata3.00: ACPI cmd c6/00:10:00:00:00:a0 (SET MULTIPLE MODE) succeeded
[  429.969344] ata3.00: ACPI cmd f5/00:00:00:00:00:00 (SECURITY FREEZE LOCK) filtered out
[  429.993926] ata3.00: configured for UDMA/133
[  577.722573] r8169 Gigabit Ethernet driver 2.3LK-NAPI loaded
[  577.723771] r8169 0000:03:00.0 eth0: RTL8101e at 0x000000005426ba5c, 00:24:21:51:21:3a, XID 94200000 IRQ 27
[  577.732588] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  577.737086] r8169 0000:03:00.0 eth0: link down
[  577.737149] IPv6: ADDRCONF(NETDEV_UP): eth0: link is not ready
[  579.369660] r8169 0000:03:00.0 eth0: link up
[  579.369670] IPv6: ADDRCONF(NETDEV_CHANGE): eth0: link becomes ready

I'll try it with a 30 second wait.

Cavsfan · 2018-03-19 22:33:05

Nope 30 seconds did not even work - nient.

I had to enter both commands via terminal. Then a slow revolving circle on the NM applet appeared and connected after several seconds.

I guess it's better than a reboot

seth · 2018-03-20 07:05:42

Tried also to wait before removing the module?

sjanktie · 2018-03-23 15:21:23

I've the same problem. It started with an update of the regular Linux kernel. That's why I switched to the LTS kernel. After a while I had the same problem with the LTS kernel.

I build my own version of (patched) network manager. Because of this I've put NM to the IgnorePkg list in pacman.conf so that it's updated only when I want it to be. NM was working perfectly and I haven't updated it in a while, but then the problem started, so I updated NM to see if that would fix the problem. It didn't. I'm quite sure that the root of the problem is not a NM, but I think NM intensifies the problem. When the problem started in the regular Linux kernel and when I switched to LTS I had the same NM version. This combination worked for about a week or two. If it was a NM problem this would not have worked at all.

After a suspend my laptop had no network connection (wired - r8169), but I was able to get a wireless connection with NM. To get a wired connection I tried this:

# modprobe -r r8169
# modprobe  r8169
# dhcpcd eth0
... no wired connection

That didn't work, but it did after stopping NM.

# modprobe -r r8169
# modprobe  r8169
# systemctl stop NetworkManager
# dhcpcd eth0
... wired connection

Running the following commands after a wake up fixes the problem for me:

# modprobe -r r8169
# modprobe  r8169
# systemctl restart NetworkManager

Last edited by sjanktie (2018-03-23 15:46:14)

Cavsfan · 2018-03-25 22:37:54

seth wrote:

Tried also to wait before removing the module?

Yes, I put a wait before and after everything.

The only thing that works is to enter it in terminal

sudo modprobe -r r8169

then after a few seconds:

sudo modprobe -r r8169

But, I do not have to touch Network manager itself.

I see the NM-applet spinning in a circle for several seconds before it re-connects, then it's good.

Right now my conky is telling me I have 60 updates waiting. I hope one of them fixes this problem.

Cavsfan · 2018-03-25 23:47:32

There were 2 network related updates in the 60 but, it is still the same.

extra/glib-networking               2.54.1-1               -> 2.56.0-1
    Network extensions for GLib
extra/networkmanager-openvpn        1.8.1dev+10+ge4d8cda-2 -> 1.8.2-1
    NetworkManager VPN plugin for OpenVPN

The one thing that does work besides typing the 2 commands into terminal is my alias.

[cavsfan@Le-Beast ~]$ cat .bashrc | grep fix-internet
alias fix-internet="sudo modprobe -r r8169 && sleep 10 && sudo modprobe r8169"

acidicX · 2018-04-16 19:21:50

I'm also having the exact same symptoms. @seth your systemd script "fixes" it for me - thanks for sharing.
@Cavsfan maybe you forgot to chmod +x the systemd script?

Last edited by acidicX (2018-04-16 19:22:14)

Cavsfan · 2018-04-17 22:06:42

acidicX wrote:

I'm also having the exact same symptoms. @seth your systemd script "fixes" it for me - thanks for sharing.
@Cavsfan maybe you forgot to chmod +x the systemd script?

No, it was working for me at first.

I did a fresh install of Arch on a new computer and am just using dhcpcd.service. I am not having this problem.
It does not even blink when it wakes from suspend to re-connect.

So, does that not prove that networkmanager is the problem?

I still have my old computer and will switch it to dhcpcd.service as soon as I can to see if that does fix it.
Been busy copying stuff over to the new one. Installed Windows 10 and Arch both UEFI.

Last edited by Cavsfan (2018-04-22 16:00:20)

rsmarples · 2018-04-18 14:57:02

progandy wrote:

If you remove networkmanager, then you have to configure your network in another way, e.g. manually or with systemd-networkd, dhcpcd, wpa_supplicant, netctl, wicd or connman, ...
https://wiki.archlinux.org/index.php/Ne … figuration
https://wiki.archlinux.org/index.php/Wi … figuration

The first wiki page comparison matrix is incorrect - dhcpcd does have an official GUI for GTK+ and Qt.
It's also lacking an entry in the equivalent wireless matrix as well.

https://aur.archlinux.org/packages/dhcpcd-ui/

There is an LXDE plugin floating around somwhere as well.

Cavsfan · 2018-04-22 16:08:18

It works on my old computer too. So, networkmanager must be the problem.

I did this first:

sudo systemctl enable dhcpcd.service
sudo systemctl start dhcpcd.service

Then removed network manager:

sudo pacman -R networkmanager-dispatcher-ntpd network-manager-applet networkmanager

Put the computer to sleep for about 20 minutes and upon resume, access to the network resumed too.

I'm going to consider this problem resolved.

JonnyRobbie · 2018-06-20 19:07:25

This problem still seems to persist for me even with the 4.17 kernel. There are two [1][2] bugreports at kernel, which gave me hope, especially given that the second one was marked as solved in 4.17, but I guess it was a different issue.

Removing networkmanager seems to be a hacky workaround at best - not a real solution. Has anyone manage to actually solve this or is there at least some bugreport I can track meanwhile?

saurabh000345 · 2019-05-13 14:07:29

I discovered that somehow implicitly, r8169 module had been blacklisted. So just deleting the /etc/modprobe.d/r8169_blacklist.conf worked for me

thejacer87 · 2019-07-15 19:06:26

saurabh000345 wrote:

I discovered that somehow implicitly, r8169 module had been blacklisted. So just deleting the /etc/modprobe.d/r8169_blacklist.conf worked for me

just want to chime in here, removing this blacklist worked for me too. not sure if it's a deeper issue, or if this could cause problems down the road.

just wanted to say if worked for me in case someone else is wondering what will work

Arch Linux

#51 2018-03-07 05:44:00

Re: [SOLVED] No network connection after suspend

#52 2018-03-07 06:36:36

Re: [SOLVED] No network connection after suspend

#53 2018-03-07 08:06:58

Re: [SOLVED] No network connection after suspend

#54 2018-03-12 20:51:14

Re: [SOLVED] No network connection after suspend

#55 2018-03-13 10:19:08

Re: [SOLVED] No network connection after suspend

#56 2018-03-15 14:11:47

Re: [SOLVED] No network connection after suspend

#57 2018-03-15 22:59:54

Re: [SOLVED] No network connection after suspend

#58 2018-03-17 14:17:34

Re: [SOLVED] No network connection after suspend

#59 2018-03-17 17:02:22

Re: [SOLVED] No network connection after suspend

#60 2018-03-18 09:38:01

Re: [SOLVED] No network connection after suspend

#61 2018-03-18 22:08:15

Re: [SOLVED] No network connection after suspend

#62 2018-03-19 08:38:39

Re: [SOLVED] No network connection after suspend

#63 2018-03-19 20:45:14

Re: [SOLVED] No network connection after suspend

#64 2018-03-19 22:33:05

Re: [SOLVED] No network connection after suspend

#65 2018-03-20 07:05:42

Re: [SOLVED] No network connection after suspend

#66 2018-03-23 15:21:23

Re: [SOLVED] No network connection after suspend

#67 2018-03-25 22:37:54

Re: [SOLVED] No network connection after suspend

#68 2018-03-25 23:47:32

Re: [SOLVED] No network connection after suspend

#69 2018-04-16 19:21:50

Re: [SOLVED] No network connection after suspend

#70 2018-04-17 22:06:42

Re: [SOLVED] No network connection after suspend

#71 2018-04-18 14:57:02

Re: [SOLVED] No network connection after suspend

#72 2018-04-22 16:08:18

Re: [SOLVED] No network connection after suspend

#73 2018-06-20 19:07:25

Re: [SOLVED] No network connection after suspend

#74 2019-05-13 14:07:29

Re: [SOLVED] No network connection after suspend

#75 2019-07-15 19:06:26

Re: [SOLVED] No network connection after suspend

Board footer