linux-kernel - Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since 6.2

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <3089214d-292b-885d-9bc1-c81d0101d5f0@leemhuis.info>
Date:   Fri, 24 Mar 2023 10:46:38 +0100
From:   Thorsten Leemhuis <regressions@...mhuis.info>
To:     Huacai Chen <chenhuacai@...nel.org>
Cc:     LKML <linux-kernel@...r.kernel.org>,
        Linux kernel regressions list <regressions@...ts.linux.dev>,
        Jianmin Lv <lvjianmin@...ngson.cn>,
        Huacai Chen <chenhuacai@...ngson.cn>,
        Bob Moore <robert.moore@...el.com>,
        "Rafael J. Wysocki" <rafael.j.wysocki@...el.com>,
        acpica-devel@...ts.linuxfoundation.org,
        ACPI Devel Maling List <linux-acpi@...r.kernel.org>
Subject: Re: [regression] Bug 217069 - Wake on Lan is broken on r8169 since
 6.2

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.