From: Johannes Berg <johannes@sipsolutions.net>
To: "Íñigo 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>
Subject: Re: iwlwifi: AC9560 firmware crash with iwlwifi-QuZ-a0-jf-b0 versions above 55
Date: Wed, 05 Oct 2022 11:35:16 +0200 [thread overview]
Message-ID: <100b06a944de88a4b80119c5a2024e0e59cf5243.camel@sipsolutions.net> (raw)
In-Reply-To: <CACT4oucG2z14214jWGJj9XZ5cYMnQpw9CACHvPZ09cbL7m9z_g@mail.gmail.com>
On Fri, 2022-09-09 at 12:41 +0200, Íñigo 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.
>
> 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.
>
I believe this is a duplicate of
https://bugzilla.kernel.org/show_bug.cgi?id=214343
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
next prev parent reply other threads:[~2022-10-05 9:35 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-09 10:41 iwlwifi: AC9560 firmware crash with iwlwifi-QuZ-a0-jf-b0 versions above 55 Íñigo Huguet
2022-10-05 9:35 ` Johannes Berg [this message]
2022-10-05 9:50 ` Íñigo Huguet
2022-10-05 10:06 ` Johannes Berg
2022-10-05 10:09 ` Íñigo Huguet
2022-11-21 8:32 ` Íñigo Huguet
2022-11-21 10:42 ` Johannes Berg
2022-11-21 11:08 ` Íñigo Huguet
2022-11-21 16:35 ` Íñigo Huguet
2022-12-12 10:06 ` Íñigo Huguet
2022-12-12 10:18 ` 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=100b06a944de88a4b80119c5a2024e0e59cf5243.camel@sipsolutions.net \
--to=johannes@sipsolutions.net \
--cc=golan.ben.ami@intel.com \
--cc=gregory.greenman@intel.com \
--cc=ihuguet@redhat.com \
--cc=jonathan.sade@intel.com \
--cc=jtornosm@redhat.com \
--cc=linux-bluetooth@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=ltrivell@redhat.com \
/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