Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 686286 - >= sys-kernel/gentoo-sources-4.19.37 - r8169 broken wake on lan
Summary: >= sys-kernel/gentoo-sources-4.19.37 - r8169 broken wake on lan
Status: RESOLVED WONTFIX
Alias: None
Product: Gentoo Linux
Classification: Unclassified
Component: Current packages (show other bugs)
Hardware: All Linux
: Normal normal
Assignee: Gentoo Kernel Bug Wranglers and Kernel Maintainers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2019-05-19 08:01 UTC by PV
Modified: 2019-05-19 09:22 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description PV 2019-05-19 08:01:47 UTC
Hello, looks like behavior of wol has been dramaticaly changed in 4.19 kernel: 

I'am on amd64 - stable, my 'lazy' observations, from emerge.log:
Tue Dec 11 22:34:52 2018 >>> sys-kernel/gentoo-sources-4.14.83 - wol working
Tue Mar 12 00:20:51 2019 >>> sys-kernel/gentoo-sources-4.19.27-r1 - wol stopped working
 
Between Dec 11 and Mar 12, settings, related to wol hasn't been changed.

Steps to reproduce on current stable (4.19.27-r1):
0. Be sure wol is enabled in your bios

1. Check wol is enabled:

# ethtool eth0 | grep Wake
        Supports Wake-on: pumbg
        Wake-on: g

2. Check the interface ifdown settings:

# cat /etc/conf.d/net | grep 'ifdown'
ifdown_eth0="no"

3. Send machine to suspend:

# echo "mem" > /sys/power/state

4. Send magic packet to suspended machine

Result: Machine didn't woke up. But it able to woke from hitting keyboard button

Expected result: Machine woken up.



If, we update wol settings just before suspending:

(check current wol settings)
# ethtool eth0 | grep Wake
        Supports Wake-on: pumbg
        Wake-on: g

(update wol state)
# ethtool -s eth0 wol g

(check again current wol setting - note, nothing changed! still 'g')
# ethtool eth0 | grep Wake
        Supports Wake-on: pumbg
        Wake-on: g

(send machine to suspend)
# echo "mem" > /sys/power/state

The wol from suspend working flaswless.

From this observation, I've added a workaround to '/etc/conf.d/net':

postup() {
# WOL workaround
        ethtool -s eth0 wol g
}


Useful links:
https://git.kernel.org/pub/scm/linux/kernel/git/torvalds/linux.git/commit/drivers/net/ethernet/realtek/r8169.c?id=fa6821cbf1d9724284ef0906c9a01a5fbf13a35c
https://www.spinics.net/lists/netdev/msg547133.html
-> https://www.spinics.net/lists/netdev/msg547582.html
-> https://www.spinics.net/lists/netdev/msg548501.html
https://askubuntu.com/questions/1051822/wake-on-lan-quit-working-with-latest-kernel-bionic
https://serverfault.com/questions/958323/broken-wol-with-vanilla-kernel-on-debian
and probably this https://bugzilla.redhat.com/show_bug.cgi?id=1657451
Comment 1 Jonas Stein gentoo-dev 2019-05-19 09:22:37 UTC
I will close this bug here, because I do not see a relation to the gentoo ebuild or the way Gentoo handles this special software package. Other distributions show the same effect.
The Kernel simply changed the defaults.
Please provide more information, if I am wrong.