Marc Muehlfeld wrote: > Martin Burnicki schrieb: >> This seems to indicate that the new kernel implements the system clock >> based on a different timer API than the old kernel. That new timer API >> may not support the particular chipset on your mainboard correctly. > > Would it be a solution to run the ntp server on a different machine with > different chipset and let the current one just be a ntp client. And the > ntp drift technique could get to come to grips with it and it will run > fine in future?
I'm afraid that would not solve the problem. Every NTP node is primarily a NTP client which gets its time from an upstream time source, which can be another NTP server, a radio clock or GPS receiver, or whatever. Using that time source it disciplines its own system time, which can then be made available to other NTP nodes on the network. Martin -- Martin Burnicki Meinberg Funkuhren Bad Pyrmont Germany _______________________________________________ questions mailing list [email protected] https://lists.ntp.org/mailman/listinfo/questions
