regressions.lists.linux.dev archive mirror
 help / color / mirror / Atom feed
From: Huacai Chen <chenhuacai@kernel.org>
To: Linux regressions mailing list <regressions@lists.linux.dev>
Cc: LKML <linux-kernel@vger.kernel.org>,
	Jianmin Lv <lvjianmin@loongson.cn>,
	 Huacai Chen <chenhuacai@loongson.cn>,
	Bob Moore <robert.moore@intel.com>,
	 "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	acpica-devel@lists.linuxfoundation.org,
	 ACPI Devel Maling List <linux-acpi@vger.kernel.org>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2
Date: Fri, 24 Mar 2023 17:50:21 +0800	[thread overview]
Message-ID: <CAAhV-H5j29CnCN+F8Oz0qh1UCqp+CmL=aQXCSjqgX8CZ5sXTtg@mail.gmail.com> (raw)
In-Reply-To: <3089214d-292b-885d-9bc1-c81d0101d5f0@leemhuis.info>

Hi, Thorsten,

I'm sorry I ignored this email, and Jianmin, could you please
investigate this problem? Thank you.

Huacai

On Fri, Mar 24, 2023 at 5:46 PM Thorsten Leemhuis
<regressions@leemhuis.info> wrote:
>
> On 19.03.23 08:20, Linux regression tracking (Thorsten Leemhuis) wrote:
> > Hi, Thorsten here, the Linux kernel's regression tracker.
> >
> > 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?
>
> Huacai Chen, did you look into this? Would be good to have this
> regression fixed rather sooner than later, as it seems to annoy quite a
> few people.
>
> Should we maybe simply revert the problematic change for now and reapply
> it later once the root-issue was found and fixed?
>
> 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
>
> > FWIW, the whole story started like this:
> >
> >>> 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.
> >
> > Meanwhile a few others that ran into the same problem with NICs from
> > different vendors joined the ticket
> >
> > 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.

  reply	other threads:[~2023-03-24  9:50 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 [this message]
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='CAAhV-H5j29CnCN+F8Oz0qh1UCqp+CmL=aQXCSjqgX8CZ5sXTtg@mail.gmail.com' \
    --to=chenhuacai@kernel.org \
    --cc=acpica-devel@lists.linuxfoundation.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).