Re: Clock Problem?

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Unruh wrote:
gaedhealic <gaedhealic@xxxxxxxxx> writes:

Unruh wrote:
gaedhealic@xxxxxxxxx writes:

On Apr 22, 3:22 pm, "Rajko M." <kakomo...@xxxxxxxxxxxx> wrote:
gaedhea...@xxxxxxxxx wrote:
Nubee here....
Hi Nubee,

And to be honest, having a ball with my new OpenSuSE 10.2, amd64
install....
...but this clock IS driving me nuts already!
I'm having no crystal ball, nor "this clock" so if you tell me what is wrong
with a clock in many more words we can look for a solution.
What you did?
What is a problem?

Do we have a fix in t+he works?
For what? Clock?
I don't have any problems with a clock, so "we" falls off in need for a fix.

Hmm...
<snip>

--
Regards, Rajko.http://en.opensuse.org/Portal

I DL the ISO for OpenSuSE 10.2 AMD64 to install on a MSI MB, AMD64.
On install, the installation program ask "Date and Time? " Set to PST,
Local, <date> <Time>
No not OK. Your bios clock is set to what? Local time or UTC. It should be
set to UTC, unless you dual boot with windows. Stting it to local time will
cause you no end of problems.


O.K., so far.
Install works, a little hitch for the Libzypp problem, all is fine,
except the clock in the KDE Panel shows incorrect time.
I have updated to Linux 2.6.18.8-0.1-default #1 SMP x86_64 GNU/Linux
Now, still, in the KDE GUI, bottom right panel, the clock is
incorrectly set. wrong time.
Using Thunderbird to post to a NG, the post failed because "Cannot
Post to Future."
O.K., right-click the clock, > click adjust date & time
Pop up window asks for SU id <suid> [enter]
KDE Control Module opens > the analog clock displays the incorrect
time.
Set the time to the correct time.
Now for the next few minutes the KDE panel Clock displays the correct
time.
Open an other window, open a konsole shell type a command # uname -a
In ten minutes the Clock is off by 10 minutes. that is, I set the
clock at 18:40 (6:40pm) and at 18:50 the KDE panel clock reads 7pm
(19:00)
OK, that is weird. It is either a severe hardware problem, or a wrong Hz
rate.

test for hardware problem?

a) Are you running ntp?

Yes, in response to earlier posts in this thread, since this AM I've
started NTP

It is not going to help. ntp cannot correct a clock that is out by more
than about 500ppm and your is out apparently by about 500000ppm.


The system corrected the time when I clicked apply and OK...

I have since set time to UTC, and the system set the correct time at boot.

OK.


However, the KDE GUI clock is still running fast by the same amount, so
at about 11 AM PST the clock shows 6:40 PM UTC.

The KDE clock should just be the same as the system time.
Open a terminal look at the system clock while you type
date
in the terminal. Compare the two times. If they are the same, then it is a
system time problem.

Now, could you estimate exactly how much the clock is out.

shut down ntpd
do
ntpdate -b pool.ntp.org
as root
and immediately run
date

record tht time.
About 100 sec later, again run
date
ntpdate pool.ntp.org
(No -b this time) this will print out the time from ntp
and compare the two times from ntp and from date. Eg date may say that 180
sec have gone by while ntp says that only 90 sec have gone by. (Note that
the first date will be the same as the first ntp time.)



convert the time difference in both cases into seconds and state how many
seconds in "date" corresponds to how many seconds in ntp.



b) What is your HZ set in the config file for the kernel ( /boot/config
maybe, or /usr/src/linux/.config

# cat /boot/config
cat: /boot/config: No such file or directory

# cat /usr/src/linux/.config
cat: /usr/src/linux/.config: No such file or directory

Using mc, i could not locate a (literal) config file in either location.

I do have a /boot/.config-2~default file, size about 64116

In this file I find:

# CONFIG_HZ_100 IS NOT SET
CONFIG_HZ_250=Y
# CONFIG_HZ_1000 IS NOT SET
CONFIG_HZ=250

OK, this is fine.
I have the same.


Type adjtimex -p
and look at the output, or post it.

# adjtimex -p
mode: 0
offset: 0
frequency: 0
maxerror: 15995
esterror: 0
status: 1
time_constant: 4
precision: 1
tolerance: 33554432
tick: 10000

This one actually confuses me -- it is the same on my system. It would seem
to say that each computer tick is 10000 usec, which is a freq of 100Hz not
250Hz.

raw time: 1177435530s 526007us = 1177435530.526007



Ok, its been just about an hour, my last post was about 19:30/40 UTC and
by my watch it is now 20:40 utc but the KDE clock reads 21:40....


in an hour, the system clock, the software, picked up an hour, or just
about exactly double time...


Now, you mentioned "hardware problems..."

Is there a test program?

thanks,
g


g


-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.5 (GNU/Linux)
Comment: Using GnuPG with SUSE - http://enigmail.mozdev.org

iD8DBQFGLnwRAqk3z+s2AjQRAj5/AJ92K8uEmnG2illClgA3mFN/cqeJcQCePo1l
Q3iC9MQ1mDgWECw2fs9M/0s=
=vnI1
-----END PGP SIGNATURE-----
.

Relevant Pages

  • Re: Naval Observatory Master Clock
    ... Now, if the timers have to set legally traceable to NIST in the theoretic case, snarf the time via NTP and set your timers to the clock value plus one-half the dispersion. ... NIST doesn't set the standard for time. ... NTP is designed to keep the clock of your computer as closely sync'ed to "true" UTC time as is possible with the particular hardware/OS/software configuration you have, and some configurations are capable of better accuracy than others. ...
    (comp.protocols.time.ntp)
  • Re: Which release notes say sts$manager:utc$configure_tdf is obsolete
    ... >>in UTC, and after comparing it to the time as determined from its ... I think it will only attempt to change the clock if it is less than ... or a ST clock just after the spring forward, and NTP would fix it. ... guess of the real time that it makes from polling the time server. ...
    (comp.os.vms)
  • Re: [PATCH/RFC 10/10] example of simple continuous gettimeofday
    ... Uses NTP to modify the clock frequency value rather then just ... > adjustment, which should be applied every f cycles. ... Your design seems to suggest keeping an NTP calculated reference time ...
    (Linux-Kernel)
  • Re: ntp discipline of local time?
    ... Principles and Precision Time Synchronization briefings on the NTP project page are old but applicable. ... The details you are asking for are carefully explained in the NTPv4 spec. ... like the clock state machine and poll-adjust algorithm continue in the daemon. ... factor from CPU cycles to time) and get rid of the offset. ...
    (comp.protocols.time.ntp)
  • Re: [PATCH/RFC 10/10] example of simple continuous gettimeofday
    ... >> The basic idea behind this is that ntp defines the frequency of the ... >> adjustment, which should be applied every f cycles. ... >> which allows for a very stable clock. ... >> resolution is still well within the practical limits of the clock. ...
    (Linux-Kernel)