Ipq806x NSS build (Netgear R7800 / TP-Link C2600 / Linksys EA8500)

ACwifidude · 2021-06-24T03:32:31.461Z

NSS builds seem to be sensitive to high UDP traffic. If you are running BitTorrent or similar heavy program that can cause some stability issues.

Otherwise the CPU settings are different. You might do better with 600mhz for your min frequency plus 35 for your up threshold or using the performance CPU governor.

This is the current CPU tweaks:

github.com/ACwifidude/openwrt

set min scaling frequency to avoid ramp-up problems

committed 05:00PM - 24 Apr 21 UTC

ricsc

+8 -0

asturel · 2021-06-24T07:25:47.612Z

Bittorrent is limited to TCP only, forgot to mention that I have:
echo performance > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor; echo performance > /sys/devices/system/cpu/cpufreq/policy1/scaling_governor
in rc.local, nothing changed on my side since build 20210118 which was stable for months.

ACwifidude · 2021-06-24T12:04:47.012Z

The 20210618 is much better - has a major bug fix for wifi.

Only minor tweaks to the NSS patches about once a month have been done to keep compatible with big changes to master.

If crashes become a regular thing - see if you can get a crash log or try the 21.02 branch to see if a master commit in the last several months is the culprit.

jack338c · 2021-06-24T13:45:16.572Z

@Ansuel
hello please have a look,I build newest openwrt master from offical and get a lot of error log from my ea7500 v1 ,thanks

#Kernel Log
[ 1714.133557] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.283688] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.283746] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.378229] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.378265] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.418357] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.418394] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.477693] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.477743] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.488503] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.489478] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.501890] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.502399] cpufreq: __target_index: Failed to change cpu frequency: -5
[ 1714.523023] krait-cache soc:l2-cache: Failed to enable regulator: -5
[ 1714.523075] cpufreq: __target_index: Failed to change cpu frequency: -5

#system log
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.404432] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.404488] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.430291] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.430327] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.447511] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.447565] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.472322] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.472378] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.489832] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.489889] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.501268] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.501610] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.521556] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.521612] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.551539] krait-cache soc:l2-cache: Failed to enable regulator: -5
Thu Jun 24 13:42:39 2021 kern.err kernel: [ 1755.551575] cpufreq: __target_index: Failed to change cpu frequency: -5
Thu Jun 24 13:42:39 2021 kern.warn kernel: [ 1755.580371] krait-cache soc:l2-cache: Failed to enable regulator: -5

Ansuel · 2021-06-24T13:57:17.862Z

there is definitely a problem in the dts

jack338c · 2021-06-24T14:14:19.264Z

maybe it's my build problem
I just downlaod an ea7500 v1 firmware from https://downloads.openwrt.org/snapshots/targets/ipq806x/generic/openwrt-ipq806x-generic-linksys_ea7500-v1-squashfs-sysupgrade.bin
and get no above logs .no issue
I'm sorry for troubles

jack338c · 2021-06-25T02:21:54.525Z

I find the reason is cpu locked,because too hot

RelentlesS · 2021-06-25T06:10:36.088Z

Hi all,

I just started using this build (R7800-20210620-Stable2012NSS-ath10k-factory.img)

Can someone tell me if this is needed / recommended to use with this build?

github.com/openwrt/openwrt

ipq806x: improve system latency

openwrt:master ← Ansuel:ipq806x-cpufreq

opened 01:40AM - 28 Mar 21 UTC

Ansuel

+17 -0

Various report and data show that the freq 384000 is too low and cause some extr…a latency to the entire system. OEM qsdk code also set the min frequency for this target to 800 mhz. Also some user notice some instability with this idle frequency, solved by setting the min frequency to 600mhz. Fix all these kind of problem by introducing a boot init.d script that set the min frequency to 600mhz and set the ondemand governor to be more aggressive. The script set these value only if the ondemand governor is detected. 384 mhz freq is still available and user can decide to restore the old behavior by disabling this script. @hnyman Signed-off-by: Ansuel Smith <ansuelsmth@gmail.com>

xeonpj · 2021-06-25T06:22:10.178Z

the UDP problem seems to persist. I put the torrent chart back exclusively by tcp and I keep testing

ACwifidude · 2021-06-25T12:13:04.995Z

That commit is included in both 21.02 and master. I took it a step further and made the speed 800mhz with 20% utilization being the up threshold.

github.com/ACwifidude/openwrt

set min scaling frequency to avoid ramp-up problems

committed 05:00PM - 24 Apr 21 UTC

ricsc

+8 -0

Having the CPU appropriately ramp up when under load ensures maximum performance.

kesagatame · 2021-06-26T09:09:07.370Z

Does this mean that both 0620 builds no longer need the custom entries in startup? I.E. mine are:

echo ondemand > /sys/devices/system/cpu/cpufreq/policy0/scaling_governor
echo ondemand > /sys/devices/system/cpu/cpufreq/policy1/scaling_governor
echo 800000 > /sys/devices/system/cpu/cpufreq/policy0/scaling_min_freq
echo 800000 > /sys/devices/system/cpu/cpufreq/policy1/scaling_min_freq
echo 75 > /sys/devices/system/cpu/cpufreq/ondemand/up_threshold
echo 10 > /sys/devices/system/cpu/cpufreq/ondemand/sampling_down_factor

ACwifidude · 2021-06-26T12:41:59.696Z

If you put those entries it’ll replace my commit’s settings (because it happens later in the boot process).

Having settings in your startup script is not needed unless you want particular settings. I’ve found these setting work great.

Ansuel · 2021-06-26T13:01:40.998Z

Hi can some do a quick test for me?

You need to remove the ecm module (winscp and remove the ecm.ko from lib/module and reboot) and give me some nss stats for the ipv4 submodule after some random traffic (if you can no wifi but ethernet traffic)

cat /sys/kernel/debug/qca-nss-drv/stats/ipv4

facboy · 2021-06-26T19:27:49.686Z

it doesn't, because your changes are in bootcount which is one of the very last things run, (after rc.local).

D43m0n · 2021-06-27T08:59:56.170Z

That’s good to know, if anyone wants to alter the builds default settings (for whatever reason) and is wondering why things don’t work as expected after a reboot

nashford · 2021-06-27T11:17:45.618Z

I am about to test this now (sorry for the delay, i travelled) but i was thinking, can i install ANY package using diffconfig , if so can i not just install MDADM to it ? i was building the KMODS i need for MDADM and then MDADM wont install etc. is the diffconfig able to do software packages as well ? I assume so..... ? if so is there some syntax i need to know?

ACwifidude · 2021-06-27T12:06:26.123Z

You can install any / all software packages with diffconfig. Just use the same syntax.

@facboy thanks for the catch

nashford · 2021-06-27T12:21:51.016Z

ACwifidude:

any / all software packages with diffconfig. Just u

So, i tried this now and i am wondering if a rebase is my issue - the packages on your master after i rebase install as 5.4.128 and the kernel is 5.4.124 - think this is the root of my issue as packages build with whats in the openwrt repo it seems - any idea ? how can i mitigate this and build at your version ?

ACwifidude · 2021-06-27T13:30:46.545Z

If you don’t rebase you’ll build with the kernel (and the packages) from the build.

I’d skip the rebase if you are trying to get max compatibility.

nashford · 2021-06-27T16:01:55.000Z

Okay, will try, How would I build just one package at a time if I keep your repo? I don't want to recompile each time I need a module etc. Also, to that point, perhaps we can expand your diffconfig to have everything needed package wise but not installed during compile time ? Is it possible to build most or all of the kmods out separate to the build with the SE code then we can repoint opkg kmods in the config file to that location in your builds ?