Linux - KernelThis forum is for all discussion relating to the Linux kernel.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
I am running 2.6.27 kernel on my arm AT91SAM9G20. I am not using ntpd. I sync my kernel time with the reference time and then leave the system for 24 hours. I see that the kernel clock drifts by 8 seconds. Can anyone help me in figuring out the reason behind this. And how to fix this in kernel?
Too my knowledge this cannot be fixed in the kernel.
The time comes from a crystal on the motherboard. These crystals are good enough to show a roughly correct time, but hardly ever good enough to keep perfect time over longer periods. I've seen big differences in the drift that can occur (from a second over a few days to more the 15 seconds in one day).
Syncing your time with a reliable outside source is the only way to go. If you are already syncing once every 24 hours, you might consider changing the config to do it more often. I personally would use ntpd.
Too my knowledge this cannot be fixed in the kernel.
The time comes from a crystal on the motherboard. These crystals are good enough to show a roughly correct time, but hardly ever good enough to keep perfect time over longer periods. I've seen big differences in the drift that can occur (from a second over a few days to more the 15 seconds in one day).
Syncing your time with a reliable outside source is the only way to go. If you are already syncing once every 24 hours, you might consider changing the config to do it more often. I personally would use ntpd.
Hope this helps.
Thanks for the reply.
We have ntpd running on the board. But some of these boards are not connected on network and there we face this drfit issue. Can't we modify in kernel to workaround this issue?
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.