Issues running ntpsec on kirkstone #561
Comments
|
So, I found my own answer. The issue apparently come from building with seccomp enabled. This seems to be a know bug with glibc. One quick fix is to disable seccomp, but probably a better patch is needed |
|
Usually this just means some syscall is filtered |
bluca
pushed a commit
to bluca/meta-openembedded
that referenced
this issue
May 23, 2022
Changelog: ===================== HA Lovelace controller: Prevent sending connect message twice (openembedded#559) Bump black from 21.11b0 to 21.11b1 (openembedded#562) Catch zeroconf errors (openembedded#564) Bump black from 21.10b0 to 21.11b0 (openembedded#561) Signed-off-by: Wang Mingyu <[email protected]> Signed-off-by: Khem Raj <[email protected]> Signed-off-by: Trevor Gamblin <[email protected]>
kraj
pushed a commit
to YoeDistro/meta-openembedded
that referenced
this issue
May 25, 2023
Changelog: ========== general: add hid_get_report_descriptor API function (openembedded#451) macOS: fix retrieving USB Interface number on macOS 13.3 (openembedded#534) macOS: Properly handle the close of run loop on macOS (openembedded#522) libusb: fix crash in hid_enumerate() caused by a stale device handle (openembedded#526) windows: alternative way to get USB Serial Number if not provided by HidD_GetSerialNumberString (openembedded#464) windows: don't mark with dllexport in static build (openembedded#507/openembedded#515) windows: Get Bluetooth device Model Number String instead of Device Name into product string (openembedded#500) general: fixes (mostly error handling) of issues found by Coverity Scan (openembedded#552/openembedded#554/openembedded#555/openembedded#559/openembedded#560/openembedded#561) general: variouse fixes and improvements Signed-off-by: Wang Mingyu <[email protected]> Signed-off-by: Khem Raj <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi,
seems to be that the ntpsec meta layer builds fine but does not run as expected. Once the process is started, even in command line, ntpd hangs right after locking in RAM and never proceeds.
root@cyclone5:~# ntpd -d 5 -D 5 -n2022-04-04T16:16:22 ntpd[467]: INIT: ntpd ntpsec-1.2.1: Starting2022-04-04T16:16:22 ntpd[467]: INIT: Command line: ntpd -d 9 -D 9 -n2022-04-04T16:16:22 ntpd[467]: INIT: precision = 2.050 usec (-19)2022-04-04T16:16:22 ntpd[467]: INIT: successfully locked into RAMI am working on a de0-nano-soc fpga, but that seems not to be the issue. All other features seem to be building fine.
Any idea?
The text was updated successfully, but these errors were encountered: