Index | Thread | Search

From:
Marcus Glocker <marcus@nazgul.ch>
Subject:
Re: sys/qwz: shutdown firmware after autoconf
To:
"Kirill A. Korinsky" <kirill@korins.ky>
Cc:
tech@openbsd.org
Date:
Tue, 2 Jun 2026 05:53:35 +0200

Download raw body.

Thread
On Mon, Jun 01, 2026 at 10:45:43PM +0200, Kirill A. Korinsky wrote:

> On Mon, 01 Jun 2026 22:27:27 +0200,
> Marcus Glocker <marcus@nazgul.ch> wrote:
> > 
> > On Mon, Jun 01, 2026 at 09:50:48PM +0200, Kirill A. Korinsky wrote:
> > 
> > > tech@,
> > > 
> > > seems that I had figured out why we need a hack to keep qwz running after
> > > autoconf.
> > > 
> > > So, here I reset pending MHI transfers and the command ring queue counter
> > > during shutdown, and remove fw_initialized so the next ifconfig up performs
> > > a full firmware boot.
> > > 
> > > Thoughts? Ok?
> > 
> > I just gave it a quick spin, but it re-introduces the issue I faced
> > before on a NWID switch attempt:
> > 
> > ifconfig: SIOCS80211NWID: Resource temporarily unavailable
> > ifconfig: qwz0: SIOCS80211WPAPSK: Resource temporarily unavailable
> > 
> > ***
> > 
> > qwz0: tx credits timeout
> > qwz0: failed to send WMI_PDEV_SET_PARAM cmd
> > qwz0: failed to enable MESH MCAST ENABLE for pdev 0: 35
> > qwz0: tx credits timeout
> > qwz0: failed to send WMI_PDEV_SET_PARAM cmd
> > qwz0: failed to enable MESH MCAST ENABLE for pdev 0: 35
> > qwz0: tx credits timeout
> > qwz0: failed to send WMI_PDEV_SET_PARAM cmd
> > qwz0: failed to enable MESH MCAST ENABLE for pdev 0: 35
> > qwz0: tx credits timeout
> > qwz0: failed to send WMI_PDEV_SET_PARAM cmd
> > qwz0: failed to enable MESH MCAST ENABLE for pdev 0: 35
> >
> 
> Does switch from NWID/AP really work on your device?

In some cases I can indeed re-associate to another NWID during runtime.
Still, afterwards there is no traffic flowing.  I try to understand why,
but no luck so far :-(
 
> On my machine I can connect only to one AP per boot. Anything else is ended
> with "Resource temporarily unavailable"

This error is completely gone with HEAD here, no matter what I am doing.

I am also chasing why upon boot my 5GHz AP always works, while my 2.4GHz
AP only intermittently works.  In the most cases I can associate to it,
but I won't get an IP assigned.  In a few cases I will, and then also
traffic is flowing.  I am also playing around with reverting the RX QoS
path which we have recently introduced.  It seems to increase the
chances that my 2.4GHz AP will work, but it still not reliable.

The entire situation is a bit puzzling to me currently ...