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: Mon, 21 Nov 2022 11:42:30 +0100	[thread overview]
Message-ID: <122752227576c059d2b1660934d57e991e7d33c8.camel@sipsolutions.net> (raw)
In-Reply-To: <CACT4ouduybj2Xn_=cgZynf7kF_7tx4cjydkWoTrCAg2=ujR2Tg@mail.gmail.com>

On Mon, 2022-11-21 at 09:32 +0100, Íñigo Huguet wrote:
> 
> > --- 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
> > 
> 
> Sorry for the delay with this, I had some issues with the hardware.
> 
> Using this workaround it doesn't show any errors and I can connect.

OK.

> However, using iwlwifi-QuZ-a0-jf-b0-74 from linux-firmware I get lots
> of errors, both with this patch applied and without it. Maybe the
> driver needs some changes?
> I get stack traces, fw dumps and message `iwlwifi 0000:00:14.3: Failed
> to send MAC context (action:1): -5`

Probably some other error?

> What would you recommend to do? It seems you didn't like this solution
> very much (and, as I say, it doesn't work with fw 74)


Well I think we still need this solution even if I didn't like it, and
the fw 74 seems to be a different issue - could you post more info about
separately?

johannes

  reply	other threads:[~2022-11-21 10:42 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
2022-10-05 10:09       ` Íñigo Huguet
2022-11-21  8:32       ` Íñigo Huguet
2022-11-21 10:42         ` Johannes Berg [this message]
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=122752227576c059d2b1660934d57e991e7d33c8.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