public inbox for linux-bluetooth@vger.kernel.org
 help / color / mirror / Atom feed
From: Johannes Berg <johannes@sipsolutions.net>
To: "Íñigo Huguet" <ihuguet@redhat.com>
Cc: gregory.greenman@intel.com, golan.ben.ami@intel.com,
	jonathan.sade@intel.com,
	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 12:06:34 +0200	[thread overview]
Message-ID: <5c47143aea07c34dbe95fdb2cab677f2a7a753fb.camel@sipsolutions.net> (raw)
In-Reply-To: <CACT4oufKgUG5n6Ocgi6r-Z=+Nt9vNVK1e5dJDccogmd8h7xM8Q@mail.gmail.com>

On Wed, 2022-10-05 at 11:50 +0200, Íñigo Huguet wrote:
> On Wed, Oct 5, 2022 at 11:35 AM Johannes Berg <johannes@sipsolutions.net> wrote:
> > 
> > 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 don't think so, we've reproduced it with iwlwifi-QuZ-a0-jf-b0-71.ucode
> 

Indeed, my git-fu was bad. Looks like 74 only fixes it (or will, since
it hasn't been released, apparently).

We could do some awful workaround like this I guess:

diff --git a/drivers/net/wireless/intel/iwlwifi/fw/acpi.c b/drivers/net/wireless/intel/iwlwifi/fw/acpi.c
index 009a4074d062..0c0a28d748f2 100644
--- a/drivers/net/wireless/intel/iwlwifi/fw/acpi.c
+++ b/drivers/net/wireless/intel/iwlwifi/fw/acpi.c
@@ -1119,6 +1119,11 @@ int iwl_read_ppag_table(struct iwl_fw_runtime *fwrt, union iwl_ppag_table_cmd *c
         int i, j, num_sub_bands;
         s8 *gain;
 
+	/* many firmware images for JF lie about this */
+	if (CSR_HW_RFID_TYPE(fwrt->trans->hw_rf_id) ==
+	    CSR_HW_RFID_TYPE(CSR_HW_RF_ID_TYPE_JF))
+		return -EOPNOTSUPP;
+
         if (!fw_has_capa(&fwrt->fw->ucode_capa, IWL_UCODE_TLV_CAPA_SET_PPAG)) {
                 IWL_DEBUG_RADIO(fwrt,
                                 "PPAG capability not supported by FW, command not sent.\n");


johannes

  reply	other threads:[~2022-10-05 10:06 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
2022-10-05  9:50   ` Íñigo Huguet
2022-10-05 10:06     ` Johannes Berg [this message]
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=5c47143aea07c34dbe95fdb2cab677f2a7a753fb.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