archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <>
To: Heiner Kallweit <>,
Cc: "David S. Miller" <>,
	Eric Dumazet <>,
	Jakub Kicinski <>, Paolo Abeni <>,
	netdev <>,
	LKML <>,
	Linux kernel regressions list <>,
	Ivan Ivanich <>
Subject: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2
Date: Wed, 22 Feb 2023 08:57:56 +0100	[thread overview]
Message-ID: <> (raw)

Hi, this is your Linux kernel regression tracker.

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 :

> Ivan Ivanich 2023-02-22 00:51:52 UTC
> After upgrade to 6.2 having issues with wake on lan on 2 systems: -
> first is an old lenovo laptop from 2012(Ivy Bridge) with realtek
> network adapter - second is a PC(Haswell refresh) with PCIE realtek
> network adapter
> Both uses r8169 driver for network.
> On laptop it's not possible to wake on lan after poweroff On PC it's
> not possible to wake on lan up after hibernate but works after
> poweroff
> In both cases downgrade to 6.1.x kernel fixes the issue.

See the ticket for more details.

@Ivan: maybe someone that sees this mail might have an idea what's
wrong. But if not, you likely need to run a bisection to find what's
causing this.

[TLDR for the rest of this mail: I'm adding this report to the list of
tracked Linux kernel regressions; the text you find below is based on a
few templates paragraphs you might have encountered already in similar

BTW, let me use this mail to also add the report to the list of tracked
regressions to ensure it's doesn't fall through the cracks:

#regzbot introduced: v6.1..v6.2
#regzbot title: net/r8169: Wake/power on Lan is broken on two machines
#regzbot ignore-activity

This isn't a regression? This issue or a fix for it are already
discussed somewhere else? It was fixed already? You want to clarify when
the regression started to happen? Or point out I got the title or
something else totally wrong? Then just reply and tell me -- ideally
while also telling regzbot about it, as explained by the page listed in
the footer of this mail.

Developers: When fixing the issue, remember to add 'Link:' tags pointing
to the report (e.g. the buzgzilla ticket and maybe this mail as well, if
this thread sees some discussion). See page linked in footer for details.

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.

             reply	other threads:[~2023-02-22  7:58 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-22  7:57 Thorsten Leemhuis [this message]
2023-03-16 13:21 ` [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2 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)
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).