[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <49a3cf01-8f1d-bf67-cfcb-c5a0537a68c9@web.de>
Date: Sat, 29 Dec 2018 14:27:37 +0100
From: Norbert Jurkeit <norbert.jurkeit@....de>
To: Heiner Kallweit <hkallweit1@...il.com>
Cc: Florian Fainelli <f.fainelli@...il.com>,
Andrew Lunn <andrew@...n.ch>,
David Miller <davem@...emloft.net>,
Greg Kroah-Hartman <gregkh@...uxfoundation.org>,
"Rafael J. Wysocki" <rafael@...nel.org>,
"netdev@...r.kernel.org" <netdev@...r.kernel.org>,
Frank Crawford <frank@...wford.emu.id.au>
Subject: Re: [PATCH net] net: phy: replace preliminary fix for PHY driver
sometimes not binding to the device
Am 29.12.18 um 12:54 schrieb Heiner Kallweit:
>
> Good to know, I'll check. In this context, do you have Wake-on-LAN enabled?
> IOW, what does "ethtool <if>" state in line "Wake-on:" ?
"ethtool enp1s0" yields
Supports Wake-on: pumbg
Wake-on: d
Unfortunately I could not find any BIOS switch to enable WOL, but
although not persistent, "ethtool -s enp1s0 wol g" works for 1 reboot. I
issued that command in a session with kernel 4.18.18, rebooted and
noticed that between shutdown and new boot the LAN port status LED
turned off for 1s, then turn on again and network came up with a 4.19
kernel which normally fails in this szenario.
Powered by blists - more mailing lists