From: Bagas Sanjaya <bagasdotme@gmail.com>
To: evgeny nikiforov <evgeny.niki4off@gmail.com>, stable@vger.kernel.org
Cc: regressions@lists.linux.dev, linux-wireless@vger.kernel.org,
Gregory Greenman <gregory.greenman@intel.com>,
Golan Ben Ami <golan.ben.ami@intel.com>,
"Linux regression tracking (Thorsten Leemhuis)"
<regressions@leemhuis.info>
Subject: Re: [iwlwifi] 6.3 regression, AX201 crash on traffic activity with Pixel 7, bisected
Date: Sun, 7 May 2023 09:34:06 +0700 [thread overview]
Message-ID: <ZFcOHkwI8erdlKdC@debian.me> (raw)
In-Reply-To: <CAPrf5XXD8COh6DK9s41uvgJ5V57nenUQVeb1f=cFVqaWDN++dA@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1523 bytes --]
On Fri, May 05, 2023 at 02:29:14AM +0500, evgeny nikiforov wrote:
> Hello
> I have a laptop with Intel Wi-Fi 6 AX201.
> After updating from 6.2 to 6.3, I'm experiencing wifi crashes, wifi
> restart when traffic is flowing with Pixel 7 Pro (wifi 6E/802.11ax).
> Other older wifi devices probably not affected (tried Xiaomi pad with
> wifi 5/802.11ac).
> Tested with iperf3 in both directions, rsyncing Pixel photos to
> laptop, via router (wifi 5) or via Pixel wifi hotspot.
> The whole system freezes for seconds, no cursor movements possible at
> these moments (libinput "Touch jump detected and discarded" in logs
> indicating this).
> No problem with the 6.2 kernel.
>
> Bisecting leads to this commit of bumping FW API to 74
> 9ad1e7e5b0c488e4518edd698238a87ac6a73caa,
> looking strange to me, but reverting from 74 to 72 in 6.3 indeed
> successful with no crash.
Thanks for the report. However, it is better to also attach your .config
so that people here can know which config options are enabled (and your
hardware setup).
Interestingly, when I see the culprit commit, it looks trivial to me:
it just bumps maximum firmware API version, so theoretically drivers
using lower API version should continue to work. Maybe you got
one of your bisection steps wrong.
Anyway, I'm adding this to regzbot:
#regzbot ^introduced: 9ad1e7e5b0c488
#regzbot title: AX201 crash on traffic activity due to firmware API bump
Thanks.
--
An old man doll... just what I always wanted! - Clara
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 228 bytes --]
next prev parent reply other threads:[~2023-05-07 2:34 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-05-04 21:29 [iwlwifi] 6.3 regression, AX201 crash on traffic activity with Pixel 7, bisected evgeny nikiforov
2023-05-07 2:34 ` Bagas Sanjaya [this message]
2023-05-07 12:35 ` Greenman, Gregory
2023-05-17 16:16 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-05 11:11 ` Thorsten Leemhuis
2023-06-05 16:34 ` evgeny nikiforov
2023-06-05 18:05 ` Thorsten Leemhuis
2023-06-05 20:12 ` evgeny nikiforov
2023-06-14 15:48 ` Linux regression tracking (Thorsten Leemhuis)
2023-06-14 17:03 ` evgeny nikiforov
2023-06-21 13:57 ` Linux regression tracking #update (Thorsten Leemhuis)
2023-06-14 17:03 ` Ben Ami, Golan
2023-06-14 17:13 ` Greenman, Gregory
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=ZFcOHkwI8erdlKdC@debian.me \
--to=bagasdotme@gmail.com \
--cc=evgeny.niki4off@gmail.com \
--cc=golan.ben.ami@intel.com \
--cc=gregory.greenman@intel.com \
--cc=linux-wireless@vger.kernel.org \
--cc=regressions@leemhuis.info \
--cc=regressions@lists.linux.dev \
--cc=stable@vger.kernel.org \
/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