Kalin

Same here, running stable for 8 days. Before the patch, usually 1 or 2 days.

I am having clock issue with kernels 5.0.5 and 5.0.7, where "Allwinner erratum UNKNOWN1" is active. Here are some additional observations: 1) It only affects system time. Hardware clock (sudo hwclock) is still correct. 2) Trying to execute "sudo hwclock -s", returns error for invalid argument 3) After reboot "sudo hwclock -s" works and system time is updated. 4) A reboot soon after "sudo hwclock -s" results in the wrong system time being back right away. 5) If I wait for a 1-2 minutes after setting the correct system time, the reboot does not break the time

Thanks, this was indeed missing in dmesg output. I switched to latest kernel 5.0.7, where this is again active.

I am experiencing the issue with 5.0.6. kernel. Here are some details: + uname -a Linux pine1 5.0.6-sunxi64 #5.78.190407 SMP Mon Apr 8 00:11:35 CEST 2019 aarch64 aarch64 aarch64 GNU/Linux + grep ERRATUM /boot/config-5.0.6-sunxi64 CONFIG_ARM64_ERRATUM_826319=y CONFIG_ARM64_ERRATUM_827319=y CONFIG_ARM64_ERRATUM_824069=y CONFIG_ARM64_ERRATUM_819472=y # CONFIG_ARM64_ERRATUM_832075 is not set CONFIG_ARM64_ERRATUM_845719=y CONFIG_ARM64_ERRATUM_843419=y CONFIG_ARM64_ERRATUM_1024718=y CONFIG_ARM64_ERRATUM_1188873=y CONFIG_ARM64_ERRATUM_1165522=y CONFIG_ARM64_ERRATUM_1286807=y # CONFIG_CAVIUM_ERRAT

Sharing some detailed explanation, available here https://lore.kernel.org/patchwork/patch/1031565/

I read somewhere that changing system time with a big difference is rejected by kernel, because it "will take too long". I have a question - are you saying that the 95 year jump happens at the place where hwclock looks or it is just in the " linux system time"? I have been running an older kernel (3.x) for few weeks and did not encounter this issue. The kernel I used has certain patches related to time, that are visible here: https://github.com/ayufan-pine64/linux-pine64/tree/my-hacks-1.2-with-drm/kernel/time I am not sure how to tell if these patches are in the armbian kerne

Sure, here is the result grep ERRATUM /boot/config* CONFIG_ARM64_ERRATUM_826319=y CONFIG_ARM64_ERRATUM_827319=y CONFIG_ARM64_ERRATUM_824069=y CONFIG_ARM64_ERRATUM_819472=y # CONFIG_ARM64_ERRATUM_832075 is not set CONFIG_ARM64_ERRATUM_845719=y CONFIG_ARM64_ERRATUM_843419=y CONFIG_ARM64_ERRATUM_1024718=y # CONFIG_CAVIUM_ERRATUM_22375 is not set CONFIG_CAVIUM_ERRATUM_23144=y # CONFIG_CAVIUM_ERRATUM_23154 is not set # CONFIG_CAVIUM_ERRATUM_27456 is not set # CONFIG_CAVIUM_ERRATUM_30115 is not set # CONFIG_QCOM_FALKOR_ERRATUM_1003 is not set # CONFIG_QCOM_FALKOR_ERRATUM_1009 is not set #

I am experiencing the same issue on sopine 64 with quite recent kernel: 4.19.20-sunxi64