New answers tagged

1

I have figured out the culprit. Doing cat /proc/acpi/wakeup, and disabling the *enabled devices one by one (using, e.g., sudo echo 'DEVABBRV' > /proc/acpi/wakeup, where DEVABBRV is the device abbreviation listed in the cat output above), it turns out that LID0 is waking up the machine "prematurely". This is perhaps due to some non-standard, proprietary ...


0

I made one measurement of clock_gettime resolution with : struct timespec now; struct timespec resolution; clock_gettime(CLOCK_MONOTONIC, &now); clock_getres(CLOCK_MONOTONIC, &resolution); printf("secs %d nanoseconds %d\n",resolution.tv_sec, resolution.tv_nsec); The result is: lacrosse@lacrosse-ThinkStation-S10:~/Debug$ ./a....


4

There are two things you should do. Make sure ntpd is started as early as possible in the boot sequence, and put an ntp-wait somewhere in the boot sequence before any of your applications start. Depending on your version of Linux, how you achieve that will vary. You should, however, make your application startup dependant on the ntp-wait finishing. ntp-...



Top 50 recent answers are included