archive mirror
 help / color / mirror / Atom feed
From: Jianmin Lv <>
To: Linux regressions mailing list <>,
	"Rafael J. Wysocki" <>
Cc: LKML <>,
	Huacai Chen <>,
	Bob Moore <>,,
	ACPI Devel Maling List <>,
	Huacai Chen <>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2
Date: Sun, 16 Apr 2023 20:35:19 +0800	[thread overview]
Message-ID: <> (raw)
In-Reply-To: <>

 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).

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:


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 As many (most?)
>>> kernel developer don't keep an eye on it, I decided to forward it by
>>> mail. Quoting from :
>> 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
> ( ), 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
> ( ).
> #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:
> If I did something stupid, please tell me, as explained on that page.
> #regzbot poke

  reply	other threads:[~2023-04-16 12:35 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 [this message]
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:

* 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).