On Sun, Jun 12, 2022 at 01:16:00PM +0200, Stefan Sperling wrote:
> On Sun, Jun 12, 2022 at 10:28:33AM +0200, Christian Schulte wrote:
> > Please see attached dmesg and pcidump. There has been a similar issue with
> > the if_iwm.c driver. Maybe this one is related.
>
> These are seperate drivers so it is unlikely that these issues would
> be related.
>
> How many different access points have you tried to reproduce the
> problem with so far?
In any case we will need to figure out which command is failing for you.
The patch below adds additional debug output while 'ifconfig iwn0 debug'
is enabled and should display the command code sent to firmware. Hopefully
this can tell us which command firmware is complaining about.
Can you reproduce the failure with it again and send new debug output?
diff 83a9dfe1b143d86e38d14e824e87df26892a9d48 /usr/src
blob - 1446e2d9c7d71bb1360e96b018c63d06695fc23f
file + sys/dev/pci/if_iwn.c
--- sys/dev/pci/if_iwn.c
+++ sys/dev/pci/if_iwn.c
@@ -3863,6 +3863,8 @@ iwn_cmd(struct iwn_softc *sc, int code, const void *bu
/* Update TX scheduler. */
ops->update_sched(sc, ring->qid, ring->cur, 0, 0);
+ if (sc->sc_ic.ic_if.if_flags & IFF_DEBUG)
+ printf("%s: sending command %d\n", sc->sc_dev.dv_xname, code);
/* Kick command ring. */
ring->cur = (ring->cur + 1) % IWN_TX_RING_COUNT;
IWN_WRITE(sc, IWN_HBUS_TARG_WRPTR, ring->qid << 8 | ring->cur);
