From: Andrew Lunn <andrew@lunn.ch>
To: Stephen Hemminger <stephen@networkplumber.org>
Cc: netdev@vger.kernel.org
Subject: Re: Fw: [Bug 217629] New: [regression] Wake-on-LAN broken in new kernel for E2400 Ethernet Controller with Qualcomm Atheros
Date: Tue, 4 Jul 2023 18:05:51 +0200 [thread overview]
Message-ID: <8790dfc9-745b-4366-94e4-2618118f9dd9@lunn.ch> (raw)
In-Reply-To: <20230703151314.1b2a21a6@hermes.local>
On Mon, Jul 03, 2023 at 03:13:14PM -0700, Stephen Hemminger wrote:
>
>
> Begin forwarded message:
>
> Date: Mon, 03 Jul 2023 15:40:58 +0000
> From: bugzilla-daemon@kernel.org
> To: stephen@networkplumber.org
> Subject: [Bug 217629] New: [regression] Wake-on-LAN broken in new kernel for E2400 Ethernet Controller with Qualcomm Atheros
>
>
> https://bugzilla.kernel.org/show_bug.cgi?id=217629
>
> Bug ID: 217629
> Summary: [regression] Wake-on-LAN broken in new kernel for
> E2400 Ethernet Controller with Qualcomm Atheros
> Product: Networking
> Version: 2.5
> Hardware: All
> OS: Linux
> Status: NEW
> Severity: normal
> Priority: P3
> Component: Other
> Assignee: stephen@networkplumber.org
> Reporter: myrbourfake@gmail.com
> Regression: No
>
> I recently upgraded my pc to linux mint 21.1 (ubuntu 22.04) with kernel
> 5.15.0.75 and I realized that wake on lan functionality is not working any
> more. Up to Linux Mint 20.3 it was always working perfectly!
> I have a Killer E2400 Gigabit Ethernet Controller with Qualcomm Atheros
> AR816x/AR817x chipset.
This might be a vendor kernel issue.
drivers/net/ethernet/atheros/alx/ethtool.c ethtool_ops does not have a
set_wol. There is no indication it has been removed. So i guess the
vendor kernel might have additional patches adding WoL support.
Andrew
prev parent reply other threads:[~2023-07-04 16:05 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 22:13 Fw: [Bug 217629] New: [regression] Wake-on-LAN broken in new kernel for E2400 Ethernet Controller with Qualcomm Atheros Stephen Hemminger
2023-07-04 16:05 ` Andrew Lunn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=8790dfc9-745b-4366-94e4-2618118f9dd9@lunn.ch \
--to=andrew@lunn.ch \
--cc=netdev@vger.kernel.org \
--cc=stephen@networkplumber.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox