regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Thorsten Leemhuis <linux@leemhuis.info>
To: Heiner Kallweit <hkallweit1@gmail.com>, nic_swsd@realtek.com
Cc: "David S. Miller" <davem@davemloft.net>,
	Eric Dumazet <edumazet@google.com>,
	Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
	netdev <netdev@vger.kernel.org>,
	LKML <linux-kernel@vger.kernel.org>,
	Linux kernel regressions list <regressions@lists.linux.dev>,
	Ivan Ivanich <iivanich@gmail.com>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2
Date: Sun, 19 Mar 2023 08:14:44 +0100	[thread overview]
Message-ID: <8e3655bf-92dc-3685-5e96-b51ba8b8e61f@leemhuis.info> (raw)
In-Reply-To: <e6aaddb9-afec-e77d-be33-570f9f10a9c2@leemhuis.info>

On 22.02.23 08:57, Thorsten Leemhuis wrote:
> Hi, this is your Linux kernel regression tracker.
> 
> 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 :
> 
>> 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.

JFYI: turns out this is not a network bug, as the issue was bisected to
5c62d5aab875 ("ACPICA: Events: Support fixed PCIe wake event"). The
ticket linked above has the details.

#regzbot introduced: 5c62d5aab875
#regzbot ignore-activity

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.

  parent reply	other threads:[~2023-03-19  7:14 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 [this message]
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:
  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=8e3655bf-92dc-3685-5e96-b51ba8b8e61f@leemhuis.info \
    --to=linux@leemhuis.info \
    --cc=davem@davemloft.net \
    --cc=edumazet@google.com \
    --cc=hkallweit1@gmail.com \
    --cc=iivanich@gmail.com \
    --cc=kuba@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=netdev@vger.kernel.org \
    --cc=nic_swsd@realtek.com \
    --cc=pabeni@redhat.com \
    --cc=regressions@lists.linux.dev \
    /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).