Hi,
I have upgraded my Dell C151 to the latest 5.6. I have always used
ntp to sync this machine and then the rest of the machines in the
network would sync from it. Since the update I cannot keep the right
time on the machine. This is with / without ntp. I have attempted
various scenario's with no luck. I am now trying the old kernel now as I
type this out. If anyone else has any links or ideas that I should check
out It would be greatly appreciated.
Just a quick note about my setup. I do not use any gui. As
mentioned I have not had any issues with this machine and it's time
until I upgrade.
AMD Athlon(tm) 64 X2 Dual Core Processor 3800+
3gb of ram.
TIA.
Brian.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: smime.p7s
Type: application/pkcs7-signature
Size: 6022 bytes
Desc: S/MIME Cryptographic Signature
URL:
<http://lists.centos.org/pipermail/centos/attachments/20110413/d4e63cdf/attachment-0005.p7s>
On 4/13/2011 7:35 AM, Mailing List wrote:> Hi, > > I have upgraded my Dell C151 to the latest 5.6. I have always used > ntp to sync this machine and then the rest of the machines in the > network would sync from it. Since the update I cannot keep the right > time on the machine. This is with / without ntp. I have attempted > various scenario's with no luck. I am now trying the old kernel now as > I type this out. If anyone else has any links or ideas that I should > check out It would be greatly appreciated. > > Just a quick note about my setup. I do not use any gui. As > mentioned I have not had any issues with this machine and it's time > until I upgrade. > > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > 3gb of ram. > > TIA. > > Brian.Just to follow up, I had switched to the old kernel before the 5.6 upgrade, and at this time my clock is working flawlessly. kernel v. 2.6.18-194.32.1.el5 Works as it should... kernel v. 2.6.18-238.5.1.el5 I cannot get my clock accurate. If there is anything I can do to help solve this IE: information or test. please let me know.At this point I will just make the old kernel default boot until there is a kernel update where which I will try again. Brian. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6022 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20110413/0df8710a/attachment-0005.p7s>
On 4/13/2011 7:35 AM, Mailing List wrote:> Hi, > > I have upgraded my Dell C151 to the latest 5.6. I have always used > ntp to sync this machine and then the rest of the machines in the > network would sync from it. Since the update I cannot keep the right > time on the machine. This is with / without ntp. I have attempted > various scenario's with no luck. I am now trying the old kernel now as > I type this out. If anyone else has any links or ideas that I should > check out It would be greatly appreciated. > > Just a quick note about my setup. I do not use any gui. As > mentioned I have not had any issues with this machine and it's time > until I upgrade. > > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > 3gb of ram. > > TIA. > > Brian. >Something I wanted to add, Cal here on the list gave me a command to run.. Here is the results on a working 5.5 kernel. root > ~# ntpq -c pe -c as remote refid st t when poll reach delay offset jitter =============================================================================*slackadelic.com 204.9.54.119 2 u 746 1024 377 57.333 -1.560 1.054 +ntp2.Rescomp.Be 128.32.206.55 2 u 351 1024 377 107.342 11.677 0.197 +w1-wdc.ipv4.got 10.0.77.54 3 u 708 1024 377 25.122 8.503 1.698 LOCAL(0) .LOCL. 10 l 33 64 377 0.000 0.000 0.001 ind assID status conf reach auth condition last_event cnt ========================================================== 1 18756 9614 yes yes none sys.peer reachable 1 2 18757 9414 yes yes none candidat reachable 1 3 18758 9414 yes yes none candidat reachable 1 4 18759 9014 yes yes none reject reachable 1 Now here is the results on the 5.6 kernels. root > ~# ntpq -c pe -c as remote refid st t when poll reach delay offset jitter ============================================================================== bindcat.fhsu.ed 132.163.4.101 2 u 1015 1024 377 49.987 -15082. 6919.88 216.45.57.38 108.71.253.18 2 u 998 1024 377 83.112 -15139. 6900.14 javanese.kjsl.c 69.36.224.15 2 u 1 1024 377 109.083 -29233. 7285.83 *LOCAL(0) .LOCL. 10 l 13 64 377 0.000 0.000 0.001 ind assID status conf reach auth condition last_event cnt ========================================================== 1 26525 9044 yes yes none reject reachable 4 2 26526 9044 yes yes none reject reachable 4 3 26527 9044 yes yes none reject reachable 4 4 26528 9644 yes yes none sys.peer reachable 4 And as for the clock source. # CentOS 5.5 Kernel 2.6.18-194.32.1.el5.. Time runs as it should. cat /sys/devices/system/clocksource/clocksource0/available_clocksource=jiffies cat /sys/devices/system/clocksource/clocksource0/current_clocksource=jiffies # CentOS 5.6 kernel 2.6.18-238.5.1.el5 Time goes to the dogs. cat /sys/devices/system/clocksource/clocksource0/available_clocksource=jiffies cat /sys/devices/system/clocksource/clocksource0/current_clocksource=jiffies TIA Brian
On 4/13/2011 7:35 AM, Mailing List wrote:> Hi, > > I have upgraded my Dell C151 to the latest 5.6. I have always used > ntp to sync this machine and then the rest of the machines in the > network would sync from it. Since the update I cannot keep the right > time on the machine. This is with / without ntp. I have attempted > various scenario's with no luck. I am now trying the old kernel now as > I type this out. If anyone else has any links or ideas that I should > check out It would be greatly appreciated. > > Just a quick note about my setup. I do not use any gui. As > mentioned I have not had any issues with this machine and it's time > until I upgrade. > > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > 3gb of ram. > > TIA. > > Brian.I hope I'm not the only one having this issue with ntp and the new 5.6 kernels.. I am still stuck on the old 5.5 kernel, anything from the 5.6 era and I start seeing time issues. Brian. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6022 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20110420/c381ff33/attachment-0005.p7s>
> On 4/13/2011 7:35 AM, Mailing List wrote: >> Hi, >> >> I have upgraded my Dell C151 to the latest 5.6. I have always used >> ntp to sync this machine and then the rest of the machines in the >> network would sync from it. Since the update I cannot keep the right >> time on the machine. This is with / without ntp. I have attempted >> various scenario's with no luck. I am now trying the old kernel now >> as >> I type this out. If anyone else has any links or ideas that I should >> check out It would be greatly appreciated. >> >> Just a quick note about my setup. I do not use any gui. As >> mentioned I have not had any issues with this machine and it's time >> until I upgrade. >> >> AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ >> 3gb of ram. >> >> TIA. >> >> Brian.Have you tried installing the adjtimex package? If your system clock is running reliably fast under the 5.6 kernel, maybe adjtimex can turn that reliability into reliable time sync for you? Rick
On 4/13/2011 7:35 AM, Mailing List wrote:> Hi, > > I have upgraded my Dell C521 to the latest 5.6. I have always used > ntp to sync this machine and then the rest of the machines in the > network would sync from it. Since the update I cannot keep the right > time on the machine. This is with / without ntp. I have attempted > various scenario's with no luck. I am now trying the old kernel now as > I type this out. If anyone else has any links or ideas that I should > check out It would be greatly appreciated. > > Just a quick note about my setup. I do not use any gui. As > mentioned I have not had any issues with this machine and it's time > until I upgrade. > > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > 3gb of ram. > > TIA. > > Brian.List, I was not able to resolve my issue with the time on this machine. I went ahead and rolled the update back to 5.5 and disabled the update to 5.6. What I would like to know is if CentOS 6 might be ok when it rolls out, or am I just going to have to keep with 5.5 till EOL? Thanks to all with there help. Brian. -------------- next part -------------- A non-text attachment was scrubbed... Name: smime.p7s Type: application/pkcs7-signature Size: 6022 bytes Desc: S/MIME Cryptographic Signature URL: <http://lists.centos.org/pipermail/centos/attachments/20110425/1a670681/attachment-0005.p7s>
Denniston, Todd A CIV NAVSURFWARCENDIV Crane
2011-Apr-25 19:47 UTC
[CentOS] CentOs 5.6 and Time Sync
> -----Original Message----- > From: centos-bounces at centos.org [mailto:centos-bounces at centos.org] On > Behalf Of Mailing List > Sent: Monday, April 25, 2011 13:57 > To: CentOS mailing list > Subject: Re: [CentOS] CentOs 5.6 and Time Sync > > On 4/13/2011 7:35 AM, Mailing List wrote: > > Hi, > > > > I have upgraded my Dell C521 to the latest 5.6. I have always used > > ntp to sync this machine and then the rest of the machines in the > > network would sync from it. Since the update I cannot keep the right > > time on the machine. This is with / without ntp. I have attempted > > various scenario's with no luck. I am now trying the old kernel now> > AMD Athlon(tm) 64 X2 Dual Core Processor 3800+ > > 3gb of ram. > > > > TIA. > > > > Brian. > > > List, > > I was not able to resolve my issue with the time on this machine. > I > went ahead and rolled the update back to 5.5 and disabled the updateto> 5.6. > > What I would like to know is if CentOS 6 might be ok when it rolls > out, or am I just going to have to keep with 5.5 till EOL? > > Thanks to all with there help. >1) I hope you are only talking about having rolled back to the last working for you kernel from 5.5, not the whole distribution. 2) If I was in your position and had time, my method would be[1] a) get the srpm for the last known working kernel (2.6.18-194.32 ???) b) get the srpm for the first known not working kernel (2.6.18-238 ???) c) expand each of the above srpms into their own rpm build tree i.e., rpmdev-setuptree;rpm -i kern1; mv rpmbuild rpmbuild.kern1; rpmdev-setuptree;rpm -i kern2; mv rpmbuild rpmbuild.kern2 d) start looking at the differences in the patches applied in kern1 vs. those in kern2, i.e., read/diff the kernel.spec files see if there were any new ones that seemed likely to be causing the problem... RTFS if necessary to make better guesses. Rebuild kernel 2 with patches taken out/modified based on my investigations and test them and see if I guessed right. If no luck, think about opening an TUV bug with lots of the info you have sent here, they may be interested even if you don't have a subscription. [1] Been there, done that: http://www.gossamer-threads.com/lists/drbd/users/9616
Seemingly Similar Threads
- ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
- ntpd under Xen Dom0 exhibits extremely high jitter/noise? runs stable/quiet under non-xen kernel.
- clocksource/0: Time went backwards
- use mathematics formula
- Screen blanking crashes