[lug] Time Warp again
Hugh Brown
hugh at math.byu.edu
Thu Feb 23 13:28:20 MST 2006
On Thu, 23 Feb 2006, Gordon Golding wrote:
> >>I have a server that every once in a while, changes it's time
>
> >do something like: hwclock --debug --show
>
> # date
> Thu Feb 23 11:14:57 MST 2006
>
> Both of these show the same output:
> # hwclock --debug
> or
> # hwclock --debug --show
> hwclock from util-linux-2.12a
> Using /dev/rtc interface to clock.
> Last drift adjustment done at 1115149028 seconds after 1969
> Last calibration done at 1115149028 seconds after 1969
> Hardware clock is on local time
> Assuming hardware clock is kept in local time.
> Waiting for clock tick...
> select() to /dev/rtc to wait for clock tick timed out
> ...got clock tick
>
> # hwclock --show
> select() to /dev/rtc to wait for clock tick timed out
>
> >>The last time I had weird clock issues, it turned out to be the kernel not getting along with a motherboard
>
> Hmmmmm.... :-)
>
hwclock --debug --show should give:
hwclock from util-linux-2.12a
Using /dev/rtc interface to clock.
Last drift adjustment done at 1137606892 seconds after 1969
Last calibration done at 1137606892 seconds after 1969
Hardware clock is on local time
Assuming hardware clock is kept in local time.
Waiting for clock tick...
...got clock tick
Time read from Hardware Clock: 2006/02/23 14:27:24
Hw clock time : 2006/02/23 14:27:24 = 1140726444 seconds since 1969
Thu 23 Feb 2006 02:27:24 PM CST -0.854604 seconds
I can't remember if I included that or not in my original post.
Timing out on /dev/rtc doesn't sound good.
Hugh
More information about the LUG
mailing list