Summary: | net-misc/ntp-4.2.4 logging "kernel time sync error 0001" | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | Allan Dennis <ajd20000> |
Component: | [OLD] Server | Assignee: | SpanKY <vapier> |
Status: | RESOLVED UPSTREAM | ||
Severity: | trivial | CC: | mrpippy |
Priority: | High | ||
Version: | unspecified | ||
Hardware: | x86 | ||
OS: | Linux | ||
URL: | https://ntp.isc.org/bugs/show_bug.cgi?id=780 | ||
Whiteboard: | |||
Package list: | Runtime testing required: | --- |
Description
Allan Dennis
2007-03-16 03:44:32 UTC
https://ntp.isc.org/bugs/show_bug.cgi?id=780 is the upstream bug. Short summary: it's from code that was introduced in 4.2.4, and is caused by ntp_adjtime (a kernel/glibc function) returning an error. Either way, it is certainly not Gentoo specific. The error is showing up for me on amd64, 2.6.17. From my observation, NTP still seems to be doing its job properly though. remind me when this gets resolved properly upstream and i'll pull down the fix/new version ;) > The error is showing up for me on amd64, 2.6.17. From my observation, NTP
> still seems to be doing its job properly though.
Not according to the upstream bug reporter, and it seems to be affecting my little office server as well (I get both the error messages and random erratic time-sync behavior). I think the suggestion of masking 4.2.4 until it's fixed is a good idea...
When you guys marked this as RESOLVED UPSTREAM, is that because the problem was determined to be a kernel bug? If so, the understanding is that the latest 2.6 kernel version fixes this? |