port-riscv/58766: ntpd / ntpdate setting time on risc64 fails to work

[he%NetBSD.org@localhost]

>Number:         58766
>Category:       port-riscv
>Synopsis:       ntpd / ntpdate setting time on risc64 fails to work
>Confidential:   no
>Severity:       non-critical
>Priority:       medium
>Responsible:    port-riscv-maintainer
>State:          open
>Class:          sw-bug
>Submitter-Id:   net
>Arrival-Date:   Sun Oct 20 19:00:00 +0000 2024
>Originator:     Havard Eidnes
>Release:        NetBSD 10.99.12
>Organization:
	I try...
>Environment:
System: NetBSD riscv64 10.99.12 NetBSD 10.99.12 (GENERIC64) #0: Sat Sep  7 14:28:19 UTC 2024  mkrepro%mkrepro.NetBSD.org@localhost:/usr/src/sys/arch/riscv/compile/GENERIC64 riscv
Architecture: riscv64
Machine: riscv
>Description:
	I run a riscv64 host inside qemu.  I notice it's running
	with a clock which is slightly "off".  ntpd detects and syncs
	to remote servers:

# ntpq -c pe
     remote           refid      st t when poll reach   delay   offset  jitter
==============================================================================
 2.netbsd.pool.n .POOL.          16 p    -   64    0    0.000   +0.000   0.004
-trf.clearnet.pw 13.51.141.188    3 u   95   64    7   26.129  +397928  85.359
+ntp.coreless.ne 194.58.205.20    2 u   56   64    7   33.504  +397918  66.410
+77-95-79-99.bb. 194.58.203.148   2 u   12   64   37   28.002  +397893 109.001
*62.101.228.30   77.40.226.121    2 u   16   64   37   27.649  +397893 109.144
-169.80-203-110. 77.40.226.121    2 u   42   64    1   26.391  +397893   3.790

	However, ntpd fails to set the time, I get these messages on
	the console:

Oct 20 17:03:34 riscv64 ntpd[2152]: step-systime: Invalid argument

	Stopping ntpd and trying ntpdate to set the date results in

Oct 20 18:36:59 riscv64 ntpdate[713]: step-systime: Invalid argument

	So ... something is "off".
>How-To-Repeat:
	Run a riscv64 host, watch it fail to set the time as above.
>Fix:
	That would be nice...