[pe.cust.wanted] why does our clock lose time?

dave@lsuc.UUCP (David Sherman) (01/17/85)

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?

David Sherman
The Law Society of Upper Canada
Toronto
-- 
{utzoo pesnta nrcaero utcs}!lsuc!dave
{allegra decvax ihnp4 linus}!utcsrgv!lsuc!dave
-- 
{utzoo pesnta nrcaero utcs}!lsuc!dave
{allegra decvax ihnp4 linus}!utcsrgv!lsuc!dave

earlw@pesnta.UUCP (Earl Wallace) (01/18/85)

> 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