From: "Linux regression tracking (Thorsten Leemhuis)" <regressions@leemhuis.info>
To: Heiner Kallweit <hkallweit1@gmail.com>
Cc: linux-wireless@vger.kernel.org,
LKML <linux-kernel@vger.kernel.org>,
Linux kernel regressions list <regressions@lists.linux.dev>,
Realtek linux nic maintainers <nic_swsd@realtek.com>,
"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>
Subject: [regression] r8169 ASPM changes broke iwlwifi driver for Intel 3165
Date: Wed, 12 Jul 2023 13:24:19 +0200 [thread overview]
Message-ID: <b30258b7-ee09-e502-1a08-809ec0bfcf12@leemhuis.info> (raw)
In-Reply-To: <6f8715af-95c2-8333-2b32-206a143ebb52@leemhuis.info>
[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
parent reply other threads:[~2023-07-12 11:24 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <6f8715af-95c2-8333-2b32-206a143ebb52@leemhuis.info>]
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=b30258b7-ee09-e502-1a08-809ec0bfcf12@leemhuis.info \
--to=regressions@leemhuis.info \
--cc=davem@davemloft.net \
--cc=edumazet@google.com \
--cc=hkallweit1@gmail.com \
--cc=kuba@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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