Relay-Version: version B 2.10.2 9/18/84; site lsuc.UUCP
Posting-Version: version B 2.10.2(pesnta.1.2) 9/5/84; site pesnta.UUCP
Path: lsuc!pesnta!earlw
From: earlw@pesnta.UUCP (Earl Wallace)
Newsgroups: pe.cust.wanted
Subject: Re: why does our clock lose time?
Message-ID: <2637@pesnta.UUCP>
Date: 18 Jan 85 03:42:17 GMT
Date-Received: 18 Jan 85 03:47:59 GMT
References: <301@lsuc.UUCP>
Organization: Perkin-Elmer DSG, Santa Clara, Calif.
Lines: 17

> Our 3220 loses time steadily, at more than a minute a week.
> PE service replaced the clock board, but that didn't help.
> Anybody know why? Could it be something to do with interrupts
> on the system getting in the way of the clock, or something
> along those lines?
> 

The parameter "PIC" in the /usr/sys/conf/param.s file might be the major cause
of the slowness.  Set it to the opposite state and see if that helps (I can't
remember if the 0 or 1 setting causes the problem...).  If PIC is set to 1, it
adds extra code in the *.s modules which could be eating up more interrupt
time than necessary.  Of course, setting to 1 might *help* the clock too!
-- 
Earl Wallace
UUCP:   ..!{ihnp4, ucbvax!hplabs, ucbvax!twg}!pesnta!earlw
PHONE:	(408) 727-5540 x230
USMAIL:	Perkin-Elmer Corp., Santa Clara, Calif. 95054