2022-01-26 13:00:17

by Randy Dunlap

[permalink] [raw]
Subject: iwlwifi problems, maybe firmware related?

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

iwlwifi 0000:00:14.3: Detected Intel(R) Wi-Fi 6 AX201 160MHz, REV=0x354
iwlwifi 0000:00:14.3: Detected RF HR B3, rfid=0x10a100
iwlwifi 0000:00:14.3: base HW address: bc:09:1b:5f:30:25

wlan0: authenticate with d4:b9:2f:7c:10:db
wlan0: send auth to d4:b9:2f:7c:10:db (try 1/3)
wlan0: authenticated
wlan0: associate with d4:b9:2f:7c:10:db (try 1/3)
wlan0: RX AssocResp from d4:b9:2f:7c:10:db (capab=0x1511 status=0 aid=2)
iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.
iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 6
iwlwifi 0000:00:14.3: Loaded firmware version: 67.8f59b80b.0 QuZ-a0-hr-b0-67.ucode
iwlwifi 0000:00:14.3: 0x00001062 | ADVANCED_SYSASSERT
iwlwifi 0000:00:14.3: 0x0080A212 | trm_hw_status0
iwlwifi 0000:00:14.3: 0x00000000 | trm_hw_status1
iwlwifi 0000:00:14.3: 0x004CB2DE | branchlink2
iwlwifi 0000:00:14.3: 0x000018DC | interruptlink1
iwlwifi 0000:00:14.3: 0x000018DC | interruptlink2
iwlwifi 0000:00:14.3: 0x00000000 | data1
iwlwifi 0000:00:14.3: 0x00000001 | data2
iwlwifi 0000:00:14.3: 0xDEADBEEF | data3
iwlwifi 0000:00:14.3: 0x000AB296 | beacon time
iwlwifi 0000:00:14.3: 0x959B1740 | tsf low
iwlwifi 0000:00:14.3: 0x000000AC | tsf hi
iwlwifi 0000:00:14.3: 0x00000000 | time gp1
iwlwifi 0000:00:14.3: 0x00386026 | time gp2
iwlwifi 0000:00:14.3: 0x00000001 | uCode revision type
iwlwifi 0000:00:14.3: 0x00000043 | uCode version major
iwlwifi 0000:00:14.3: 0x8F59B80B | uCode version minor
iwlwifi 0000:00:14.3: 0x00000351 | hw version
iwlwifi 0000:00:14.3: 0x18489004 | board version
iwlwifi 0000:00:14.3: 0x8068FC32 | hcmd
iwlwifi 0000:00:14.3: 0x26620000 | isr0
iwlwifi 0000:00:14.3: 0x01000000 | isr1
iwlwifi 0000:00:14.3: 0x08B00002 | isr2
iwlwifi 0000:00:14.3: 0x00C34008 | isr3
iwlwifi 0000:00:14.3: 0x00000000 | isr4
iwlwifi 0000:00:14.3: 0x0035019C | last cmd Id
iwlwifi 0000:00:14.3: 0x0000B2C8 | wait_event
iwlwifi 0000:00:14.3: 0x00000080 | l2p_control
iwlwifi 0000:00:14.3: 0x00001C20 | l2p_duration
iwlwifi 0000:00:14.3: 0x0000003F | l2p_mhvalid
iwlwifi 0000:00:14.3: 0x00000080 | l2p_addr_match
iwlwifi 0000:00:14.3: 0x00000009 | lmpm_pmg_sel
iwlwifi 0000:00:14.3: 0x00000000 | timestamp
iwlwifi 0000:00:14.3: 0x000098E4 | flow_handler
iwlwifi 0000:00:14.3: Start IWL Error Log Dump:
iwlwifi 0000:00:14.3: Transport status: 0x0000004B, valid: 7
iwlwifi 0000:00:14.3: 0x20000070 | NMI_INTERRUPT_LMAC_FATAL
iwlwifi 0000:00:14.3: 0x00000000 | umac branchlink1
iwlwifi 0000:00:14.3: 0x80455E52 | umac branchlink2
iwlwifi 0000:00:14.3: 0x010332C0 | umac interruptlink1
iwlwifi 0000:00:14.3: 0xC0081AC6 | umac interruptlink2
iwlwifi 0000:00:14.3: 0x00000400 | umac data1
iwlwifi 0000:00:14.3: 0xC0081AC6 | umac data2
iwlwifi 0000:00:14.3: 0x00000000 | umac data3
iwlwifi 0000:00:14.3: 0x00000043 | umac major
iwlwifi 0000:00:14.3: 0x8F59B80B | umac minor
iwlwifi 0000:00:14.3: 0x0038604B | frame pointer
iwlwifi 0000:00:14.3: 0xC088750C | stack pointer
iwlwifi 0000:00:14.3: 0x003901A9 | last host cmd
iwlwifi 0000:00:14.3: 0x00000000 | isr status reg
iwlwifi 0000:00:14.3: IML/ROM dump:
iwlwifi 0000:00:14.3: 0x00000003 | IML/ROM error/state
iwlwifi 0000:00:14.3: 0x00005A13 | IML/ROM data1
iwlwifi 0000:00:14.3: 0x00000080 | IML/ROM WFPM_AUTH_KEY_0
iwlwifi 0000:00:14.3: Fseq Registers:
iwlwifi 0000:00:14.3: 0x60000000 | FSEQ_ERROR_CODE
iwlwifi 0000:00:14.3: 0x80290033 | FSEQ_TOP_INIT_VERSION
iwlwifi 0000:00:14.3: 0x00090006 | FSEQ_CNVIO_INIT_VERSION
iwlwifi 0000:00:14.3: 0x0000A482 | FSEQ_OTP_VERSION
iwlwifi 0000:00:14.3: 0x00000003 | FSEQ_TOP_CONTENT_VERSION
iwlwifi 0000:00:14.3: 0x4552414E | FSEQ_ALIVE_TOKEN
iwlwifi 0000:00:14.3: 0x20000302 | FSEQ_CNVI_ID
iwlwifi 0000:00:14.3: 0x01300504 | FSEQ_CNVR_ID
iwlwifi 0000:00:14.3: 0x20000302 | CNVI_AUX_MISC_CHIP
iwlwifi 0000:00:14.3: 0x01300504 | CNVR_AUX_MISC_CHIP
iwlwifi 0000:00:14.3: 0x05B0905B | CNVR_SCU_SD_REGS_SD_REG_DIG_DCDC_VTRIM
iwlwifi 0000:00:14.3: 0x0000025B | CNVR_SCU_SD_REGS_SD_REG_ACTIVE_VDIG_MIRROR
iwlwifi 0000:00:14.3: WRT: Collecting data: ini trigger 4 fired (delay=0ms).
ieee80211 phy0: Hardware restart was requested
iwlwifi 0000:00:14.3: FW error in SYNC CMD PHY_CONTEXT_CMD
CPU: 2 PID: 129 Comm: kworker/u16:3 Not tainted 5.16.0 #8
Hardware name: Dell Inc. Inspiron 15 5510/076F7Y, BIOS 2.4.1 11/05/2021
Workqueue: phy0 ieee80211_iface_work [mac80211]

iwlwifi 0000:00:14.3: PHY ctxt cmd error. ret=-5
wlan0: associated
iwlwifi 0000:00:14.3: Microcode SW error detected. Restarting 0x0.



Can anyone tell what's going on here?
Is it just firmware version problem?
Any suggestions/ideas?


This is openSUSE Tumbleweed (rolling updates) on a Dell Inspiron 15.
I don't know how new or old this problem is since I just got the laptop
and I haven't used anything older on it.

thanks.
--
~Randy


2022-01-26 13:09:32

by Ben Greear

[permalink] [raw]
Subject: Re: iwlwifi problems, maybe firmware related?

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.

Thanks,
Ben

--
Ben Greear <[email protected]>
Candela Technologies Inc http://www.candelatech.com

2022-01-26 15:26:25

by Randy Dunlap

[permalink] [raw]
Subject: Re: iwlwifi problems, maybe firmware related?



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.

--
~Randy

2022-01-26 20:16:56

by Luciano Coelho

[permalink] [raw]
Subject: Re: iwlwifi problems, maybe firmware related?

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.

2022-01-26 20:23:23

by Ben Ami, Golan

[permalink] [raw]
Subject: RE: iwlwifi problems, maybe firmware related?

Hey,

Here it is:
https://bugzilla.kernel.org/show_bug.cgi?id=215488

Thanks,
Golan.

-----Original Message-----
From: Coelho, Luciano <[email protected]>
Sent: Wednesday, January 26, 2022 09:13
To: [email protected]; greearb <[email protected]>; [email protected]
Cc: Ben Ami, Golan <[email protected]>
Subject: Re: iwlwifi problems, maybe firmware related?

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.
---------------------------------------------------------------------
A member of the Intel Corporation group of companies

This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.

2022-01-26 22:28:50

by Luciano Coelho

[permalink] [raw]
Subject: Re: iwlwifi problems, maybe firmware related?

On Wed, 2022-01-26 at 10:32 -0800, Randy Dunlap wrote:
> Hi--
>
> On 1/25/22 23:12, Coelho, Luciano wrote:
> > 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).
>
> Just confirming that kernel 5.16 without broadcast filtering works
> with firmware v67.

Great, thanks for the confirmation!

Just out of curiosity. How did you end up with broadcast filtering
enabled? Is it a default configuration from some distro?


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

Will do.

--
Cheers,
Luca.

2022-01-26 22:30:21

by Randy Dunlap

[permalink] [raw]
Subject: Re: iwlwifi problems, maybe firmware related?

Hi--

On 1/25/22 23:12, Coelho, Luciano wrote:
> 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).

Just confirming that kernel 5.16 without broadcast filtering works
with firmware v67.

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

Yes, please.

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



--
~Randy

2022-01-26 22:31:28

by Randy Dunlap

[permalink] [raw]
Subject: Re: iwlwifi problems, maybe firmware related?



On 1/26/22 10:36, Coelho, Luciano wrote:
> On Wed, 2022-01-26 at 10:32 -0800, Randy Dunlap wrote:
>> Hi--
>>
>> On 1/25/22 23:12, Coelho, Luciano wrote:
>>> 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).
>>
>> Just confirming that kernel 5.16 without broadcast filtering works
>> with firmware v67.
>
> Great, thanks for the confirmation!
>
> Just out of curiosity. How did you end up with broadcast filtering
> enabled? Is it a default configuration from some distro?
>

Nope. I didn't know that it was not supported so I enabled it.

>
>>> I have removed this option from the driver now and will send the patch
>>> to 5.17-rc* as a fix.
>>
>> Yes, please.
>
> Will do.
>
> --
> Cheers,
> Luca.

--
~Randy