Bug 4932
| Summary: | timer problems with kernels => 2.6.12 | ||
|---|---|---|---|
| Product: | Timers | Reporter: | Georg Armbruster (georg) |
| Component: | Realtime Clock | Assignee: | john stultz (john.stultz) |
| Status: | REJECTED UNREPRODUCIBLE | ||
| Severity: | normal | CC: | akpm, john.stultz |
| Priority: | P2 | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Kernel Version: | 2.6.13.rc* | Subsystem: | |
| Regression: | --- | Bisected commit-id: | |
|
Description
Georg Armbruster
2005-07-23 09:19:28 UTC
Are you running the NTP daemon? If so, could you try disabling it, see what happens? Hi Andrew, you are right, it must have to do with the ntpd daemon; disabling chrony and checking the time every hour using ntpdate shows no differences in time over the last 24 hours. Since the problem began nevertheless with the kernel update, do you have any clue where to start searching? Thanks for your help! Peace, Georg Interesting, I've not heard of chrony (for reference - http://chrony.sunsite.dk/index.php ) before. Does it provide anything like the peerstats logging that the ntp.org ntpd provides? Hi John, chrony is a lightweight ntp-daemon and worked quite reliable - that is, until recently :) I'm not exactly sure how to read them, but I put the chrony logs on the web for your reference: http://www.relaxing-solutions.net/measurements.log http://www.relaxing-solutions.net/statistics.log http://www.relaxing-solutions.net/tracking.log Regards, Georg Hmm. Odd. I'm not seeing anything in the logs that point to time drifting away from the time server. Just to clarify the problem, when you say the clocks go crazy and are wrong for a couple of minutes per hour, do you mean the clock drifts (slows down or speeds up) few minutes every hour, or that for a discrete amount of time each hour, gettimeofday returns incorrect time values? Hi John, it's like you said, during one hour, the clock drifts away for several minutes, it mostly sped up. Interestingly, during midday more than in the morning and the evenings. The really strange thing is: for the last couple of days, the problem doesn't exist anymore. I had this phenomenon on four pc's, and I switched back only one of these to the old kernel. The other three, I swear, were not touched at all concerning configuration. Yet for the last couple of days, they work normally again. Which is, basically, something I cannot understand. (Since it was me who quite often told folks that computers don't do anything on their own. Boy was I wrong :=) Well, basically, I cannot understand this. If you haven't any additional ideas, I propose closing this bug until the problem comes up again. What do you think? Georg: Hmm. Ok, I'll go ahead and close this. Please do reopen if you've had any continuing issues. |