Path: utzoo!utgpu!news-server.csri.toronto.edu!clyde.concordia.ca!uunet!mcsun!hp4nl!phigate!cnps!news
From: dupuy@HUDSON.CS.COLUMBIA.EDU (Alexander Dupuy)
Newsgroups: comp.protocols.time.ntp
Subject: problem running ntp 3.4 on a Sun 4/390 running SunOS 4.0.3
Message-ID: <1153@cnps.PHILIPS.nl>
Date: 23 Jul 90 12:36:54 GMT
Sender: news@cnps.PHILIPS.nl
Lines: 21

We had this problem too, on a Sun-4/390 running 4.0.3.SPARCserver.390.  The
problem is that the kernel is built with a bogus copy of clock.o which has all
the debugging statements turned on.  Not only does this generate reams and
reams of stupid messages, but the kernel printfs block the timer interrupts,
causing the machine to keep truly terrible time - worse than a Sparcstation-1!

The fix is to take the Sun-4 clock.o module from a vanilla 4.0.3 release, or
the 4.0.3 patch tape, and make the following "well-known" adb patch to it:

        # adb -w /sys/sun4/OBJ/clock.o
        todget+0x1e0?X
<old value should be 80a3e006>
        todget+0x1e0?W 80a3e007
        $q
        #

The rebuild your kernel and you're off and running!  I did this a few months
back, and it turned my 4/390 from a lousy timekeeper which flooded my syslogs
into a happy (and quiet) chimer.

@alex