Bug 16082 - No Wired connection after suspend in Mageia 5 Xfce
Summary: No Wired connection after suspend in Mageia 5 Xfce
Status: RESOLVED OLD
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: Cauldron
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: NEEDINFO
Depends on:
Blocks:
 
Reported: 2015-06-05 12:28 CEST by MakkiC Qua
Modified: 2017-01-07 10:20 CET (History)
4 users (show)

See Also:
Source RPM:
CVE:
Status comment:


Attachments

Description MakkiC Qua 2015-06-05 12:28:17 CEST
Description of problem:
After suspend no wired connection, only wireless is showing.

Work perfectly after restart/shut down.

Mageia 5 Xfce 4.12 

Notebook Toshiba C660


How reproducible:
Only when put notebook to sleep/suspend.

After suspend:

.....# ifconfig
lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 346  bytes 26672 (26.0 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 346  bytes 26672 (26.0 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

After restart:

.....# ifconfig
enp2s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet XXX.XX.X.XX  netmask 255.255.255.0  broadcast XXX.XXX.X.XXX
        inet6 XXX::XXX:XXX:XXX:XXX  prefixlen 64  scopeid 0x20<link>
        ether XX:XX:XX:XX:XX:XX  txqueuelen 1000  (Ethernet)
        RX packets 8  bytes 1166 (1.1 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 23  bytes 2028 (1.9 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 0  (Local Loopback)
        RX packets 182  bytes 13600 (13.2 KiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 182  bytes 13600 (13.2 KiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

Thanks!


Reproducible: 

Steps to Reproduce:
Comment 1 Sander Lepik 2015-06-05 13:07:50 CEST
Could you please paste the output of the following command:

# lspcidrake -v |grep -i network

Also check your dmesg for error messages.

Keywords: (none) => NEEDINFO
CC: (none) => mageia, tmb

Comment 2 MakkiC Qua 2015-06-05 15:02:10 CEST
When i have wired connection:
# lspcidrake -v |grep -i network
ath9k           : Qualcomm Atheros|AR9285 Wireless Network Adapter (PCI-Express) [NETWORK_OTHER] (vendor:168c device:002b subv:144f subd:7173) (rev: 01)
r8169           : Realtek Semiconductor Co., Ltd.|RTL8101E/RTL8102E PCI Express Fast Ethernet controller [NETWORK_ETHERNET] (vendor:10ec device:8136 subv:1179 subd:fc30) (rev: 05)

after suspend the same command only show for wifi: ath9k...

Strange:
this is after suspend: http://www.dodaj.rs/f/1B/5r/Jxs4on6/screenshot2015-06-0514-4.png
but, if i disconnect cable when a notebook is in sleep, and power on, got this:
http://www.dodaj.rs/f/3a/uK/gNrn81/screenshot2015-06-0514-4.png
and now i connect cable, click connect and i have network connection.

No error messages about network in dmesg.
Comment 3 MakkiC Qua 2015-06-05 15:10:03 CEST
For more info:
I use btrfs partition for / and /home, no swap partition.
Installed from network install, only xfce ~ two mounths ago.
Comment 4 Sander Lepik 2015-06-05 15:33:26 CEST
It seems that for some reason the kernel module must be reloaded.

You could try this workaround:

create the following file: /etc/systemd/system/r8169-reload.service

[Unit]
Description=Reload r8169 lan driver after system resume
After=hibernate.target suspend.target hybrid-sleep.target

[Service]
Type=oneshot
ExecStart=/usr/sbin/modprobe -r r8169
ExecStart=/usr/sbin/modprobe r8169

[Install]
WantedBy=hibernate.target suspend.target hybrid-sleep.target

And then run these commands:

systemctl daemon-reload
systemctl enable r8169-reload.service

Try to reboot and suspend. You might need to check that it's actually r8169 that is loaded in your kernel.

This is just a possible workaround, maybe Thomas knows how to do it better.
Comment 5 MakkiC Qua 2015-06-05 17:26:42 CEST
Thanks for helping!

Above workaround not work, and i was enabled r8169-reload.service but not listed in systemctl list-units command. My fail, i should use systemctl --all.

In lsmod command r8169 module is listed before and after suspend, so modprobe r8169 is not needed.

$ ps -ef | grep -ie net -e wpa
root        25     2  0 17:01 ?        00:00:00 [netns]
systemd+  1103     1  0 17:04 ?        00:00:00 /usr/lib/systemd/systemd-networkd
makki     2536  2513  0 17:04 ?        00:00:03 /usr/lib64/xfce4/panel/wrapper-1.0 /usr/lib64/xfce4/panel/plugins/libnetload.so 5 23068712 netload Network Monitor Show network traffic
makki     2544  2499  0 17:04 ?        00:00:04 /usr/bin/perl /usr/bin/net_applet
makki     7883  7847  0 17:26 pts/0    00:00:00 grep --color -ie net -e wpa
Comment 6 Sander Lepik 2015-06-05 17:37:13 CEST
What happens if you manually try to remove the module and then reload it? Just to make sure that it's possible to remove the module and nothing else depends on it.
Comment 7 MakkiC Qua 2015-06-06 09:47:15 CEST
I didn't try.
Now in a message log found this:

Jun  6 09:32:14 mageia systemd-sleep[5285]: Suspending system...
Jun  6 09:32:25 mageia kernel: [ 1053.340067] r8169 0000:02:00.0: System wakeup enabled by ACPI
Jun  6 09:32:25 mageia kernel: [ 1053.451035] r8169 0000:02:00.0: Refused to change power state, currently in D3
Jun  6 09:32:25 mageia kernel: [ 1053.543100] r8169 0000:02:00.0: System wakeup disabled by ACPI
Jun  6 09:32:25 mageia kernel: [ 1053.543643] r8169 0000:02:00.0 enp2s0: rtl_phyar_cond == 1 (loop: 20, delay: 25).
Jun  6 09:32:25 mageia kernel: [ 1054.162443] r8169 0000:02:00.0 enp2s0: rtl_ephyar_cond == 1 (loop: 100, delay: 10).
Jun  6 09:32:25 mageia kernel: [ 1054.162462] r8169 0000:02:00.0 enp2s0: link up
Jun  6 09:32:25 mageia kernel: [ 1054.694474] r8169 0000:02:00.0 enp2s0: rtl_counters_cond == 1 (loop: 1000, delay: 10).
Jun  6 09:32:25 mageia kernel: [ 1054.706274] r8169 0000:02:00.0 enp2s0: rtl_chipcmd_cond == 1 (loop: 100, delay: 100).
Jun  6 09:32:25 mageia dhclient: receive_packet failed on enp2s0: Network is down
Jun  6 09:32:25 mageia systemd-networkd[1163]: enp2s0          : lost carrier
Jun  6 09:32:25 mageia ifplugd(enp2s0)[4210]: Failed to detect plug status of enp2s0
Jun  6 09:32:25 mageia ifplugd(enp2s0)[4210]: Exiting.
Jun  6 09:32:26 mageia ModemManager[1066]: <info>  (net/enp2s0): released by modem /sys/devices/pci0000:00/0000:00:1c.0/0000:02:00.0
Jun  6 09:32:27 mageia mgaapplet[2765]: Checking Network: seems disabled
Comment 8 Dariusz Bismor 2015-11-26 10:34:01 CET
I have a same situation here with KDE, and I think it is bootscript- or systemd-related. I'm so close to solve it, and I'm angry because I can't make the final step.

The symptom is that the IP is not refreshed after a suspend, and if you move your laptop meanwhile to another network, you still have the previous IP. 

I try to do a manual "systemctl restart network" (or reload) and an error pops up, after "systemctl status network.service" I have:
systemctl status network.service
â network.service - LSB: Bring up/down networking
   Loaded: loaded (/etc/rc.d/init.d/network)
   Active: failed (Result: exit-code) since czw 2015-11-26 08:13:02 CET; 11s ago
  Process: 22055 ExecStart=/etc/rc.d/init.d/network start (code=exited, status=1/FAILURE)
   CGroup: /system.slice/network.service
           ââ 1305 /sbin/ifplugd -I -b -i wlp2s0
           ââ17147 /sbin/ifplugd -I -b -i enp0s25
           ââ17214 /usr/sbin/wpa_supplicant -B -i wlp2s0 -c /etc/wpa_supplica...

I'v also tried "service network restart", with the same.

I've found out that "systemctl stop network" or "service network stop" does not shut down both the ifplugd daemons. If I kill them, and then do "service network start", the above error still appears, but the network is fine. And I don't know how to solve this graciously, killing ifplugd-s doesn't seem fine to me.

CC: (none) => Dariusz.Bismor

Comment 9 Marja Van Waes 2016-12-08 10:39:21 CET
Is this issue still valid?

CC: (none) => marja11

Comment 10 Marja Van Waes 2017-01-07 10:20:29 CET
No reply, and Cauldron changed a lot since 2015.

Closing as OLD

Status: NEW => RESOLVED
Resolution: (none) => OLD


Note You need to log in before you can comment on or make changes to this bug.