On Mon, May 30, 2022 at 11:58:23PM +0100, Chris Narkiewicz wrote:
> > Do you see this problem with every access point, or just a specific one?
>
> I tried 2 APs with the same result.
>
> > Do see the problem while forcing 11n/11ac off? To do this you could try
> > forcing the driver into 11a mode
>
> Yes, my initial debug dmesg was generated using 11a mode.
> I have the same debug for 11ac, 11n and 11g modes.
Linux developers with access to magic tea leaves tell me that
sysassert code 0x000019A8 is related to Tx antenna configuration
info which the driver sends as part of the failing LQ command.
Can you please apply this patch, boot the resulting kernel, and
show me the new line that now appears in dmesg? It will show us
the antenna configuration of your device. Apparently the driver is
trying to use an antenna which is invalid. If that is indeed the case,
knowing which antennas are considered valid by the device should allow
us to fix the issue.
diff 83a9dfe1b143d86e38d14e824e87df26892a9d48 /usr/src
blob - 6de80bd303e3c03a8f4eb2533f54f65d4deebdd3
file + sys/dev/pci/if_iwm.c
--- sys/dev/pci/if_iwm.c
+++ sys/dev/pci/if_iwm.c
@@ -10161,6 +10161,10 @@ iwm_init_hw(struct iwm_softc *sc)
return EBUSY;
}
+ printf("%s: valid Tx antenna masks: phycfg: 0x%x nvm: 0x%x\n",
+ DEVNAME(sc), ((sc->sc_fw_phy_config & IWM_FW_PHY_CFG_TX_CHAIN)
+ >> IWM_FW_PHY_CFG_TX_CHAIN_POS), sc->sc_nvm.valid_tx_ant);
+
err = iwm_send_tx_ant_cfg(sc, iwm_fw_valid_tx_ant(sc));
if (err) {
printf("%s: could not init tx ant config (error %d)\n",
