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. Asmentioned 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