summaryrefslogtreecommitdiffstats
path: root/lib/debug_locks.c
diff options
context:
space:
mode:
authorHeiner Kallweit <hkallweit1@gmail.com>2018-02-22 21:22:40 +0100
committerDavid S. Miller <davem@davemloft.net>2018-02-23 12:28:21 -0500
commit7edf6d314cd061e1d0a1b7bc0b511d64322c3f72 (patch)
tree9d8856d34a996e0dd066cc707e8c698b8ae4125b /lib/debug_locks.c
parent46182452cf5abe95782e100f0719b7497641d263 (diff)
downloadlinux-7edf6d314cd061e1d0a1b7bc0b511d64322c3f72.tar.bz2
r8169: disable WOL per default
Currently, if BIOS enables WOL in the chip, settings are inconsistent because the device isn't marked as wakeup-enabled (if not done explicitly via userspace tools). This causes issues with suspend/ resume because mdio_bus_phy_may_suspend() checks whether device is wakeup-enabled. In detail MDIO bus access in phy_suspend() can fail because the MDIO bus is disabled. In the history of the driver we find two competing approaches: 8f9d5138035d "r8169: remember WOL preferences on driver load" prefers to preserve what the BIOS may have set, whilst bde135a672bf "r8169: only enable PCI wakeups when WOL is active" disabled PCI wakeup per default to work around a bug on one platform. Seems like nobody complained after the latter patch about non-working WOL, what makes me think that nobody uses WOL w/o configuring it explicitly. My opinion: Vast majority of users doesn't use WOL even if the BIOS enables it in the chip. And having WOL being active keeps the PHY(s) from powering down if being idle. If somebody needs WOL, he can enable it during boot, e.g. by configuring systemd.link/WakeOnLan. Therefore, to make WOL consistent again, disable it per default. Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'lib/debug_locks.c')
0 files changed, 0 insertions, 0 deletions