On Wed, Dec 20, 2023 at 02:00:36PM -0800, Greg Steuck wrote:
> I'm sending this with the subject of the bug reported before in hope it will 
> join
> the thread even though I'm seeing this with an iwm(4) interface. I'm
> running a Nov 3 snap of -current.
> 
> The messages seem mostly harmless as the interface recovers without prodding.
> 
> iwm0 at pci0 dev 20 function 3 "Intel AC 9560" rev 0x11, msix
> iwm0: hw rev 0x310, fw ver 46.ff18e32a.0, address 50:e0:85:
> 
> iwm0: flags=808843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST,AUTOCONF4> mtu 1500
>       lladdr 50:e0:85:
>       index 1 priority 4 llprio 3
>       groups: wlan egress
>       media: IEEE802.11 autoselect (VHT-MCS0 mode 11ac)
>       status: active
>       ieee80211: join XXX chan 153 bssid 66:22:32: 97% wpakey wpaprotos wpa2 
> wpaakms psk wpaciphers ccmp wpagroupcipher ccmp
>       inet 192.168.0.101 netmask 0xffffff00 broadcast 192.168.0.255
> 
> % grep iwm /var/log/messages
> Dec 20 09:23:19 lenny /bsd: iwm0: unhandled firmware response 
> 0x3fd/0x3800000c rx ring 0[198]
> Dec 20 11:03:23 lenny /bsd: iwm0: unhandled firmware response 
> 0x3fd/0x3800000c rx ring 32[143]
> Dec 20 12:19:53 lenny /bsd: iwm0: unhandled firmware response 
> 0x3fd/0x3800000c rx ring 19[216]
> Dec 20 13:01:56 lenny /bsd: iwm0: unhandled firmware response 
> 0x3fd/0x3800000c rx ring 30[46]
> Dec 20 13:26:17 lenny /bsd: iwm0: unhandled firmware response 
> 0x3fd/0x3800000c rx ring 19[171]
> Dec 20 13:33:17 lenny /bsd: iwm0: unhandled firmware response 
> 0x3fd/0x3800000c rx ring 54[207]

I cannot tell what this firmware message is about because it is undocumented.

The response code decodes to MAC_CONF_GROUP (0x3) and sub-command 0xfd,
which is not listed in the firmware API header file:
https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/backport-iwlwifi.git/tree/drivers/net/wireless/intel/iwlwifi/fw/api/mac-cfg.h#n76
0xfd is located in the range between PROBE_RESPONSE_DATA_NOTIF and
CHANNEL_SWITCH_START_NOTIF. So it is likely some other xxx_NOTIF event.

Without further information the best we could do is ignore the event.
But I will try to ask Linux developers for clues first.

> Dec 20 13:52:30 lenny /bsd: iwm0: fatal firmware error

Could you enable 'ifconfig iwx0 debug' and trigger this firmware error again
to get more details about the error?

Reply via email to