From: "Linux regression tracking (Thorsten Leemhuis)" <email@example.com>
To: Jianmin Lv <firstname.lastname@example.org>,
Linux regressions mailing list <email@example.com>,
"Rafael J. Wysocki" <firstname.lastname@example.org>
Cc: LKML <email@example.com>,
Huacai Chen <firstname.lastname@example.org>,
Bob Moore <email@example.com>,
ACPI Devel Maling List <firstname.lastname@example.org>,
Huacai Chen <email@example.com>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2
Date: Sun, 16 Apr 2023 14:52:59 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
On 16.04.23 14:35, Jianmin Lv wrote:
> From the feedbacks, the WOL issue has been fixed, and I have submitted a
> fixed patch to ACPICA, which has been reviewing in last week (Rafael
> also looked into the fixed patch).
Great, many thx. I looked for something like that, but failed to find it.
FWIW, a link to the patch submission would have been nice. I tried to
find it just now, but maybe it's not on lore.kernel.org or I did
something stupid. And
https://lists.linuxfoundation.org/pipermail/acpica-devel/ seems to lack
behind or might not be the list you submitted the patch to. Whatever.
> There are two kinds of issues in the bug, one is WOL failed in kexec
> reboot, another is WOL failed in cold reboot. The former one still exist
> after reverted patch(5c62d5aab8752e5ee7bfbe75ed6060db1c787f98),
> so this issue is not caused by the reverted patch. The second is caused
> by the reverted patch, and has been fixed with my provided patch.
> Please see:
I'll post a quick update there.
Ciao, Thorsten (wearing his 'the Linux kernel's regression tracker' hat)
Everything you wanna know about Linux kernel regression tracking:
If I did something stupid, please tell me, as explained on that page.
> On 2023/4/14 下午8:48, Thorsten Leemhuis wrote:
>> 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 ).
>> 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:
>> If I did something stupid, please tell me, as explained on that page.
>> #regzbot poke
next prev parent reply other threads:[~2023-04-16 12:53 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
2023-04-16 12:35 ` Jianmin Lv
2023-04-16 12:52 ` Linux regression tracking (Thorsten Leemhuis) [this message]
2023-04-17 0:54 ` Jianmin Lv
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:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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).