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;
Message-ID: <100b06a944de88a4b80119c5a2024e0e59cf5243.camel@sipsolutions.net>
Subject: Re: iwlwifi: AC9560 firmware crash with iwlwifi-QuZ-a0-jf-b0
 versions above 55
From:   Johannes Berg <johannes@sipsolutions.net>
To:     =?ISO-8859-1?Q?=CD=F1igo?= Huguet <ihuguet@redhat.com>,
        gregory.greenman@intel.com, golan.ben.ami@intel.com,
        jonathan.sade@intel.com
Cc:     Linux List Kernel Mailing <linux-wireless@vger.kernel.org>,
        linux-bluetooth@vger.kernel.org,
        Jose Ignacio Tornos Martinez <jtornosm@redhat.com>,
        Laura Trivelloni <ltrivell@redhat.com>
Date:   Wed, 05 Oct 2022 11:35:16 +0200
In-Reply-To: <CACT4oucG2z14214jWGJj9XZ5cYMnQpw9CACHvPZ09cbL7m9z_g@mail.gmail.com>
References: <CACT4oucG2z14214jWGJj9XZ5cYMnQpw9CACHvPZ09cbL7m9z_g@mail.gmail.com>
Content-Type: text/plain; charset="UTF-8"
Content-Transfer-Encoding: quoted-printable
User-Agent: Evolution 3.44.4 (3.44.4-2.fc36) 
MIME-Version: 1.0
Precedence: bulk

On Fri, 2022-09-09 at 12:41 +0200, =C3=8D=C3=B1igo Huguet wrote:
> With an AC9560 installed on a system with Quasar (11th gen processor,
> in my case) we're getting a firmware crash as soon as you try to do
> something with the card. The problem doesn't happen with the card
> installed in older platforms (8th / 9th gen), and it neither happens
> with firmware iwlwifi-QuZ-a0-jf-b0-55 version, but yes with any other
> newer version.
>=20
> I've tried different versions of kernel and firmware, including the
> latest kernel and linux-firmware available today, and all of them fail
> unless I remove all fw files above version 55.
>=20

I believe this is a duplicate of

https://bugzilla.kernel.org/show_bug.cgi?id=3D214343

which was supposed to be fixed in firmware, but evidently that fix was
never backported to older images.

Internally, FW commit d8887278 fixed this, so FW version 69 should be
OK?

I'm not sure we can easily workaround it in the driver? Maybe we can
detect the RF, but that's kind of awkward.

johannes