Hey Bjoern, Thanks again for all your efforts! I hope you don't get discouraged by the lack of feedback on recent commits. As far as I can tell, most of us are on stable/13 (I certainly am). Personally, I usually wait for the MFCs. I don't mind cherry-picking but without actually inspecting the diffs it's often difficult determine whether only cherry-picking your iwlwifi related commits are necessary. I do spot the occasional LinuxKPI commits which make me doubt whether they are necessary too.
Best regards, ~ Joel ------- Original Message ------- On Thursday, March 24th, 2022 at 21:28, J.R. Oldroyd <f...@opal.com> wrote: > On Thu, 24 Mar 2022 15:48:55 -0400 "J.R. Oldroyd" f...@opal.com wrote: > > > [ report re iwlwifi on 8265 ] > > I also see this in the log: > > Mar 24 15:28:08 susauq kernel: iwlwifi0: No beacon heard and the time event > is over already... > > 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
