I've seen it as well, and seems to affect kernel 6.6. Linus posted a similar issue on Linux mailing list. My workaround was to edit fs.mk and explicitly disable all the PSTORE_*COMPRESSION options.
The data is essentially garbage, and can be rm manually for now.
Seeing that it's a 5MB file I can already tell NSS acceleration is working. A long with the nss_stats output, everything looks to be working.
Is your ping issue recent or did you have a working NSS build with low ping?
SQM is only meant to prevent latency spikes when there's heavy usage on your network. If your problem exists on stock firmware, or when there's little to no traffic on your network, then you'll need to call up your ISP.
oh, thanks for the quick answer and the hint.. Do you have some more insights or documentation how qca-nss-wifi-meshmgr and mesh11sd are used or configured? I guess then I can build my own install from the normal snapshot..
what is the error you are getting ? looking at your github actions log it seems to be related with failed downloads (like binutils). I am using fedora or/and archlinux with no issues
On the contrary, I found a BIG improvment in WiFi speed in IPQ6018 with recent update. The community test JDC AX1800-Pro (ath11k ahb), 800Mb for 6.6.35 while 940Mb for 6.6.36. It is super stable. Also, a big improvment in JDC AX6600 QCN9024 (ath11k pci) . The people are still wondering what is the "black magic"? .
I have a 2Gb Internet (2000Mb DL, 100Mb UL), here is AX6600 QCN9024 80MHz test(1297 DL and 114 UL):
i did A/B test multiple times between 6.6.35 and 6.6.36 keeping wifi parameters constant.
.35 is able to sustain peak throughput
.36 is able to reach the same peak throughput but cannot sustain and fluctuates.
same for both ul and dl.
test done on iperf3 between apple wifi clients and hosts on lan.
to be fair 6.6.35 is the best wifi performance i have seen in the ax3600 on the nss bandwagon.
going back to 6.6.35 for now as it was perfectly stable and performant for a week plus until i have time to catch up to AQL (disable/tweak it)
Does anyone have issues with IPTV multicast traffic? I can't get it to work on my AX3600 with NSS builds. Same config works fine on stock builds.
Using igmpproxy with stb connected directly to router via ethernet. Upon switching channels I get about a second or two of video before it freezes, with fragments of audio making it through every now and then after that.
Using tcpdump and gstreamer I can extract a working ts stream from wan port, but a severely corrupted one from lan port where stb is connected. Comparing dumps from both sides there is about a 10% drop in amount of traffic on lan side after a few seconds. Trying to match packets in wireshark, I see missing packets on lan side, followed by errors like: [Detected 6 missing TS frames before this (last_cc:6 total skips:22974 discontinuity:4485)].
Current results are from a custom build using JuliusBairaktaris's builder with some extra packages but otherwise default config. I have had the same issue every time I tried NSS builds over the last 2 months, using various builds.
If anyone has any ideas or suggestions on how to better narrow down this issue I would appreciate it.
conf dump
root@OpenWrt:/etc/config# cat nss
config nss 'general'
option enable_rps '1'
option enable_log '1'
root@OpenWrt:/etc/config# cat pbuf
config general 'opt'
option auto_scale 'off'
option memory_profile '1gb'
root@OpenWrt:/etc/config# cat ecm
config ecm 'global'
option acceleration_engine 'auto'
config ecm 'general'
option enable_bridge_filtering '0'
option disable_offloads '0'
option disable_flow_control '0'
option disable_interrupt_moderation '0'
option disable_gro '0'
root@OpenWrt:/etc/config# cat network
config interface 'loopback'
option device 'lo'
option proto 'static'
option ipaddr '127.0.0.1'
option netmask '255.0.0.0'
config globals 'globals'
option ula_prefix 'fd10:ae21:321::/48'
option packet_steering '0'
config device
option name 'br-lan'
option type 'bridge'
list ports 'lan1'
list ports 'lan2'
list ports 'lan3'
option igmp_snooping '1'
option multicast_querier '1'
config interface 'lan'
option device 'br-lan'
option proto 'static'
option ipaddr '10.0.0.1'
option netmask '255.255.0.0'
option ip6assign '60'
option ipv6 '0'
option delegate '0'
config interface 'wan'
option device 'wan'
option proto 'dhcp'
option ipv6 '0'
option peerdns '0'
list dns '1.1.1.1'
list dns '1.0.0.1'
config interface 'wan6'
option device 'wan'
option proto 'dhcpv6'
option peerdns '0'
list dns '2606:4700:4700::1111'
list dns '2606:4700:4700::1001'
root@OpenWrt:/etc/config# cat pbuf
config general 'opt'
option auto_scale 'off'
option memory_profile '1gb'
root@OpenWrt:/etc/config# cat igmpproxy
config igmpproxy
option quickleave 1
# option verbose [0-3](none, minimal[default], more, maximum)
config phyint
option network wan
option zone wan
option direction upstream
list altnet 0.0.0.0/0
config phyint
option network lan
option zone lan
option direction downstream
. The people are still wondering what is the "black magic"? 
.
