Marc_in_the_dark

set the minimum CPU speed to 110400 and maximum speed to 110400. CPU governor = conservative (armbian config > system > CPU). So the processor will not change the CPU clock.

Uptime is now 28 days. Maybe the fixed CPU speed is the solution for this problem. But the longest uptime I ever had was 40 days. I have to break this record first.

The current intermediate status...system is still running and uptime is now 13 days. With stretch sometimes I had an uptime of 40 days. But nothing in comparision with the uptime of my Raspberry systems (it runs for years). keep the fingers cross and hope a fixed CPU speed is the solution for this issue.

Good to know. Now I disabled the CPU powersafe mode by using a fixed CPU speed for minimum and maximum. With Buster, it's seems much easier to reproduce. Today it needed 6h and than it was 1978. Now, I test with a fixed CPU speed.

I made a full upgrade from Stretch to Buster on two OrangePi 2E and got the 1978 problem again after 2 days.

the longest uptime without the 1978 issue was 45 days and the shortest uptime (ended yesterday) was 2 days. I tried so many things but could not solve it yet. The last change (yesterday) was to limit the cpu clockdown. Now it goes down to 800 and up to 1200Mhz in "conservative" mode. I ordered a second OrangePi +2E to make more tests. The second +2E shows the same problem and in the next step I will install the latest armbian image with the newest kernel.

Hello, I found this thread by searching for "orange pi 1978" with Google because I have the same problem here with 2 identical Orange Pi Plus 2E systems. One both systems I installed ARMBIAN 5.73 stable - 4.19.20-sunxi and the problem is reproducible but it takes around 2 weeks till it happens. Both systems running in the same network and do exactly the same (the 2nd is a backup-system) but the problem does not occur on both system at the same time. In the moment, were the problem occur you have limited access to the system. SSH does not work, shutdown or reboot does not work and today I tried to sync the the systemtime with the RTC but it does not work. RTC has the correct time and system date was 7th May 1978. The only solution is to cut the power and connect it again. I use a WLAN-power-socket to do this remote. Do you have any idea what I can try? I thought an external RTC modul could help and sync the time in case of the 1978-problem happens but today I learned the RTC is not the problem (sudo hwclock -r gives the right time) and it's not possible to set the date with sudo hwclock -s when it happens. Thanks for your help!