I decided to dig into this since I was seeing the same issue.
root@string:~# uname -r
root@string:~# dpkg -s linux-image-next-sunxi64
Status: install ok installed
Maintainer: Igor Pecovnik <igor.pecovnik@****l.com>
Description: Linux kernel, version 4.19.20-sunxi64
This package contains the Linux kernel, modules and corresponding other
files, version: 4.19.20-sunxi64.
root@string:~# grep CONFIG_FSL_ERRATUM_A008585 /boot/config-4.19.20-sunxi64
Sat Apr 28 02:43:25 UTC 2114
Local time: Sat 2114-04-28 02:43:30 UTC
Universal time: Sat 2114-04-28 02:43:30 UTC
RTC time: Tue 2019-03-05 22:21:31
Time zone: Etc/UTC (UTC, +0000)
System clock synchronized: no
systemd-timesyncd.service active: no
RTC in local TZ: no
root@string:~# hwclock -s
hwclock: settimeofday() failed: Invalid argument
I decided to do a much more simple test:
I can see that the when date attempts to make the clock_settime syscall, it receives EINVAL back. I'm wondering then why it sees CLOCK_REALTIME as invalid. I could potentially see an issue with CLOCK_REALTIME_COARSE which man 2 CLOCK_GETRES says is "architecture specific", but this one is throwing me of.