Re: iwlwifi/LinuxKPI 802.11 update

From: Bjoern A. Zeeb <bz_at_FreeBSD.org>
Date: Thu, 24 Mar 2022 22:26:45 UTC
On Thu, 24 Mar 2022, J.R. Oldroyd wrote:

> On Thu, 24 Mar 2022 15:48:55 -0400 "J.R. Oldroyd" <fbsd@opal.com> wrote:
>>
>> [ report re iwlwifi on 8265 ]
>
> I also see this in the log:


That's the things I am interested in ..


> Mar 24 15:28:08 susauq kernel: iwlwifi0: No beacon heard and the time event is over already...

Sigh.

> Mar 24 15:28:37 susauq kernel: iwlwifi0: iwl_trans_send_cmd bad state = 0
> Mar 24 15:28:37 susauq kernel: iwlwifi0: Failed to remove MAC context: -5
> Mar 24 15:28:37 susauq kernel: iwlwifi0: iwl_trans_send_cmd bad state = 0
> Mar 24 15:28:37 susauq kernel: iwlwifi0: Failed to synchronize multicast groups update
> Mar 24 15:28:37 susauq kernel: iwlwifi0: iwl_trans_send_cmd bad state = 0
> Mar 24 15:28:37 susauq kernel: iwlwifi0: Failed to synchronize multicast groups update
> Mar 24 15:28:37 susauq kernel: iwlwifi0: iwl_trans_send_cmd bad state = 0
> Mar 24 15:28:37 susauq kernel: iwlwifi0: Failed to synchronize multicast groups update
> Mar 24 15:28:39 susauq kernel: iwlwifi0: lkpi_sta_scan_to_auth: waiting for 5 queues to be allocated by driver
> Mar 24 15:28:39 susauq kernel: iwlwifi0: No beacon heard and the time event is over already...
> Mar 24 15:28:46 susauq kernel: iwlwifi0: lkpi_sta_scan_to_auth: waiting for 5 queues to be allocated by driver

More sigh.
Did it work despite of that?


I assume that's also the 18:50 UTC main build?


I'll get back to you again off-list tomorrow afternoon at some point about
this.


/bz

-- 
Bjoern A. Zeeb                                                     r15:7