<f00b4r0>
nbd: building kmod, will install and report
<f00b4r0>
nbd: I'm seeing hostapd eating 25% cpu constantly now, is that expected?
<f00b4r0>
nothing in logs
<f00b4r0>
it's totally unresponsive to ubus calls (e.g. get_clients times out)
<f00b4r0>
hmm not all aps are up: only 1 instead of 3 on 5GHz. Something is broken here.
<f00b4r0>
nbd: so I've deployed on 3 devices: router + 2 dumb APs, all same hw. The two dumb APs are now unusable for wifi: hostapd pegged and unresponsive. 2 out of 3 APs missing on 5GHz.
<f00b4r0>
iwinfo assoclist shows only one client connected on one of the 2.4G aps, on each device, and it's one of the infamous tuya systems
<f00b4r0>
it seems to be the root cause because the router is not affected (all phy-aps present on both bands, everything normal), and it doesn't have any tuya device associated
<f00b4r0>
I can't keep this running for very long (location is disturbed) so I'll revert if I don't hear from you shortly
<f00b4r0>
wifi up/down also not working
<f00b4r0>
killing and restarting hostapd seems to have done the trick
<f00b4r0>
+ wifi down / up
<f00b4r0>
looks like some sort of deadlock
n3ph has joined #openwrt-devel
<f00b4r0>
nbd: fwiw both dumb APs have 2 tuya devices "harrassing" them. is it possible that there's some race in the code triggered by the second one? When hung, only one device was associated.
rua has quit [Quit: Leaving.]
warpme has quit []
rsalvaterra has quit []
n3ph has quit [Ping timeout: 480 seconds]
rsalvaterra has joined #openwrt-devel
danitool has joined #openwrt-devel
rmilecki has joined #openwrt-devel
schwicht has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
schwicht has joined #openwrt-devel
rua has joined #openwrt-devel
schwicht has quit [Ping timeout: 480 seconds]
warpme has joined #openwrt-devel
SwedeMike has quit [Quit: leaving]
warpme has quit []
KGB-2 has quit [Remote host closed the connection]
KGB-2 has joined #openwrt-devel
warpme has joined #openwrt-devel
valku has joined #openwrt-devel
rua has quit [Remote host closed the connection]
rua has joined #openwrt-devel
rua is now known as Guest24394
rua has joined #openwrt-devel
Guest24394 has quit [Remote host closed the connection]
<f00b4r0>
nbd: patch introduces a different bug:
<f00b4r0>
Mon Aug 18 12:18:26 2025 daemon.info hostapd: phy0-ap0: STA c4:82:e1:ad:ef:8e IEEE 802.11: deauthenticated due to local deauth request
<f00b4r0>
it seems to make a little more "sense" indeed
n3ph has quit [Ping timeout: 480 seconds]
<nbd>
btw. one way to get even better information is to use the kernel faddr2line script - use gdb to resolve the nearest function, calculate the offset and then do faddr2line mt7996e.ko func+offset
<nbd>
since it shows the callsites of inline functions where gdb only shows the inline functions themselves
<f00b4r0>
I'll take a look
<f00b4r0>
btw readelf shows this for mt7915e: [ 3] .text PROGBITS 00000000 000090 0184c0 00 AX 0 0 16