On Tue, 2025-05-13 at 10:04 -0500, Denis Kenzior wrote: > > I think it's expecting a confirm in response, but that was already lost > > before. > > Sorry, what is 'it' referring to here? mac80211 > iwd sends the Commit and Confirm via CMD_AUTHENTICATE. You can see that Commit > frame from the AP was received and then iwd submits a Confirm to the kernel: > > May 09 22:10:56 archlinux iwd[31729]: [SAE]: Sending Commit to 96:2a:6f:b6:d7:9f > May 09 22:10:56 archlinux iwd[31729]: [SAE]: Received frame transaction=1 > status=126 state=committed > May 09 22:10:56 archlinux iwd[31729]: [SAE]: Sending Confirm to > 96:2a:6f:b6:d7:9f sc=1 sure > The kernel then transmits the Confirm three times, but attempt 2 and 3 somehow > never make it out over the air. I find that strange since they should still go > out, regardless whether the Confirm from the AP was lost initially. By that time iwlwifi has given up on the whole thing and said it was disconnected, I'm not super surprised that something is mixed up. OTOH, according to trace-cmd, the frames _are_ going to the firmware and even ACKed in the log: irq/134-iwlwifi-392 [002] 64416.251984: iwlwifi_dbg: iwl_mvm_rx_tx_cmd_single -- TXQ 1 status SUCCESS (0x00000001) irq/134-iwlwifi-392 [002] 64416.251987: iwlwifi_dbg: iwl_mvm_rx_tx_cmd_single -- initial_rate 0x8100 retries 0, idx=3 ssn=4 next_reclaimed=0x4 seq_ctl=0x30 so not sure, the PHY context seems correct as well. Don't think this is the underlying issue here though. johannes
