Re: Update on AlderLake stuck on 2.4G

On Sun, 4 May 2025, Adrian Chadd wrote:

> On Sun, 4 May 2025 at 10:41, Bjoern A. Zeeb <bz@freebsd.org> wrote:
>
>> On Sun, 4 May 2025, Kevin Oberman wrote:
>>
>> Hi,
>>
>>> I have now located and am now running on an ASUS RT-ARCH13 router
>> connected
>>> to Comcast. This device claims WiFi5 compliance with 11ac and CCMP.
>>>
>>> Still stuck at 11ng and only connects at 2.4G.
>>>
>>>> ifconfig wlan0
>>> wlan0: flags=8843<UP,BROADCAST,RUNNING,SIMPLEX,MULTICAST> metric 0 mtu
>> 1500
>>> options=0
>>> ether 70:a8:d3:df:3c:de
>>> inet 192.168.1.5 netmask 0xffffff00 broadcast 192.168.1.255
>>> groups: wlan
>>> ssid babcom channel 11 (2462 MHz 11g ht/20) bssid 4c:ed:fb:37:b0:20
>>> regdomain FCC country US authmode WPA2/802.11i privacy ON
>>> deftxkey UNDEF AES-CCM 2:128-bit txpower 30 bmiss 7 scanvalid 60
>>> protmode CTS -ampdu ampdulimit 64k -amsdutx amsdurx shortgi
>>> -ldpctx ldpcrx -uapsd wme roaming MANUAL
>>> parent interface: iwlwifi0
>>> media: IEEE 802.11 Wireless Ethernet MCS mode 11ng
>>> status: associated
>>> nd6 options=29<PERFORMNUD,IFDISABLED,AUTO_LINKLOCAL>
>>>
>>> My AP shows up as: 11   54M  -51:-96   100 EP   HTCAP VHTCAP VHTOPMODE
>> WME
>>> ATH RSN
>>> The 5G SSID does not show up at all, though my phone shows it and
>> connects
>>> successfully. Attempts to manually scan return instantly and list scan
>>> always list the exact same data including S/N, so it does not seem to
>>> actually scan.
>>
>
> Is there still that scan bug where an interrupted scan never finishes, and
> thus "ifconfig wlan0 scan" always returns cached scan results?
> I thought that was fixed years ago. :/

No. It never was. My last attempts didn't fully fix it all either.
But also the scan framework is insufficient as one could not even swap
between hwscan and swscan which made me stop last time as Realtek might
need that.  Anyway ...

> Also, Kevin, is this on iwlwifi? That should be doing offloaded scanning,

It says above in the ifconfig output Adrian.

> right bz? So as long as we send a well crafted firmware
> message with a useful dwell time, it should be seeing the beacons?
>
> What dwell time is being configured when doing scanning on iwlwifi?

This worked for ages.  We are seeing all kinds of weird things recently.
My current bet is the next race conditions and memory corruption in
net80211 but it's kind-of hard to track it down through remote debugging
through email until one can reproduce it locally and then things go a
lot faster.

That said, can we https://reviews.freebsd.org/D49865 into the tree so
that one of these problems possibly leading to panics is gone?

/bz

-- 
Bjoern A. Zeeb                                                     r15:7