Date: Fri, 26 Aug 2016 20:56:53 +0000 From: bugzilla-noreply@freebsd.org To: freebsd-arm@FreeBSD.org Subject: [Bug 212185] The aarch64 EFI loader does not get/set the EFI clock Message-ID: <bug-212185-7@https.bugs.freebsd.org/bugzilla/>
next in thread | raw e-mail | index | archive | help
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=3D212185 Bug ID: 212185 Summary: The aarch64 EFI loader does not get/set the EFI clock Product: Base System Version: 11.0-RC1 Hardware: Any OS: Any Status: New Severity: Affects Many People Priority: --- Component: arm Assignee: freebsd-arm@FreeBSD.org Reporter: peter@FreeBSD.org If you boot an aarch64 machine on real hardware, you are greeted with: warning: no time-of-day clock registered, system time will not be set accurately After reading the code, it appears that the EFI runtime services get/set cl= ock calls are not used. For reference, there is an implementation in the stable/10/sys/ia64/ia64/ef= i.c although it is a little strange in that it attaches to the ia64 nexus drive= r.=20 See efi_get_time() / efi_set_time() and the nexus clock driver. The impact of this is that aarch64 machines boot up on Jan 1st, 1970 and are unable to do dnssec validation. This affects ntp.conf if you have dns name= s in there. --=20 You are receiving this mail because: You are the assignee for the bug.=
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-212185-7>