Received-SPF: pass (google.com: domain of linux-wireless-owner@vger.kernel.org designates 2620:137:e000::1:20 as permitted sender) client-ip=2620:137:e000::1:20;
Date:   Sun, 7 May 2023 09:34:06 +0700
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
Message-ID: <ZFcOHkwI8erdlKdC@debian.me>
References: <CAPrf5XXD8COh6DK9s41uvgJ5V57nenUQVeb1f=cFVqaWDN++dA@mail.gmail.com>
MIME-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha512;
        protocol="application/pgp-signature"; boundary="F/57nm9pIGEA54YJ"
Content-Disposition: inline
In-Reply-To: <CAPrf5XXD8COh6DK9s41uvgJ5V57nenUQVeb1f=cFVqaWDN++dA@mail.gmail.com>
Precedence: bulk


--F/57nm9pIGEA54YJ
Content-Type: text/plain; charset=utf-8
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

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.
>=20
> 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.

--=20
An old man doll... just what I always wanted! - Clara

--F/57nm9pIGEA54YJ
Content-Type: application/pgp-signature; name="signature.asc"

-----BEGIN PGP SIGNATURE-----

iHUEABYKAB0WIQSSYQ6Cy7oyFNCHrUH2uYlJVVFOowUCZFcOGAAKCRD2uYlJVVFO
ox7CAQDz7X4BIZetFYf5xDlesSK4n/xhGALqkQA/jbiy76HqXwD/VdhazGC5IYYE
0QcUnhKVoWyq18YVsBCPK4gMmS1s5wQ=
=7XJc
-----END PGP SIGNATURE-----

--F/57nm9pIGEA54YJ--