Re: SCO Openserver 5.0.6 losing time
From: Stevalyn (stevalyn_at_reply.to.news)
Date: 09/11/03
- Next message: Stevalyn: "Migrating from OS5.0.7 to UW7.1.3 - Help!"
- Previous message: Chaz: "Re: Network Horror"
- In reply to: schumw: "SCO Openserver 5.0.6 losing time"
- Next in thread: schumw: "Re: SCO Openserver 5.0.6 losing time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Thu, 11 Sep 2003 18:42:55 +0930
schumw wrote:
> We have a server running SCO Openserver 5.0.6a and the system is losing
> time at about (in fact almost exactly) 15 seconds a minute. The Real
> Time Clock keeps time fine, however the operating system clock is
> losing it.
>
>
>
> # setclk -p
>
> RTC 2003/09/11 14:36:29 STD
>
> SYS 2003/09/11 14:35:12 STD RTC-SYS=77
>
> # setclk -p
>
> RTC 2003/09/11 14:36:43 STD
>
> SYS 2003/09/11 14:35:23 STD RTC-SYS=80
>
> # setclk -p
>
> RTC 2003/09/11 14:37:29 STD
>
> SYS 2003/09/11 14:35:57 STD RTC-SYS=92
>
> # setclk -p
>
> RTC 2003/09/11 14:38:44 STD
>
> SYS 2003/09/11 14:36:54 STD RTC-SYS=110
>
>
>
> Does anyone know of a solution to this?
>
>
>
> Thanks.
>
>
> --
> Posted via http://dbforums.com
Quote from
TA # 115103
Please check the following:
1. Are you using a non-standard time zone or a half hour time zone, such
as IST?
There is a known problem with half hour and non-standard time
zones, which has been reported to Caldera Engineering. A
workaround for this problem is to disable RTC tracking. To
do this,
edit /etc/conf/pack.d/clock/space.c and change:
FROM:
int track_rtc = 1;
TO:
int track_rtc = 0;
then, relink the kernel with the following:
/etc/conf/cf.d/link_unix -y and reboot.
2. If you are using a standard time zone, such as GMT or EST, but the
problem is still occurring, it may be that the clock driver's
measurements of the CPU clock frequency are inconsistent. To check if
this is the case, please run:
grep clock /usr/adm/syslog
If the output is similar to that below, then this is the
problem.
In this case, the system had a 180 Mhz CPU, but as you can
see the
clock driver's measurement of the frequency was inconsistent.
%clock - - - type=TSC/67360126Hz
%clock - - - type=TSC/101040742Hz
%clock - - - type=TSC/134720983Hz
%clock - - - type=TSC/112267613Hz
%clock - - - type=TSC/134720903Hz
It is possible to work around this problem by forcing the
clock
driver to use a specified frequency. For instance, if you know
that you have a 133 Mhz CPU, try booting the system with the
following bootstring:
unix clock.tsc_clock_hz=133000000
(that is the Mhz value followed by six zeros). If the
system clock
still runs slowly, you can try a slightly lower value. If the
system clock runs a bit fast, you can try a slightly higher
value.
If this fixes the problem, then you can 'hard wire' the clock
driver to use this value all the time. Edit
/etc/conf/pack.d/clock/space.c and change:
unsigned long tsc_clock_hz = 0;
to equal the Mhz value that fixes the problem. Then, relink the
kernel with /etc/conf/cf.d/link_unix -y and reboot.
Note
If you are having this problem with a version of OpenServer prior to
5.0.6, then the solution is to upgrade to 5.0.6 and then apply the
workarounds detailed above.
- Next message: Stevalyn: "Migrating from OS5.0.7 to UW7.1.3 - Help!"
- Previous message: Chaz: "Re: Network Horror"
- In reply to: schumw: "SCO Openserver 5.0.6 losing time"
- Next in thread: schumw: "Re: SCO Openserver 5.0.6 losing time"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|
