[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <d677ecf0-b106-03a0-2c66-d817ff39d20a@gmail.com>
Date: Mon, 28 Jan 2019 20:02:47 +0100
From: Heiner Kallweit <hkallweit1@...il.com>
To: Marc Haber <mh+netdev@...schlus.de>
Cc: "netdev@...r.kernel.org" <netdev@...r.kernel.org>
Subject: Re: WoL broken in r8169.c since kernel 4.19
On 28.01.2019 08:30, Marc Haber wrote:
> On Sun, Jan 27, 2019 at 10:09:51PM +0100, Heiner Kallweit wrote:
>> Yes. All you have to do after each "git bisect good/bad" is build again,
>> test, and make current build as good or bad.
>
> Will report back if I get any results. When I bisected last time, I
> ended up with a kernel that didn't even boot, but with 5 steps this is
> probably manageable. Will take most of the week though.
>
> Greetings
> Marc
>
One more test .. Can you provide the output of the following under 4.18 and under 4.19?
It may not apply cleanly, but you get the idea. The message is written when suspending.
diff --git a/drivers/net/ethernet/realtek/r8169.c b/drivers/net/ethernet/realtek/r8169.c
index 3e650bd9e..3a8b4b1b1 100644
--- a/drivers/net/ethernet/realtek/r8169.c
+++ b/drivers/net/ethernet/realtek/r8169.c
@@ -6927,6 +6927,8 @@ static int rtl8169_suspend(struct device *device)
rtl8169_net_suspend(dev);
clk_disable_unprepare(tp->clk);
+ pr_info("may wakeup? %d\n", device_may_wakeup(device));
+
return 0;
}
--
2.20.1
Powered by blists - more mailing lists