BipBip1981

Hi, To my side, i have a stable system: bulleye trunk build from source with armbian-dev-tools with 5.15.26 Kernel and 400MHZ-1400MHZ schedutil. Have a good day.

Hi, Thks for your patch, i think it's more "clean" than my "Kiss workaround" Have a good day

Hello, yes, -> Welcome to Armbian 21.08.6 Hirsute with bleeding edge Linux 5.15.5-rockchip64

Hello, My workaround or patch, maybe it bad, sad or unclear but it's KISS and seem to work ! Bye root@helios64:~# cat /etc/fancontrol # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 #FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input FCTEMPS=/dev/fan-p6/pwm1=/sys/class/thermal/thermal_zone0/temp /dev/fan-p7/pwm1=/sys/class/thermal/thermal_zone0/temp MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110 MINSTART=/dev/fan-p6/pwm1=60 /dev/fan-p7/pwm1=60 MINSTOP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MINPWM=20

Hello, My workaround or patch, maybe it bad, sad or unclear but it's KISS and seem to work ! Bye root@helios64:~# cat /etc/fancontrol # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 #FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input FCTEMPS=/dev/fan-p6/pwm1=/sys/class/thermal/thermal_zone0/temp /dev/fan-p7/pwm1=/sys/class/thermal/thermal_zone0/temp MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110 MINSTART=/dev/fan-p6/pwm1=60 /dev/fan-p7/pwm1=60 MINSTOP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MINPWM=20

Hello, My workaround or patch, maybe it bad, sad or unclear but it's KISS and seem to work ! Bye root@helios64:~# cat /etc/fancontrol # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 #FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input FCTEMPS=/dev/fan-p6/pwm1=/sys/class/thermal/thermal_zone0/temp /dev/fan-p7/pwm1=/sys/class/thermal/thermal_zone0/temp MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110 MINSTART=/dev/fan-p6/pwm1=60 /dev/fan-p7/pwm1=60 MINSTOP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MINPWM=20

Hello, My workaround or patch, maybe it bad, sad or unclear but it's KISS and seem to work ! Bye root@helios64:~# cat /etc/fancontrol # Helios64 PWM Fan Control Configuration # Temp source : /dev/thermal-cpu INTERVAL=10 #FCTEMPS=/dev/fan-p6/pwm1=/dev/thermal-cpu/temp1_input /dev/fan-p7/pwm1=/dev/thermal-cpu/temp1_input FCTEMPS=/dev/fan-p6/pwm1=/sys/class/thermal/thermal_zone0/temp /dev/fan-p7/pwm1=/sys/class/thermal/thermal_zone0/temp MINTEMP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MAXTEMP=/dev/fan-p6/pwm1=110 /dev/fan-p7/pwm1=110 MINSTART=/dev/fan-p6/pwm1=60 /dev/fan-p7/pwm1=60 MINSTOP=/dev/fan-p6/pwm1=40 /dev/fan-p7/pwm1=40 MINPWM=20

Hi, I have same problem with WD Red 8to (WDC WD80EFBX-68AZZN0). In slot 3 Depend of drive, some are more or less sensible Best configuration without or (with less) error (i test again...) is: slot 1: WDC WD80EFAX-68KNBN0 slot 2: WDC WD80EFAX-68KNBN0 slot 3: TS256GSSD370S slot 4: WDC WD80EFBX-68AZZN0 slot 5: WDC WD80EFBX-68AZZN0 harddrive in slot 5 was in slot 3 before and i had: 199 UDMA_CRC_Error_Count 0x000a 200 200 000 Old_age Always - 11 in: Error 11 occurred at disk power-on lifetime: 46 hours (1 days + 22 hours) Bye.

Hi, i use Armbian Bullseye.

Hi, I try "on demand" 400-1400Mhz this week-end, seem stable. I will waiting one week... Next i try 400-1800Mhz. I do all my previous test with "Conservative" on governor, maybe "on demand" is the key of stability. Have a good day

Hi, Seem stable after one year of multiple testing with this settings: - Last Kernel Linux 5.10.63-rockchip64 but in logs i have a regulator voltage error.. (with Linux 5.10.43-rockchip64, not this issue..) - Max/Min CPU Freq 1,2GHz & Governor to Performance (advise here and i think it the best advise i never see... https://wiki.debian.org/InstallingDebianOn/Kobol/Helios64) With another setting like this it's simple: - Totaly instable randomly: Kernel Panic, lost network Freeze... (with docker container, ramdomly crash is daily...) After many reading, i think Rockchip and Linux Kernel have a big problem with Governor and CPU Frequency Management I am not a Guru and maybe i write bigs errors or sh.. Have a good day

Hello, Same issu: emmc mounted readonly, mmc2: running CQE recovery ... with Buster or Bulleye and kernel 5.10.60-rockchip64. ext4 on emmc pass to read-only after lot of I/O error and Helios become unusable. Downgrade to Armbian 21.05.8 Buster with Linux 5.10.43-rockchip64 and all is Okok, no I/O error on emmc.