Hello,
Well the problem is solved thanks to Martin J. Moore :
---- snip -----
Do "sysconfig -q generic clock-frequency". The value should be 1200 for
a 4000. If it's not 1200, look for a line defining clock-frequency in
/etc/sysconfigtab. If present, delete it and reboot.
--- snip ----
it was 1024 and therefor the clock was going wrong.
Thanks also to Tom Blinn who gave a good round up of how the time is caclulated
---snip ----
The console firmware is responsible for programming the "realtime clock"
on the motherboard, which is supposed to interrupt the kernel about once
each millisecond. The exact rate is programmed by console firmware, and
passed to the UNIX kernel in a special data structure called the HWRPB
(or HardWare Reset Parameter Block). Each time the interrupt happens,
special code in the kernel increments the kernel's time value. In some
cases, the interrupts can be missed, in which case, you'll see a clock
drift, but it's usually that the calculated time grows SLOWER than the
actual passage of time (because you don't increment the system's measure
of time as often as you should).
----- snip -----
Have fun
Samier Kesou
---------------------- Weitergeleitet von Samier Kesou/Extern/11/BfA-Berlin on
21.08.2001 11:58 ---------------------------
Samier.Kesou_at_bfa-berlin.de on 20.08.2001 16:00:34
An: tru64-unix-managers_at_ornl.gov
Kopie: (Blindkopie: Samier Kesou/Extern/11/BfA-Berlin)
Thema: Time-keeping
Hello,
i have a little problem with the calculated time on my server (Alpha 4000 -
DUV40E).
We have added a new scsi host adapter. Now all pci slots are used.
After that the local clock of the server runs in actual 5 minutes 7 minutes.
Thats +24 Minutes in an hour.
The clock chip and the backplane have been checked with no result.
Does anyone have an idea how this can happen.
Thanks in advance,
Samier.
Received on Tue Aug 21 2001 - 10:11:13 NZST