From: Stephen Hemminger <stephen@networkplumber.org>
To: netdev@vger.kernel.org
Subject: Fw: [Bug 217629] New: [regression] Wake-on-LAN broken in new kernel for E2400 Ethernet Controller with Qualcomm Atheros
Date: Mon, 3 Jul 2023 15:13:14 -0700 [thread overview]
Message-ID: <20230703151314.1b2a21a6@hermes.local> (raw)
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.
As this functionality is very important for my job I'm filing here a bug with
the hope things to return back to normal.
There is this bug from 2013 https://bugzilla.kernel.org/show_bug.cgi?id=61651
which looks like dead thread, that's why I decided to open a new one.
--
You may reply to this email to add a comment.
You are receiving this mail because:
You are the assignee for the bug.
next reply other threads:[~2023-07-03 22:13 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-03 22:13 Stephen Hemminger [this message]
2023-07-04 16:05 ` Fw: [Bug 217629] New: [regression] Wake-on-LAN broken in new kernel for E2400 Ethernet Controller with Qualcomm Atheros Andrew Lunn
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=20230703151314.1b2a21a6@hermes.local \
--to=stephen@networkplumber.org \
--cc=netdev@vger.kernel.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