Linux wireless drivers development
 help / color / mirror / Atom feed
From: "Coelho, Luciano" <luciano.coelho@intel.com>
To: "linux-wireless@vger.kernel.org" <linux-wireless@vger.kernel.org>,
	greearb <greearb@candelatech.com>,
	"rdunlap@infradead.org" <rdunlap@infradead.org>
Cc: "Ben Ami, Golan" <golan.ben.ami@intel.com>
Subject: Re: iwlwifi problems, maybe firmware related?
Date: Wed, 26 Jan 2022 07:12:47 +0000	[thread overview]
Message-ID: <cb3e4991c19659ab73cc0d9c12e8b7dbba9d652d.camel@intel.com> (raw)
In-Reply-To: <0ee64c55-1326-addb-7c9c-c922373f78c0@infradead.org>

Hi,

Adding Golan to the thread.

On Tue, 2022-01-25 at 18:20 -0800, Randy Dunlap wrote:
> 
> On 1/25/22 15:58, Ben Greear wrote:
> > On 1/25/22 3:08 PM, Randy Dunlap wrote:
> > > Hi,
> > > 
> > > When I boot 5.16 or 5.17-rc1, I get messages like:
> > > 
> > > iwlwifi 0000:00:14.3: api flags index 2 larger than supported by driver
> > > iwlwifi 0000:00:14.3: TLV_FW_FSEQ_VERSION: FSEQ Version: 89.3.35.37
> > > iwlwifi 0000:00:14.3: loaded firmware version 67.8f59b80b.0 QuZ-a0-hr-b0-67.ucode op_mode iwlmvm
> > 
> > We see nothing but crashes with the version 67 firmware.  Remove that
> > from your /lib/firmware/ dir (and make sure version 66 or lower is there),
> > and reboot and it should work again.
> 
> Well. Yes, that does make things work for me.
> 
> It's odd, though, that openSUSE Tumbleweed with kernel "Linux version 5.16.1-1-default"
> (whatever that is) also works with no problems.
> 
> Thanks for your help.

This is because of broadcast filtering.  This feature hasn't been
supported for quite a while and now the firmware rejects the command we
send to it.

The easy fix is to compile iwlwifi without
CONFIG_IWLWIFI_BCAST_FILTERING (which should not be enabled by
default).

I have removed this option from the driver now and will send the patch
to 5.17-rc* as a fix.

Golan, I think we have a bugzilla for this, do you remember?


--
Cheers,
Luca.

  reply	other threads:[~2022-01-26  7:12 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-25 23:08 iwlwifi problems, maybe firmware related? Randy Dunlap
2022-01-25 23:58 ` Ben Greear
2022-01-26  2:20   ` Randy Dunlap
2022-01-26  7:12     ` Coelho, Luciano [this message]
2022-01-26  7:37       ` Ben Ami, Golan
2022-01-26 18:32       ` Randy Dunlap
2022-01-26 18:36         ` Coelho, Luciano
2022-01-26 18:46           ` Randy Dunlap

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=cb3e4991c19659ab73cc0d9c12e8b7dbba9d652d.camel@intel.com \
    --to=luciano.coelho@intel.com \
    --cc=golan.ben.ami@intel.com \
    --cc=greearb@candelatech.com \
    --cc=linux-wireless@vger.kernel.org \
    --cc=rdunlap@infradead.org \
    /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