Bug#918042: WoL does not work on r8169 (regression since 4.18)
- To: Marc Haber <mh+debian-packages@zugschlus.de>, 918042@bugs.debian.org
- Subject: Bug#918042: WoL does not work on r8169 (regression since 4.18)
- From: Salvatore Bonaccorso <carnil@debian.org>
- Date: Sat, 29 May 2021 10:55:44 +0200
- Message-id: <YLIBkFFDw/EXMUPn@eldamar.lan>
- Reply-to: Salvatore Bonaccorso <carnil@debian.org>, 918042@bugs.debian.org
- In-reply-to: <154645216259.4671.11370863814358203509.reportbug@fan.zugschlus.de>
- References: <154645216259.4671.11370863814358203509.reportbug@fan.zugschlus.de> <154645216259.4671.11370863814358203509.reportbug@fan.zugschlus.de>
Control: tags -1 + moreinfo
On Wed, Jan 02, 2019 at 07:02:42PM +0100, Marc Haber wrote:
> Package: src:linux
> Version: 4.20-1~exp1
> Severity: normal
>
> Hi,
>
> I frequently send my desktop PC to sleep (suspend-to-ram) and wake it up
> from remote when I need to access it. To do so, I use a script on a
> banana pi which ends up calling etherwake 54:04:a6:82:21:00. This
> has worked reliably up to the last 4.18 release, including the Debian
> kernel linux-image-4.18.0-3-amd64 version 4.18.20-2.
>
> In 4.19, this ceased to work and has remained that way up to the kernel
> I am reporting this issue on, linux-image-4.20.0-trunk-amd64 version
> 4.20-1~exp1. I have observed this behavior also on my "own", locally
> built kernels of various 4.19 releases and also 4.20. Sorry, I didn't
> try any Debian 4.19 kernels, I decided to pursue this issue further
> after the regression was also present in 4.20.
>
> I am prepared to try kernel patches or follow other hints in debugging
> this. I acknowledge that this is most probably an upstream issue, but I
> don't have enough kernel foo to investigate this on an upstream level
> (and frankly, I am afraid of doing a bisect between 4.18 and 4.19).
>
> Any hints will be appreciated.
Marc, ist this still something you can reproduce with a recent kernel?
Regards,
Salvatore
Reply to: