Seneca

I've tried to provoke a system freeze with high cpu and IO, but it seems stable for now.
20:05:49 up 4 days, 23:47, 1 user, load average: 0,14, 0,15, 0,11 I'll update this thread if the issue reoccurs.

Just an update from yesterday, no freezes or crashes yet, even though quite heavy IO and CPU.

I did a dist-upgrade yesterday, and I've had two freezes since then due to high IO (probably). But I've reverted the cpufreq tweaks now (ondemand+min/max 400000/1800000), and I never enabled he vdd tweaks in boot.cmd, so there wasn't anything to revert. So we'll see how it goes, I'll try to put a lot of IO load on it the coming days.
5.10.21-rockchip64 #21.02.3 SMP PREEMPT Mon Mar 8 01:05:08 UTC 2021 aarch64 aarch64 aarch64 GNU/Linux  

I seem to have freezes as well. I stayed on the recommended release with zero updates from the default installation. I'm running Sonarr, Radarr, Jackett, Transmission, Samba, NFS server and Zram swap.
 
Linux muzzy 5.8.14-rockchip64 #20.08.10 SMP PREEMPT Tue Oct 13 16:58:01 CEST 2020 aarch64 aarch64 aarch64 GNU/Linux I've also changed the cpufreq config to avoid issues. Locked at 1,2ghz min/max, performance govenor.
It seems like when I do a lot of I/O and put a high load on the cpu, the system just freezes. There's nothing in the syslog but I haven't looked in the serial console.
I'm only running SSD's in this machine, so there's no shortage of bandwidth on the drives. If there's no load, I haven't had one freeze at all. Medium load doesn't seem to be an issue either.
Has anyone tried adding active cooling on the cpu?
I'm guessing this is the same issue that was posted about on the 27th of October in the blog, why hasn't there been an update on it?
 
And for the mods: how can I remove this forum posting limitation, like one post per week or something?

If anyone is interested, I've created a shell script that can be run with cron to check A/C and battery status, and do a graceful shutdown when a battery threshold is met.  It also logs power outages, battery drain when off A/C, and when it posts a shutdown (if any).  This is a simple script, nothing fancy, but works for me.  It has a granularity of one minute (cron is limited to one minute intervals), but I've been able to keep the system up on heavy load for 4-5 minutes before the script generates a shutdown on low battery.
 
The script is generous -- it waits for 916mV or less before a shut-down.  This value was provided by the KOBOL team on their Wiki as the recommended shutdown threshold for the battery, but can be changed via the script.  You can comment out any file-logging lines, or change the file location, also from within the script.  I've heavily commented it, should be pretty easy to follow.
 
Copy the script below into a file named whatever you choose, place it where you want to run it, and cron it to get it going.  It should only create disk writes when the power is out or when shutting down from battery drain on no A/C (a few lines once per minute), and will create no disk writes  if you comment out the logging.
 
 
Let me know how it works for you, if you use it.  I've been testing it for the past couple of days, and it's worked as intended.  I'm always open to code tips, and I'm still learning, so any advice is appreciated.