Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

FPGA CI: Fix NTP clock sync, panic-after-softlock, and systemd init order #1277

Merged
merged 3 commits into from
Jan 18, 2024

Conversation

korran
Copy link
Collaborator

@korran korran commented Jan 17, 2024

fpga-image: Synchronize clock via NTP.

GitHub rejects runners with a local clock that varies by more than 15
minutes. Unfortunately, the RTC on the zcu104 boards is terrible,
drifting more than 30 seconds a day.

fpga-image: Run startup script after everything else.

Before this change, systemd hadn't fully initialized when the startup
script was run (as it was blocking continued startup).

fpga-image: Use softlock_panic sysctl correctly.

Previously, we were setting this as if it was a timeout value, but it's
actually just a boolean.

See
https://www.infradead.org/~mchehab/kernel_docs/admin-guide/sysctl/kernel.html#softlockup-panic

Previously, we were setting this as if it was a timeout value, but it's
actually just a boolean.

See
https://www.infradead.org/~mchehab/kernel_docs/admin-guide/sysctl/kernel.html#softlockup-panic
Before this change, systemd hadn't fully initialized when the startup
script was run (as it was blocking continued startup).
GitHub rejects runners with a local clock that varies by more than 15
minutes. Unfortunately, the RTC on the zcu104 boards is terrible,
drifting more than 30 seconds a day.
@korran korran merged commit 73a4c1e into chipsalliance:main Jan 18, 2024
11 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants