Packet-steering + usteer/802.11krv soft-bricks routers - worked before in 24.10.4-5 snapshots, not in 25.12.0*

davygravy · March 7, 2026, 7:54pm

I have two MR7350’s running as Bridged APs, originally had a 24.10.4-ish snapshot installed. I have ZRAM swap enabled on both. Wifi FT/roaming worked very well using usteer and a non-basic wpad (mbedtls or openssl).

With the upgrade to 25.12.0, they seem to act very differently. Starting service wpad restart with 802.11kvr enabled and usteer, they both soft-bricked. After resetting them and with about a dozen reset/reinstall attempts, I am pretty sure that either something in the wpad stack/setup for this router is borked in 25.12.0, or perhaps ZRAM has some hidden problem or incompatibility with the current wpad or other binary.

The behavior is repeatable: A fresh install of 25.12.0* with no other added packages…, install wpad-mbedtls or wpad-openssl, and restart with service wpad restart. The router will soft brick w/ red light. Following top and dmesg as I restart wpad in another ssh window yields no clues.

Before attaching on of my MR7350s to serial connection for troubleshooting, I want to rule out other things.

Is my ZRAM swap working as expected? I think so.

root@AirDisk2:~# stress-ng --vm 8 --vm-bytes 512M -t 30s --oom-avoid

… yields this…


root@AirDisk2:~# service zram restart
zram_stop: deactivate swap /dev/zram0
zram_reset: claiming memory back via /sys/block/zram0/reset
zram_start: activating '/dev/zram0' for swapping (189 MiB)
zram_reset: enforcing defaults via /sys/block/zram0/reset
zram_comp_algo: set compression algorithm 'lzo' for zram '/dev/zram0'
Setting up swapspace version 1, size = 198176768 bytes

root@AirDisk2:~# free -h
total        used        free      shared  buff/cache   available
Mem:         387992      253912       84060        2012       50020       83488
Swap:        193532           0      193532

root@AirDisk2:~# sysctl -a | grep swap
vm.swappiness = 90

root@AirDisk2:~# sysctl -a | grep vm.
vm.admin_reserve_kbytes = 8192
vm.compact_unevictable_allowed = 1
vm.compaction_proactiveness = 20
vm.dirty_background_bytes = 0
vm.dirty_background_ratio = 10
vm.dirty_bytes = 0
vm.dirty_expire_centisecs = 3000
vm.dirty_ratio = 20
vm.dirty_writeback_centisecs = 500
vm.dirtytime_expire_seconds = 43200
vm.extfrag_threshold = 500
vm.laptop_mode = 0
vm.legacy_va_layout = 0
vm.lowmem_reserve_ratio = 256	256	32	0
vm.max_map_count = 65530
vm.memfd_noexec = 0
vm.min_free_kbytes = 16384
vm.mmap_min_addr = 4096
vm.mmap_rnd_bits = 18
vm.oom_dump_tasks = 1
vm.oom_kill_allocating_task = 0
vm.overcommit_kbytes = 0
vm.overcommit_memory = 0
vm.overcommit_ratio = 50
vm.page-cluster = 3
vm.page_lock_unfairness = 5
vm.panic_on_oom = 0
vm.percpu_pagelist_high_fraction = 0
vm.stat_interval = 1
vm.swappiness = 90
vm.user_reserve_kbytes = 11903
vm.vfs_cache_pressure = 100
vm.watermark_boost_factor = 15000
vm.watermark_scale_factor = 10

root@AirDisk2:~# /etc/init.d/zram status

Gathering stats info for zram device "zram0"

ZRAM
----
Block device              - /sys/block/zram0
Device size               - 189 MiB
Compression algo          - lzo-rle [lzo] 

DATA
----
Original data size        - 3.34 MiB
Compressed data size      - 0.76 MiB
Compress ratio            - 4.37 

MEMORY
------
Memory used, total        - 2.58 MiB
Allocator overhead        - 1.82 MiB
Allocator efficiency      - 29.55 %
Maximum memory ever used  - 74.87 MiB
Memory limit              - 0.00 MiB

PAGES
-----
Same pages count          - 0
Pages compacted           - 102568
Free pages discarded      - 9092578

=============================

Solutions/thoughts:

(contributing problem) The device did soft-brick (IMHO - looking at how Openwrt defines soft-brick) but it was because of problem in the dual-firmware setup - I believe this was my mistake. There is a bug/problem for the MR7350’s in which flash layout/partitioning, where flashing to be approached a bit differently. This post shows how to flash it usually, but it may fail if the flash target is not 16MB, but rather 8MB+8MB. That was the case in my router, fixed by following this procedure. So, when the kernel panics occurred, for some reason the router would either Boot-Loop or it would try to boot the other ( alt_kernel ) and fail with the red flashing LED. Now that there are two valid images to boot, it is working as expected. DONE
For the dual-boot setup, I’ll be staying with 25.12.0 as one choice, and more proven 24.10.5 as a failsafe. DONE
(main problem) The kernel panics/reboots have seemed to stop completely since I disabled the software Packet Steering (Interfaces > Global Settings). With this, usteer and 802.11rkv Fast Transition w/ Roaming is again working as it should. DONE.
(not a contributing problem, but needs a lot of work) My config works, but the two initial responders ( thank you @anon63541380 and @psherman) pointed out quite a few gaffs/issues/inconsistencies with the setup of my network. It does what I need it to do, but I see the issues in it and I’ll work with @psherman or others as I get time/energy to put a plan together so that my IoT and regular subnets are actually segregated to some degree. This will take some thinking on my part, since I want most of the IoT subnet to be blocked off from the internet, but not all of it. I also want to add a guest network. [all yet to do…]
The config worked perfectly in 24.10.5. I’ve not yet determined what the change was in 25.12.0 that caused the problems. It may have been a change in the config layout, or a default different. [ yet to do ]

anon63541380 · March 7, 2026, 9:22pm

That is not "soft bricked", maybe a kernel crashed maximum.
Can you show an example of a client needing KVR?

Please connect to your OpenWrt device using ssh and copy the output of the following commands and post it here using the "Preformatted text </> " button (red circle; this works best in the 'Markdown' composer view in the blue oval):

Remember to redact passwords, VPN keys, MAC addresses and any public IP addresses you may have:

ubus call system board
cat /etc/config/network
cat /etc/config/wireless
cat /etc/config/dhcp
cat /etc/config/firewall

davygravy · March 7, 2026, 11:06pm

Thank you @anon63541380 .
Here is the output:

root@AirDisk2:~# ubus call system board
{
	"kernel": "6.12.71",
	"hostname": "AirDisk2",
	"system": "ARMv8 Processor rev 4",
	"model": "Linksys MR7350",
	"board_name": "linksys,mr7350",
	"rootfs_type": "squashfs",
	"release": {
		"distribution": "OpenWrt",
		"version": "25.12.0-rc5",
		"firmware_url": "https://downloads.openwrt.org/",
		"revision": "r32673-482ba7230a",
		"target": "qualcommax/ipq60xx",
		"description": "OpenWrt 25.12.0-rc5 r32673-482ba7230a",
		"builddate": "1771363837"
	}
}
root@AirDisk2:~# cat /etc/config/network

config interface 'loopback'
	option device 'lo'
	option proto 'static'
	list ipaddr '127.0.0.1/8'

config globals 'globals'
	option dhcp_default_duid '0004b7f8bc39b65543ddb1c7fd67eab78c82'
	option ula_prefix 'fd4a:223b:da83::/48'
	option packet_steering '1'

config device
	option name 'br-lan'
	option type 'bridge'
	option igmp_snooping '1'
	list ports 'lan1'
	list ports 'lan2'
	list ports 'lan3'
	list ports 'lan4'
	list ports 'wan'
	option arp_accept '1'
	option ipv6 '0'

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ip6assign '60'
	option gateway '192.168.11.2'
	list dns '192.168.11.2'
	option broadcast '192.168.11.255'
	list ipaddr '192.168.11.8/23'

config interface 'lan_IoT'
	option proto 'static'
	option device 'br-lan'
	option ipaddr '192.168.11.8'
	option gateway '192.168.11.2'
	option netmask '255.255.254.0'
	option broadcast '192.168.11.255'

config device
	option name 'wan'

config device
	option name 'phy0-ap0'

root@AirDisk2:~# cat /etc/config/wireless

config wifi-device 'radio0'
	option type 'mac80211'
	option path 'platform/soc@0/c000000.wifi'
	option band '5g'
	option channel '36'
	option htmode 'HE80'
	option country 'US'
	option cell_density '0'
	option disabled '1'

config wifi-iface 'default_radio0'
	option device 'radio0'
	option network 'lan'
	option mode 'ap'
	option ssid 'AirDisk1'
	option encryption 'psk2'
	option key 'REDACTED'
	option ieee80211r '1'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option ieee80211k '1'
	option bss_transition '1'
	option mobility_domain '1a2b'
	option wnm_sleep_mode '1'
	option wnm_sleep_mode_no_keys '1'
	option proxy_arp '1'
	option disabled '1'

config wifi-device 'radio1'
	option type 'mac80211'
	option path 'platform/soc@0/c000000.wifi+1'
	option band '2g'
	option channel '1'
	option cell_density '0'
	option country 'US'
	option htmode 'HT20'

config wifi-iface 'default_radio1'
	option device 'radio1'
	option network 'lan'
	option mode 'ap'
	option ssid 'AirDisk1'
	option encryption 'psk2'
	option key 'REDACTED'
	option ieee80211r '1'
	option ft_over_ds '0'
	option ft_psk_generate_local '1'
	option ieee80211k '1'
	option bss_transition '1'
	option mobility_domain '1a2b'
	option wnm_sleep_mode '1'
	option wnm_sleep_mode_no_keys '1'
	option proxy_arp '1'
	option disabled '1'

config wifi-iface 'wifinet2'
	option device 'radio1'
	option mode 'ap'
	option ssid 'AirDisk1-IoT-24'
	option encryption 'psk2'
	option key 'REDACTED'
	option network 'lan_IoT'
	option disassoc_low_ack '0'

root@AirDisk2:~# cat /etc/config/dhcp

config dnsmasq
	option localise_queries '1'
	option rebind_protection '1'
	option rebind_localhost '1'
	option local '/lan/'
	option domain 'local'
	option expandhosts '1'
	option cachesize '1000'
	option readethers '1'
	option leasefile '/tmp/dhcp.leases'
	option resolvfile '/tmp/resolv.conf.d/resolv.conf.auto'
	option localservice '1'
	option ednspacket_max '1232'
	option addmac '1'
	option logqueries '1'
	option logfacility 'DAEMON'
	option boguspriv '0'
	list server '/*.168.192.in-addr.arpa/192.168.11.2'
	list server '/*.168.192.in-addr.arpa/192.168.11.6'
        list address 'REDACTED'
        list address 'REDACTED'
        list address 'REDACTED'
        list address 'REDACTED'
        list address 'REDACTED'
        list address 'REDACTED'

config dhcp 'lan'
	option interface 'lan'
	option start '100'
	option limit '150'
	option leasetime '12h'
	option dhcpv4 'server'
	option dynamicdhcp '0'

config odhcpd 'odhcpd'
	option leasefile '/tmp/odhcpd.leases'
	option leasetrigger '/usr/sbin/odhcpd-update'
	option loglevel '4'
	option piodir '/tmp/odhcpd-piodir'
	option hostsdir '/tmp/hosts'

config dhcp 'lan_IoT'
	option interface 'lan_IoT'
	option start '100'
	option limit '150'
	option leasetime '12h'
	option dhcpv4 'server'
	option ignore '1'
	option dynamicdhcp '0'

root@AirDisk2:~# cat /etc/config/firewall

config defaults
	option input 'ACCEPT'
	option output 'ACCEPT'
	option forward 'ACCEPT'

anon63541380 · March 7, 2026, 11:51pm

Is it imported from non-openwrt or AI-generated?

davygravy · March 8, 2026, 12:49am

Neither. Why do you ask?

Also RE “soft bricked” vs “kernel crash max”, I can say that unplugging/powering down and restarting did not return it to a functional booting state - it was either in a bootloop (blue LED) appearing to attempt to boot, but then rebooting; or with a red LED. It took several resets to get it to boot again.

RE FastTransition/802.11krv, we have 4 or 5 dead spots in our house - for instance, walking from the 4 season porch to the kitchen would invariably result in a dropped call (cell phone) or loss of connectivity (laptop or tablet). I tweaked usteer quite a bit to get it right, but it resulted in one being able to walk anywhere in the house w/o dropping a call on the cell phone. Our house was built in the 60’s, and has had a lot of remodeling/adding done to it, so there are some extra (thick) walls here and there.

psherman · March 8, 2026, 3:13am

This looks very wrong....

davygravy:

config interface 'lan'
	option device 'br-lan'
	option proto 'static'
	option ip6assign '60'
	option gateway '192.168.11.2'
	list dns '192.168.11.2'
	option broadcast '192.168.11.255'
	list ipaddr '192.168.11.8/23'

config interface 'lan_IoT'
	option proto 'static'
	option device 'br-lan'
	option ipaddr '192.168.11.8'
	option gateway '192.168.11.2'
	option netmask '255.255.254.0'
	option broadcast '192.168.11.255'

The fact that you have two network interfaces linked to the same bridge and wit hate same subnet is certainly not helping. I don't know if this is the cause of your core issue, but this is most certainly wrong. The broadcast address is unnecessary to include in the config stanza (it's automatically calculated).

These should be deleted:

It's also rather unusual to have a DHCP server on your AP. Is the DHCP server disabled on the main router?

There are many other issues, but these are two very serious issues that should be addressed.

Therefore, what is the upstream network configuration? And what are your goals?
And also, how did you end up with the current configuration?

anon63541380 · March 8, 2026, 6:51am

First disable kv and temporarily disable usteer
Observe (no) crashes. and try to log them at least via logread -f in ssh session or better forwarding syslog to some eg cctv network storage you have 24x7 on
kv is enabled by usteer on the fly - just start usteer and kv will be back
Observe (no) crashes

davygravy · March 8, 2026, 3:39pm

@anon63541380 & @psherman : I appreciate the feedback. Thank you.

I am traveling a lot right now/undergoing medical stuff, but when I return I’ll dig into this. A few to points to reiterate/clarify:

when the routers both (nearly) simultaneously crashed, I eventually made sure to (1) reset to ensure the config was -default-, without any of my own changes - no previous config.tar.gz uploaded (2) remove wpad-basic-mbedtls, (3) install wpad-{mbedtls | openssl}[I tried both], (4) restart wpad with service wpad restart . It is my recollection that steps 1-4 always resulted in a crashed system (recoverable only by reset). The immediacy/consistency of the crash was so striking that I repeated it over and over… 4 times, I believe.
When I return from my trip/treatments, I will try this again, with serial connection. Both routers are being used right now (w/o FT), but I’ll take one of them out of service (replace w/ a Gb switch) and connect w/ serial. [ I’ve worked on embedded devices for 20 years - Buildroot, etc. To me, serial is the way to go to really peer into a headless device when something is borked. ]
I’m usually pretty methodical, but the “big C” treatments are sometimes leaving me w/ a bit of haze - I did not keep a text copy of the terminal commands. When I return to this, I will post the text of the CLI/terminal commands I use. That, I hope, will either convince you of what I’m saying, or reveal whatever misstep(s) on my part.
@psherman , I set the two adjoining subnets that way, since the 192.168.10.0/24 section is just for IoT devices/HomeAssistant. The other section, 192.168.11.0/24, is for general use (laptops, phones, desktops). My intent was (is!) to truly separate 192.168.10.0/23 into two isolated halves, but I haven’t had a chance to do that yet.
It isn’t a lot of fun I guess, but I now see a greater utility (a need) to go through my /etc/config/* and look for orphan devices/interfaces, and general cruft. I see lines there pertaining to ipv6, for instance, which I don’t use.
@psherman : the option dynamicdhcp '0'is a good catch. Although it isn’t serving any DCHP addresses, it shouldn’t be on. That is fixed now. I think the confusion may have be from the two separate LUCI pages that address this…

image418×334 17.6 KB
image473×473 26.9 KB
I’ve looked over dmesgkernel messages from a fresh boot, and see no error, warning or clues.

anon63541380 · March 8, 2026, 3:56pm

That is more important than gadgets, wake us up when you return to them.

psherman · March 8, 2026, 5:28pm

I agree that your health is more important than any of this... please take care of yourself!

When you are in a reasonable place to tackle the network stuff, let's look at the full topology and configs... the current state is wrong and rather than hacking around, let's fix all the issues and get it into a properly configured state.

davygravy · March 11, 2026, 2:45pm

Back from treatment… looking at the logs. Again, this was working very well in 24.10.5-ish snapshots…

Snippet that shows that the router stayed up for several hours, crashed and rebooted. For context, ZRAM is on, 256MB with vm.swappiness=100 on this run, but the same thing seems to happen w/ swap on default settings and no swap at all.

If this doesn’t show relevant/crucial information you need, please let me know and I’ll do my best to provide it.

2026-03-11T02:31:02-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy1-ap0 sta=50:8b:b9:37:98:50 signal=-50
2026-03-11T02:31:02-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy1-ap0 sta=50:8b:b9:37:98:50 signal=-50
2026-03-11T02:31:02-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy1-ap0 sta=50:8b:b9:37:98:50 signal=-49
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] qcom-q6v5-wcss-pil cd00000.remoteproc: fatal error received:
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] Image Variant : IMAGE_VARIANT_STRING=6018.wlanfw.evalQ
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494]
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] ar_wal_peer.c:2462 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] Thread ID      : 0x00000060  Thread name    : WLAN RT1  Process ID     : 0
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] Register:
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] SP : 0x4bb8d4c8
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] FP : 0x4bb8d4d0
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] PC : 0x4ac8db68
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] SSR : 0x00000008
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] BADVA : 0x00020000
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] LR : 0x4ac8d304
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494]
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] Stack Dump
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] from : 0x4bb8d4c8
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494] to   : 0x4bb8dc58
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.157494]
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.205807] remoteproc remoteproc0: crash detected in cd00000.remoteproc: type fatal error
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.228027] remoteproc remoteproc0: handling crash #1 in cd00000.remoteproc
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.236341] remoteproc remoteproc0: recovering cd00000.remoteproc
2026-03-11T02:31:02-05:00 AirDisk2 kernel: [22272.284308] remoteproc remoteproc0: stopped remote processor cd00000.remoteproc
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.568162] ath11k c000000.wifi: failed to find peer 50:8b:b9:37:98:50 on vdev 2 after creation
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.568222] ath11k c000000.wifi: failed to find peer vdev_id 2 addr 50:8b:b9:37:98:50 in delete
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.575688] ath11k c000000.wifi: failed peer 50:8b:b9:37:98:50 delete vdev_id 2 fallback ret -22
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.577623] remoteproc remoteproc0: remote processor cd00000.remoteproc is now up
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.579071] ath11k c000000.wifi: qmi fail to get qcom,m3-dump-addr, ignore m3 dump mem req
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.579537] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0xff soc_id 0xffffffff
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.579546] ath11k c000000.wifi: fw_version 0x25008f8e fw_build_timestamp 2024-03-01 03:54 fw_build_id WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.584436] ath11k c000000.wifi: Failed to add peer: 50:8b:b9:37:98:50 for VDEV: 2
2026-03-11T02:31:03-05:00 AirDisk2 kernel: [22272.630642] ath11k c000000.wifi: Failed to add station: 50:8b:b9:37:98:50 for VDEV: 2
2026-03-11T02:31:03-05:00 AirDisk2 hostapd: phy1-ap1: STA 50:8b:b9:37:98:50 IEEE 802.11: Could not add STA to kernel driver
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 14 ::1/51894 reply 3.north-america.pool.ntp.org is NODATA-IPv6
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 16 127.0.0.1/51894 reply query is duplicate
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 17 127.0.0.1/38386 query[A] time.apple.com from 127.0.0.1
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 17 127.0.0.1/38386 forwarded time.apple.com to 192.168.11.2
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 18 ::1/38386 query[A] time.apple.com from ::1
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 19 ::1/38386 query[AAAA] time.apple.com from ::1
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 19 ::1/38386 forwarded time.apple.com to 192.168.11.2
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 20 127.0.0.1/38386 query[AAAA] time.apple.com from 127.0.0.1
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 17 127.0.0.1/38386 reply time.apple.com is <CNAME>
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 17 127.0.0.1/38386 reply time.g.aaplimg.com is 17.253.2.43
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 17 127.0.0.1/38386 reply time.g.aaplimg.com is 17.253.2.37
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 17 127.0.0.1/38386 reply time.g.aaplimg.com is 17.253.20.45
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 18 ::1/38386 reply query is duplicate
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 19 ::1/38386 reply time.apple.com is <CNAME>
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 19 ::1/38386 reply time.g.aaplimg.com is 2620:149:a10:4000::31
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 19 ::1/38386 reply time.g.aaplimg.com is 2620:149:a23:4000::1f2
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 19 ::1/38386 reply time.g.aaplimg.com is 2620:149:a23:3000::1e2
2026-03-10T21:43:07-05:00 AirDisk2 dnsmasq[1]: 20 127.0.0.1/38386 reply query is duplicate
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: exiting on receipt of SIGTERM
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: started, version 2.91 cachesize 1000
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: DNS service limited to local subnets
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: compile time options: IPv6 GNU-getopt no-DBus UBus no-i18n no-IDN DHCP no-DHCPv6 no-Lua TFTP no-conntrack no-ipset no-nftset no-auth no-DNSSEC no-ID loop-detect inotify dumpfile
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: UBus support enabled: connected to system bus
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using nameserver 192.168.11.2#53 for domain *.168.192.in-addr.arpa
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using nameserver 192.168.11.6#53 for domain *.168.192.in-addr.arpa
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using only locally-known addresses for lan
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: reading /tmp/resolv.conf.d/resolv.conf.auto
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using nameserver 192.168.11.2#53 for domain *.168.192.in-addr.arpa
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using nameserver 192.168.11.6#53 for domain *.168.192.in-addr.arpa
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using nameserver 192.168.11.2#53
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: using only locally-known addresses for lan
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: read /etc/hosts - 12 names
2026-03-11T02:31:31-05:00 AirDisk2 dnsmasq[1]: read /tmp/hosts/dhcp.cfg01411c - 2 names
2026-03-11T02:31:33-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy0-ap0 sta=9e:94:d4:54:f4:06 signal=-46
2026-03-11T02:31:33-05:00 AirDisk2 hostapd: phy0-ap0: STA 9e:94:d4:54:f4:06 IEEE 802.11: authenticated
2026-03-11T02:31:33-05:00 AirDisk2 usteer: usteer event=assoc_req_accept node=hostapd.phy0-ap0 sta=9e:94:d4:54:f4:06 signal=-46
2026-03-11T02:31:33-05:00 AirDisk2 hostapd: phy0-ap0: STA 9e:94:d4:54:f4:06 IEEE 802.11: associated (aid 1)
2026-03-11T02:31:34-05:00 AirDisk2 hostapd: phy0-ap0: AP-STA-CONNECTED 9e:94:d4:54:f4:06 auth_alg=open
2026-03-11T02:31:34-05:00 AirDisk2 hostapd: phy0-ap0: STA 9e:94:d4:54:f4:06 RADIUS: starting accounting session C6E8545F88D6D7E3
2026-03-11T02:31:34-05:00 AirDisk2 hostapd: phy0-ap0: STA 9e:94:d4:54:f4:06 WPA: pairwise key handshake completed (RSN)
2026-03-11T02:31:34-05:00 AirDisk2 hostapd: phy0-ap0: EAPOL-4WAY-HS-COMPLETED 9e:94:d4:54:f4:06
2026-03-11T02:31:37-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy1-ap0 sta=50:8b:b9:37:98:50 signal=-49
2026-03-11T02:31:37-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy1-ap0 sta=50:8b:b9:37:98:50 signal=-49
2026-03-11T02:31:37-05:00 AirDisk2 usteer: usteer event=auth_req_accept node=hostapd.phy1-ap0 sta=50:8b:b9:37:98:50 signal=-49
2026-03-11T02:31:37-05:00 AirDisk2 hostapd: phy1-ap0: STA 50:8b:b9:37:98:50 IEEE 802.11: did not acknowledge authentication response
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] qcom-q6v5-wcss-pil cd00000.remoteproc: fatal error received:
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] QC Image Version: QC_IMAGE_VERSION_STRING=WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] Image Variant : IMAGE_VARIANT_STRING=6018.wlanfw.evalQ
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698]
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] ar_wal_peer.c:2462 Assertion is_graceful_to_handle failedparam0 :zero, param1 :zero, param2 :zero.
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] Thread ID      : 0x00000060  Thread name    : WLAN RT1  Process ID     : 0
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] Register:
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] SP : 0x4bb8d4c8
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] FP : 0x4bb8d4d0
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] PC : 0x4ac8db68
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] SSR : 0x00000008
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] BADVA : 0x00020000
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] LR : 0x4ac8d304
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698]
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] Stack Dump
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] from : 0x4bb8d4c8
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698] to   : 0x4bb8dc58
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.334698]
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.383185] remoteproc remoteproc0: crash detected in cd00000.remoteproc: type fatal error
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.405250] remoteproc remoteproc0: handling crash #1 in cd00000.remoteproc
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.413570] remoteproc remoteproc0: recovering cd00000.remoteproc
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.461525] remoteproc remoteproc0: stopped remote processor cd00000.remoteproc
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.702717] ath11k c000000.wifi: failed to find peer 50:8b:b9:37:98:50 on vdev 2 after creation
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.702773] ath11k c000000.wifi: failed to find peer vdev_id 2 addr 50:8b:b9:37:98:50 in delete
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.710250] ath11k c000000.wifi: failed peer 50:8b:b9:37:98:50 delete vdev_id 2 fallback ret -22
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.718942] ath11k c000000.wifi: Failed to add peer: 50:8b:b9:37:98:50 for VDEV: 2
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.728027] ath11k c000000.wifi: Failed to add station: 50:8b:b9:37:98:50 for VDEV: 2
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.735497] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
2026-03-11T02:31:37-05:00 AirDisk2 hostapd: phy1-ap1: STA 50:8b:b9:37:98:50 IEEE 802.11: Could not add STA to kernel driver
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.743262] ath11k c000000.wifi: failed to send pdev bss chan info request
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.751095] ath11k c000000.wifi: failed to send WMI_PDEV_BSS_CHAN_INFO_REQUEST cmd
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.754740] remoteproc remoteproc0: remote processor cd00000.remoteproc is now up
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.757588] ath11k c000000.wifi: failed to send pdev bss chan info request
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.772695] ath11k c000000.wifi: qmi fail to get qcom,m3-dump-addr, ignore m3 dump mem req
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.779895] ath11k c000000.wifi: chip_id 0x0 chip_family 0x4 board_id 0xff soc_id 0xffffffff
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.787690] ath11k c000000.wifi: fw_version 0x25008f8e fw_build_timestamp 2024-03-01 03:54 fw_build_id WLAN.HK.2.5.0.1-03982-QCAHKSWPL_SILICONZ-3
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.832621] Unable to handle kernel read from unreadable memory at virtual address 0000000000000000
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.832673] Mem abort info:
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.840510]   ESR = 0x0000000096000005
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.843495]   EC = 0x25: DABT (current EL), IL = 32 bits
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.847101]   SET = 0, FnV = 0
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.852596]   EA = 0, S1PTW = 0
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.855421]   FSC = 0x05: level 1 translation fault
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.858460] Data abort info:
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.863328]   ISV = 0, ISS = 0x00000005, ISS2 = 0x00000000
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.866452]   CM = 0, WnR = 0, TnD = 0, TagAccess = 0
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.871743]   GCS = 0, Overlay = 0, DirtyBit = 0, Xs = 0
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.876865] user pgtable: 4k pages, 39-bit VAs, pgdp=00000000512bd000
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.882239] [0000000000000000] pgd=0000000000000000, p4d=0000000000000000, pud=0000000000000000
2026-03-11T02:31:37-05:00 AirDisk2 kernel: [   26.888592] Internal error: Oops: 0000000096000005 [#1] SMP

davygravy · March 11, 2026, 8:52pm

I’m wondering if this is related to the Packet Steering or SMP scripts. I’ve disabled PS to see if there is a change in the behavior.

psherman · March 11, 2026, 9:21pm

Glad that you're back from treatment. I'd imagine that it's quite punishing on your system, so please continue to take care of yourself.

Meanwhile, I still think that we should address the fundamental network configuration issues that I commented about earlier. It may or may not resolve the issue you're chasing down, but it is important nonetheless.

anon63541380 · March 11, 2026, 9:32pm

In parallel...

For crashing wifi firmware - didable kv (in config and usteer), wait, enable it but disable R, wait. Enable kb by starting usteer, both kombos of 11r.
If one is vulprit we can still vary wifi firmware a bit, before disabling kv or r

davygravy · March 12, 2026, 8:40pm

OK, I believe that I’ve found and corrected the (a) cause of the reboot(s).
After asking around and doing some digging, it seems that the likely culprit is a poor interaction between qca_nss_dp and PS (software Packet Steering) in Openwrt. What I found:

the qca_nss_dp and qca_ssdk modules are more stubs/placeholders than actual drivers. The intent is to replace them w/ a proper (set of) driver(s). https://github.com/openwrt/openwrt/pull/22381 shows some progress, but it may be a while.
the PS binary in Openwrt, while not a bludgeon, it was described to me as something quite a bit less precise than a sharp knife. It may throw interrupts in an incorrect manner. Overall, across platforms/different equipment, it may work quite well, or it may work less well, or it may cause problems.
since disabling PS (Interfaces>Global Network Options), my router/bridged AP has worked as expected, even under high load. Kernel messages showing problems have stopped, and uSteer/802.11rkv is working very well.
transfer speeds have not been reduced (to the extent that I can check).