View Issue Details

IDProjectCategoryView StatusLast Update
0016486CentOS-7kernelpublic2019-10-21 00:37
Reporterkrbvroc1 
PrioritynormalSeveritymajorReproducibilityalways
Status newResolutionopen 
Product Version7.7-1908 
Target VersionFixed in Version 
Summary0016486: After 7.6->7.7 update, r8169 WOL no longer works
DescriptionI had a system running for several 7.x update cycles with a Realtek motherboard NIC. I have the BIOS set to Wake on LAN (note this is not only MagicPacket). Any LAN traffic that reaches the NIC would wake the server out of suspend (systemctl suspend). After updating to 7.7 this no longer works. Pressing the power button works to wake the device, but network traffic no longer does (I even tried a magic packet).

03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 15)
    Subsystem: Intel Corporation Device 2060
    Flags: bus master, fast devsel, latency 0, IRQ 18
    I/O ports at e000 [size=256]
    Memory at 81204000 (64-bit, non-prefetchable) [size=4K]
    Memory at 81200000 (64-bit, non-prefetchable) [size=16K]
    Capabilities: [40] Power Management version 3
    Capabilities: [50] MSI: Enable- Count=1/1 Maskable- 64bit+
    Capabilities: [70] Express Endpoint, MSI 01
    Capabilities: [b0] MSI-X: Enable+ Count=4 Masked-
    Capabilities: [d0] Vital Product Data
    Capabilities: [100] Advanced Error Reporting
    Capabilities: [140] Virtual Channel
    Capabilities: [160] Device Serial Number 01-00-00-00-68-4c-e0-00
    Capabilities: [170] Latency Tolerance Reporting
    Capabilities: [178] L1 PM Substates
    Kernel driver in use: r8169
    Kernel modules: r8169

ethtool shows WOL (g) is enabled:
    Supports Wake-on: pumbg
    Wake-on: ug
    Current message level: 0x00000033 (51)
                   drv probe ifdown ifup
    Link detected: yes
TagsNo tags attached.
abrt_hash
URL

Relationships

related to 0016413 assignedtoracat After update from 7.6 to 7.7 network card does not connect 

Activities

krbvroc1

krbvroc1

2019-09-28 19:51

reporter   ~0035263

Note that booting the previous kernel works:
3.10.0-957.27.2.el7.x86_64 #1 SMP Mon Jul 29 17:46:05 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

The upgrade to the current 3.10.0-1062 is what breaks this.
fpaquet

fpaquet

2019-10-06 07:37

reporter   ~0035341

Same issue here on 3 of 4 workstations. The 4. workstation is waking up on WoL.

[bsa.opag.ch:/root] ethtool enp7s0
Settings for enp7s0:
    Supported ports: [ TP AUI BNC MII FIBRE ]
    Supported link modes: 10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Half 1000baseT/Full
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes: 10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Half 1000baseT/Full
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                         100baseT/Half 100baseT/Full
                                         1000baseT/Half 1000baseT/Full
    Link partner advertised pause frame use: Symmetric Receive-only
    Link partner advertised auto-negotiation: Yes
    Link partner advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Port: MII
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: pumbg
    Wake-on: g
    Current message level: 0x00000033 (51)
                   drv probe ifdown ifup
    Link detected: yes

[bsa.opag.ch:/root] lspci
...
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)

---
BIOS ACPI Sleep mode is set to S3.
fpaquet

fpaquet

2019-10-06 07:42

reporter   ~0035342

Looking at the 4. workstation (host montesa), where WoL is working:

[root] ping montesa
PING montesa (192.1.1.15) 56(84) bytes of data.
^C
--- montesa ping statistics ---
2 packets transmitted, 0 received, 100% packet loss, time 1001ms

[root] ether-wake montesa
[root] ping montesa
PING montesa (192.1.1.15) 56(84) bytes of data.
From dhcp-118 (192.1.1.118) icmp_seq=1 Destination Host Unreachable
...
From dhcp-118 (192.1.1.118) icmp_seq=36 Destination Host Unreachable
64 bytes from montesa (192.1.1.15): icmp_seq=37 ttl=64 time=2326 ms
64 bytes from montesa (192.1.1.15): icmp_seq=38 ttl=64 time=1326 ms
---

[root@montesa:/root] ethtool enp7s0
Settings for enp7s0:
    Supported ports: [ TP MII ]
    Supported link modes: 10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Half 1000baseT/Full
    Supported pause frame use: No
    Supports auto-negotiation: Yes
    Supported FEC modes: Not reported
    Advertised link modes: 10baseT/Half 10baseT/Full
                            100baseT/Half 100baseT/Full
                            1000baseT/Half 1000baseT/Full
    Advertised pause frame use: No
    Advertised auto-negotiation: Yes
    Advertised FEC modes: Not reported
    Link partner advertised link modes: 10baseT/Half 10baseT/Full
                                         100baseT/Half 100baseT/Full
                                         1000baseT/Full
    Link partner advertised pause frame use: Symmetric
    Link partner advertised auto-negotiation: Yes
    Link partner advertised FEC modes: Not reported
    Speed: 1000Mb/s
    Duplex: Full
    Port: MII
    PHYAD: 0
    Transceiver: internal
    Auto-negotiation: on
    Supports Wake-on: pumbg
    Wake-on: d
    Current message level: 0x00000033 (51)
                   drv probe ifdown ifup
    Link detected: yes
--
[root@montesa:/root] lspci | grep Eth
07:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 06)
fpaquet

fpaquet

2019-10-06 07:49

reporter   ~0035343

differences in output of ethtool:

montesa: Supported ports: [ TP MII ]
bsa: Supported ports: [ TP AUI BNC MII FIBRE ]

---
[root@montesa:/root] cat /etc/sysconfig/network-scripts/ifcfg-enp7s0
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=none
DEFROUTE=yes
IPV4_FAILURE_FATAL=no
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp7s0
UUID=b77ad498-6d0a-4f1a-994d-6da616931f12
DEVICE=enp7s0
ONBOOT=yes
IPADDR=192.1.1.15
PREFIX=24
GATEWAY=192.1.1.1
DNS1=157.161.1.2
DNS2=157.161.255.133
DOMAIN=opag.ch

[bsa.opag.ch:/root] cat /etc/sysconfig/network-scripts/ifcfg-enp7s0
HWADDR=50:E5:49:BE:F4:D8
TYPE=Ethernet
PROXY_METHOD=none
BROWSER_ONLY=no
BOOTPROTO=dhcp
DEFROUTE=yes
IPV4_FAILURE_FATAL=yes
IPV6INIT=no
IPV6_AUTOCONF=yes
IPV6_DEFROUTE=yes
IPV6_FAILURE_FATAL=no
IPV6_ADDR_GEN_MODE=stable-privacy
NAME=enp7s0
UUID=61ce505f-620c-3972-b204-0869c0b1153f
ONBOOT=yes
AUTOCONNECT_PRIORITY=-999
IPADDR=192.168.1.40
PREFIX=24
GATEWAY=192.168.1.1
DNS1=192.168.1.1
DOMAIN=opag.ch
ETHTOOL_OPTS="wol g"
ZONE=public




---
Note: montesa WoL is working, bsa WoL not working
fpaquet

fpaquet

2019-10-06 07:53

reporter   ~0035344

as mentioned in this article https://www.lisenet.com/2016/set-up-wake-on-lan-wol-on-centos-7/
Changing ifcfg-enp7s0 to ETHTOOL_OPTS="-s enp7s0 wol g" doesn't help.
WoL still not working
fpaquet

fpaquet

2019-10-06 08:01

reporter   ~0035345

The following steps fixes WoL for me on host bsa:

1. remove ETHTOOL_OPTS in /etc/sysconfig/network-scripts/ifcfg-enp7s0
2. enable "Magic" via "Network Connections" gui
    (nm-connection-editor)

See attached screenshot

WoL01.png (49,276 bytes)
WoL01.png (49,276 bytes)
fpaquet

fpaquet

2019-10-11 16:19

reporter   ~0035446

withdrawing my last statement - three of our workstations still do not WoL
fpaquet

fpaquet

2019-10-12 05:45

reporter   ~0035449

Here's a CentOS forum entry which claims to be solved the issue:
https://www.centos.org/forums/viewtopic.php?f=47&t=71861
fpaquet

fpaquet

2019-10-12 05:59

reporter   ~0035450

Now this is weird:
After re-checking our workstations, i noticed that the one station where WoL is working has "Wake-on: d" (see output of ethtool montesa above).

I was curious trying it, and in fact WoL on bsa is WORKING now. With the Magic OFF!

WoL02.png (52,136 bytes)
WoL02.png (52,136 bytes)
fpaquet

fpaquet

2019-10-12 06:18

reporter   ~0035451

Now i'm not sure about what ethtool reports and how to set wake-on-lan via nmcli correctly.

man ethtool says:
                  p Wake on PHY activity
                  u Wake on unicast messages
                  m Wake on multicast messages
                  b Wake on broadcast messages
                  a Wake on ARP
                  g Wake on MagicPacket™
                  s Enable SecureOn™ password for MagicPacket™
                  d Disable (wake on nothing). This option
                      clears all previous options.

man nmcli -> man nm-settings (802-3 section) has more options than ethtool reports:
  wake-on-lan, uint32, 1
  The NMSettingWiredWakeOnLan options to enable. Not all devices support all options.
  May be any combination of
  NM_SETTING_WIRED_WAKE_ON_LAN_PHY (0x2),
  NM_SETTING_WIRED_WAKE_ON_LAN_UNICAST (0x4),
  NM_SETTING_WIRED_WAKE_ON_LAN_MULTICAST (0x8),
  NM_SETTING_WIRED_WAKE_ON_LAN_BROADCAST(0x10),
  NM_SETTING_WIRED_WAKE_ON_LAN_ARP (0x20),
  NM_SETTING_WIRED_WAKE_ON_LAN_MAGIC (0x40)
  or the special values
  NM_SETTING_WIRED_WAKE_ON_LAN_DEFAULT (0x1) (to use global settings) and
  NM_SETTING_WIRED_WAKE_ON_LAN_IGNORE (0x8000) (to disable management of Wake-on-LAN inNetworkManager).

Note that nmcli offers the option DEFAULT 0x1 besides IGNORE 0x8000, while ethtool only knows "Disable"
jimj

jimj

2019-10-13 20:31

reporter   ~0035456

As described in the forum post referenced above I was able to fix this for my desktop by running this command:
nmcli c modify "enp3s0" 802-3-ethernet.auto-negotiate yes

I assume with the new kernel the NIC's speed/duplex no longer matches the switch port's speed/duplex after the PC is suspended. My guess is that setting "802-3-ethernet.auto-negotiate yes" causes the NIC to keep the correct/matching speed/duplex auto negotiate setting after the computer is suspended.
jimj

jimj

2019-10-13 20:32

reporter   ~0035457

Forgot to share my hardware:
$ lspci|grep Ethernet
03:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)
04:00.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL8111/8168/8411 PCI Express Gigabit Ethernet Controller (rev 03)

Issue History

Date Modified Username Field Change
2019-09-28 18:09 krbvroc1 New Issue
2019-09-28 19:51 krbvroc1 Note Added: 0035263
2019-09-28 21:38 toracat Relationship added related to 0016413
2019-10-06 07:37 fpaquet Note Added: 0035341
2019-10-06 07:42 fpaquet Note Added: 0035342
2019-10-06 07:49 fpaquet Note Added: 0035343
2019-10-06 07:53 fpaquet Note Added: 0035344
2019-10-06 08:01 fpaquet File Added: WoL01.png
2019-10-06 08:01 fpaquet Note Added: 0035345
2019-10-11 16:19 fpaquet Note Added: 0035446
2019-10-12 05:45 fpaquet Note Added: 0035449
2019-10-12 05:59 fpaquet File Added: WoL02.png
2019-10-12 05:59 fpaquet Note Added: 0035450
2019-10-12 06:18 fpaquet Note Added: 0035451
2019-10-13 20:31 jimj Note Added: 0035456
2019-10-13 20:32 jimj Note Added: 0035457