mirror of
https://github.com/systemd/systemd-stable.git
synced 2025-01-26 10:03:40 +03:00
dde5c821bf
sd-boot uses rdtsc to set those timestamps. There is no guarantee that the tsc has any particular absolute value. On my VM: $ head /sys/firmware/efi/efivars/LoaderTime* ==> /sys/firmware/efi/efivars/LoaderTimeExecUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f <== 4397904074 ==> /sys/firmware/efi/efivars/LoaderTimeInitUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f <== 4396386839 ==> /sys/firmware/efi/efivars/LoaderTimeMenuUSec-4a67b082-0a4c-41cf-b6c7-440b29bb8c4f <== 4396392521 $ build/test-boot-timestamps ... LoaderTimeExecUSec=4396386839 too large, refusing. Failed to read EFI loader data: Input/output error Assertion 'q >= 0' failed at src/test/test-boot-timestamps.c:84, function main(). Aborting. (with patch) $ build/test-boot-timestamps ... EFI Loader: start=1h 13min 16.386s exit=1h 13min 17.904s duration=1.517s Firmware began 1h 13min 17.904074s before kernel. Loader began 1.517235s before kernel. Firmware began Tue 2020-05-26 11:04:13 CEST. Loader began Tue 2020-05-26 12:17:30 CEST. Kernel began Tue 2020-05-26 12:17:31 CEST.
System and Service Manager
Details
General information about systemd can be found in the systemd Wiki.
Information about build requirements is provided in the README file.
Consult our NEWS file for information about what's new in the most recent systemd versions.
Please see the Hacking guide for information on how to hack on systemd and test your modifications.
Please see our Contribution Guidelines for more information about filing GitHub Issues and posting GitHub Pull Requests.
When preparing patches for systemd, please follow our Coding Style Guidelines.
If you are looking for support, please contact our mailing list or join our IRC channel.
Stable branches with backported patches are available in the stable repo.