Re: qwx0: failed to send/start with QCNFA765

On Thu, 22 Feb 2024 17:17:45 +0100 Stefan Sperling wrote:
> On Thu, Feb 22, 2024 at 03:28:42PM +0100, Marco van Hulten wrote:
> > On Thu, 22 Feb 2024 13:29:27 +0100 Stefan Sperling wrote:
> > > Can you reproduce this on non-WPA-Enterprise networks,
> > > i.e. without eduraom / wpaakms 802.1x?
> >
> > Did not succeed in reproducing so far.
>
> I figured out the scan command error, details and patch below.
>
> The good news is that this is just a cosmetic issue.
> Let me know if you still see any issues with the patch applied.

This is good news. Thank you for your patch! I have not tested it. I
can do this this weekend; but if a snapshot would be built by then, I
will test it the morning hereafter (CET).

> > Additional dmesg output that seems to be new:
> >
> > qwx0: missed beacon threshold set to 30 beacons, beacon interval is
> > 100 TU qwx0: failed to enqueue rx buf: 28
> > qwx_ce_recv_process_cb: failed to post rx buf to pipe: 2 err: 28
>
> The above is a known issue I still need to investigate.
> I suspect it is harmless.

Okay, sounds good.

> Now, regarding your scan command failures:
> [...]
> qwx0: failed to start hw scan: 58
>
> So this is not an actual error condition, it is expected behaviour.
> ESHUTDOWN will cause the scan thread to stop what is it doing and
> allow the ifconfig driver thread to take back control of the hardware.
>
> The patch below should avoid printing a warning about this for all
> WMI commands, including your case, but handling other potential
> cases as well.

I can follow the explanation. There are quite a few exceptions just
for suppressing the printing, but it is clear what is done.

Right now I am using this qwx Wi-Fi at home without problems (but with
the error messages as I have not applied the patch). I've attached a
dmesg again, just in case it is useful.

Thanks again.

Marco