[comp.protocols.time.ntp] xntpd woes on a Sun 4/390 running SunOS 4.0.3

matt@eecs.nwu.edu (Matt Larson) (05/04/91)

I am having trouble getting xntpd (version 1.3) to behave on a Sun
4/390 running SunOS 4.0.3.  Exactly the same symptoms occur when
running ntp.

I see the following over and over again on the console:

resettodr: setting TOD chip to 06-03-23 20:46:52
resettodr: TOD chip was 06-03-23 20:46:50

The frequency between these messages is proportional to the size of
the kernel variable ``tickadj''.  Speaking of kernel variables, here
are the values of the relevant ones (in hex):

tick		270d
tickadj		3e8
dosynctodr	0

I know that tickadj should be 5, but that just increases the number of
times I see the ``resettodr'' message.  (To once every four
seconds...)

I have also applied another patch from Sun.  The important excerpts
are below:

-- begin part of patch from Sun
Dave Barney
Sun Microsystems, USAC
debarn@sun.com
(415)336-1226

********************TOD Patch***********************

There is a bug in SunOS 4.0.3 which causes the Sun 4300 processor
board to be unable to synchronize the kernel's notion of the time
of day with the TOD chip.

This applies ONLY to SunOS 4.0.3 for the Sun 4 ...

To patch a running kernel: (will be fixed until next reboot)

        # adb -w -k /vmunix /dev/mem
        todget+0x1e0/X
<old value should be 80a3e006>
        todget+0x1e0/W 80a3e007
        $q
        #

-- end part of patch from Sun

I don't know if this patch is intended to fix the console messages or
just clock drift in general.  Either way, it doesn't work.

Now, none of this would be overly frustrating -except- that -right
next- to this particular 4/390 is ANOTHER 4/390, with the same kernel
configuration (I have cmp'ed every object module) and running exactly
the same of version of the ntp I tried.  It has no such messages on
the screen.  Could this be a hardware problem with the first 4/390?

While I suspect that this problem is fixed under SunOS 4.1, upgrading
is not possible right now.

So, any comments or suggestions would be greatly appreciated.

Thanks,

--
Matt Larson, Distributed Systems Analyst
Academic Computing and Network Services, Northwestern University
matt@acns.nwu.edu   (708) 491-5366