On 13.01.2019 17:01, Marc Haber wrote: > On Sat, Jan 12, 2019 at 09:28:48PM +0100, Heiner Kallweit wrote: >> On 12.01.2019 21:08, Marc Haber wrote: >>> I am writing to all people who have commits in r8169.c between the v4.18 >>> and v4.19 tags in the Linux kernel. Please ignore as appropriate. If >>> you'd prefer that to be on a mailing list, please indicate on which list >>> you want to have that, and I'll resend. >>> >> It should be cc'ed to the netdev mailing list, as listed in MAINTAINERS. > > I have bounced the original message there. Sorry for missing that, I was > not aware that the MAINTAINERS file goes down on a single driver level. > The netdev mailing list is used for everything in the network subsystem.
>>> My desktop copmuter has the following network interface: >>> >>> >> Unfortunately there's different chip versions with the same description. >> Please provide the result of "dmesg | grep XID". > > [1/5004]mh@fan:~ $ dmesg | grep XID > [ 2.671004] r8169 0000:06:00.0 eth0: RTL8168evl/8111evl, > 54:04:a6:82:21:00, XID 2c900800, IRQ 29 > >>> I regularly buĂld a VPN tunnel to my local network from 'on the road' >>> and use WoL to wake up the desktop box when I need it. >>> >>> Since kernel 4.19, that does not work any more, the desktop remains >>> suspended when I send it a magic packet. This still applies to 4.20.1, >>> and it still works with any 4.18 kernel. >>> >> WoL works perfectly fine here with r8169 from runtime-suspend and >> from S3. How do you enable WoL? And which WoL method do you use >> (magic packet or ..) ? > > I do enable WOL via systemd-networkd: > [7/5009]mh@fan:~ $ cat /etc/systemd/network/10-lanc0.link > [Match] > MACAddress=54:04:a6:82:21:00 > > [Link] > Name=lanc0 > WakeOnLan=magic > > and I wake up the box by calling > > sudo etherwake -i int182 54:04:a6:82:21:00 > > on the router. int182 is the interface name of the correct interface, > this is proven correct by the fact that the box wakes up just fine with > older version of the driver. > >> Please provide a register dump (ethtool -d <if>). > > The register dump is here (obtained with 4.20.1 with the r8169.c from > 4.18): > [5/5008]mh@fan:~ $ sudo ethtool -d lanc0 > RealTek RTL8168evl/8111evl registers: > -------------------------------------------------------- > [..] > > Greetings > Marc > I removed most people from To/Cc because I think for now they aren't needed and our conversation would just bother them. I assume you want to wake the system from S5 (poweroff). Does is wake from S3 (suspend-to-RAM) ? You can trigger this with "systemctl suspend". Any difference if you enable WoL manually via ethtool "ethtool -s <if> wol g" ? And a basic question: Once you have powered off your system, is network LED on PC and router on? Heiner