From: Thorsten Leemhuis <regressions@leemhuis.info>
To: Jianmin Lv <lvjianmin@loongson.cn>,
"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Huacai Chen <chenhuacai@loongson.cn>,
Bob Moore <robert.moore@intel.com>,
acpica-devel@lists.linuxfoundation.org,
ACPI Devel Maling List <linux-acpi@vger.kernel.org>,
Huacai Chen <chenhuacai@kernel.org>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2
Date: Fri, 14 Apr 2023 14:48:31 +0200 [thread overview]
Message-ID: <13aea525-108a-e018-987d-2447ff1d42df@leemhuis.info> (raw)
In-Reply-To: <53e8b4db-e8dd-4dfa-f873-7dcbeac09149@leemhuis.info>
On 19.03.23 08:20, Linux regression tracking (Thorsten Leemhuis) wrote:
> On 22.02.23 08:57, Thorsten Leemhuis wrote:
>>
>> I noticed a regression report in bugzilla.kernel.org. As many (most?)
>> kernel developer don't keep an eye on it, I decided to forward it by
>> mail. Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217069 :
>
> An issue that looked like a network bug was now bisected and it turns
> out it's cause by 5c62d5aab875 ("ACPICA: Events: Support fixed PCIe wake
> event") which Huacai Chen provided. Could you take a look at the ticket
> linked above?
Jianmin did get close to a proper fix a while ago
(https://bugzilla.kernel.org/show_bug.cgi?id=217069#c46 ), but it
appears there wasn't any progress to fix this during the last week. Or
did I miss it?
This is kinda unsatisfying, as the culprit is now known for nearly four
weeks; especially as this is a issue that is present in 6.2 since it was
released and would have been possible to fix there and in mainline with
a simple revert. We even got close to one two weeks ago already
(https://bugzilla.kernel.org/show_bug.cgi?id=217069#c49 ).
#sigh
I'd say we should revert this. Rafael, what's your opinion here?
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
--
Everything you wanna know about Linux kernel regression tracking:
https://linux-regtracking.leemhuis.info/about/#tldr
If I did something stupid, please tell me, as explained on that page.
#regzbot poke
next prev parent reply other threads:[~2023-04-14 12:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-22 7:57 [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2 Thorsten Leemhuis
2023-03-16 13:21 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-19 7:14 ` Thorsten Leemhuis
2023-03-19 7:20 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-24 9:46 ` Thorsten Leemhuis
2023-03-24 9:50 ` Huacai Chen
2023-03-24 10:09 ` Jianmin Lv
2023-03-25 13:31 ` Linux regression tracking (Thorsten Leemhuis)
2023-03-27 7:56 ` Jianmin Lv
2023-04-14 12:48 ` Thorsten Leemhuis [this message]
2023-04-16 12:35 ` Jianmin Lv
2023-04-16 12:52 ` Linux regression tracking (Thorsten Leemhuis)
2023-04-17 0:54 ` Jianmin Lv
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=13aea525-108a-e018-987d-2447ff1d42df@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=acpica-devel@lists.linuxfoundation.org \
--cc=chenhuacai@kernel.org \
--cc=chenhuacai@loongson.cn \
--cc=linux-acpi@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=lvjianmin@loongson.cn \
--cc=rafael.j.wysocki@intel.com \
--cc=regressions@lists.linux.dev \
--cc=robert.moore@intel.com \
/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;
as well as URLs for NNTP newsgroup(s).