Message-ID: <b30258b7-ee09-e502-1a08-809ec0bfcf12@leemhuis.info>
Date:   Wed, 12 Jul 2023 13:24:19 +0200
From:   "Linux regression tracking (Thorsten Leemhuis)" 
        <regressions@...mhuis.info>
To:     Heiner Kallweit <hkallweit1@...il.com>
Cc:     linux-wireless@...r.kernel.org,
        LKML <linux-kernel@...r.kernel.org>,
        Linux kernel regressions list <regressions@...ts.linux.dev>,
        Realtek linux nic maintainers <nic_swsd@...ltek.com>,
        "David S. Miller" <davem@...emloft.net>,
        Eric Dumazet <edumazet@...gle.com>,
        Jakub Kicinski <kuba@...nel.org>,
        Paolo Abeni <pabeni@...hat.com>,
        netdev <netdev@...r.kernel.org>
Subject: [regression] r8169 ASPM changes broke iwlwifi driver for Intel 3165

[adding maintainers for r8169 to the list of recipients while dropping
the iwlwifi folks (the latter are already aware about the bad bisection)]

On 10.07.23 10:32, Linux regression tracking (Thorsten Leemhuis) wrote:
> Hi, Thorsten here, the Linux kernel's regression tracker.
> 
> I noticed a regression report in bugzilla.kernel.org. As many (most?)
> kernel developers don't keep an eye on it, I decided to forward it by mail.
> 
> Aloka Dixit, apparently it's cause by a change of yours: bd54f3c2907
> ("wifi: mac80211: generate EMA beacons in AP mode") [v6.4-rc1]

Heiner, this turned out to be a bad bisection. The reporter ran another
one and this time even verified the results by reverting the fix ontop
of v6.4. Turns out the issue is caused by 5fc3f6c90cc ("r8169:
consolidate disabling ASPM before EPHY access") you contributed.

Blacklisting r8169 fixes the issue, too. For details see:
https://bugzilla.kernel.org/show_bug.cgi?id=217635

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.

> Note, you have to use bugzilla to reach the reporter, as I sadly[1] can
> not CCed them in mails like this.
> 
> Quoting from https://bugzilla.kernel.org/show_bug.cgi?id=217635 :
> 
>> Distro: Arch Linux
>> Kernel version: 6.4.1.arch1-1
>> Happens on mainline kernel? : YES (linux-mainline 6.4-1)
>> Note: linux-mainline 6.4.1 is not available at time of this writing
>>
>> Arch linux bug:
>> https://bugs.archlinux.org/task/78984
>>
>> Summary:
>> No network access even after connecting to wifi. Websites don't load, ping doesn't work.
>> This didn't happen on kernel 6.3.x (specifically 6.3.9, the last 6.3 kernel provided by Arch).
>>
>> Bug happens on both Arch-provided kernel and mainline kernel
>>
>> Steps to reproduce:
>> 1) On fresh boot, connect to a wifi network
>>    a) Make sure wifi password is not saved beforehand
>> 2) Ping a url with terminal, or open a website with browser
>> 3) Ping fails to work / website doesn't load
> 
> See the ticket for more details and the bisection result that came later.
> 
> Aditya Kumar Singh, FWIW, I hope you don't mind that I CCed you, but you
> already contributed a fix for the culprit, so it seemed the right thing
> to do in this case.
> 
> [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
> form.]
> 
> 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: bd54f3c29077f2
> https://bugzilla.kernel.org/show_bug.cgi?id=217635
> #regzbot title: net: wireless: iwlwifi driver broken on Intel 3165
> network card
> #regzbot ignore-activity

#regzbot introduced: 5fc3f6c90cca19e

Powered by blists - more mailing lists