Date: Tue, 21 Oct 2025 07:10:21 -0700 From: Adrian Chadd <adrian.chadd@gmail.com> To: Andriy Gapon <avg@freebsd.org> Cc: "freebsd-wireless@freebsd.org" <wireless@freebsd.org> Subject: Re: wlan: UP but not RUNNING ? Message-ID: <CAJ-VmonbRK1-mVcHs83sHNQYwXqxoy3nAGiQDmJ0mNaBw_eP8A@mail.gmail.com> In-Reply-To: <81321964-801f-497b-ab46-d8866401e900@FreeBSD.org> References: <8ed936d2-242a-4dca-a38b-1117b41e87ef@FreeBSD.org> <6a2e22ae-b8f9-46de-8a0f-881d7c01ceb0@FreeBSD.org> <81321964-801f-497b-ab46-d8866401e900@FreeBSD.org>
index | next in thread | previous in thread | raw e-mail
[-- Attachment #1 --] hi, Ok, let's file a PR with what you have and then dig into it a bit more! thanks, -a On Tue, 21 Oct 2025 at 06:30, Andriy Gapon <avg@freebsd.org> wrote: > On 21/10/2025 16:05, Andriy Gapon wrote: > > It seems that the problem happens because the VAP is already in > IEEE80211_S_RUN > > state somehow and ieee80211_start_locked is not called, obviously, in > > SIOCSIFFLAGS handling code. > > I have this DTrace output to confirm that: > > ieee80211_ioctl:entry wlan0 cmd 0x80206910 flags 0x8902 drv flags 0 state 5 > ieee80211_ioctl:entry wlan0 cmd 0x80206910 flags 0x8903 drv flags 0 state 5 > > So, the VAP state is indeed IEEE80211_S_RUN. > But IFF_RUNNING / IFF_DRV_RUNNING is not set in either if_flags or > if_drv_flags. > > Looks like something set the VAP state bypassing the interface state > machinery. > > I tried to catch the state transitions with wlandebug_wlan0 in rc.conf but > apparently that changes timing enough to mask the issue. > > -- > Andriy Gapon > > [-- Attachment #2 --] <div dir="ltr"><div>hi,</div><div><br></div><div>Ok, let's file a PR with what you have and then dig into it a bit more!</div><div><br></div><div>thanks,</div><div><br></div><div><br></div><div>-a</div><div><br></div></div><br><div class="gmail_quote gmail_quote_container"><div dir="ltr" class="gmail_attr">On Tue, 21 Oct 2025 at 06:30, Andriy Gapon <<a href="mailto:avg@freebsd.org">avg@freebsd.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On 21/10/2025 16:05, Andriy Gapon wrote:<br> > It seems that the problem happens because the VAP is already in IEEE80211_S_RUN <br> > state somehow and ieee80211_start_locked is not called, obviously, in <br> > SIOCSIFFLAGS handling code.<br> <br> I have this DTrace output to confirm that:<br> <br> ieee80211_ioctl:entry wlan0 cmd 0x80206910 flags 0x8902 drv flags 0 state 5<br> ieee80211_ioctl:entry wlan0 cmd 0x80206910 flags 0x8903 drv flags 0 state 5<br> <br> So, the VAP state is indeed IEEE80211_S_RUN.<br> But IFF_RUNNING / IFF_DRV_RUNNING is not set in either if_flags or if_drv_flags.<br> <br> Looks like something set the VAP state bypassing the interface state machinery.<br> <br> I tried to catch the state transitions with wlandebug_wlan0 in rc.conf but <br> apparently that changes timing enough to mask the issue.<br> <br> -- <br> Andriy Gapon<br> <br> </blockquote></div>home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?CAJ-VmonbRK1-mVcHs83sHNQYwXqxoy3nAGiQDmJ0mNaBw_eP8A>