Path: utzoo!attcan!uunet!aplcen!samsung!cs.utexas.edu!rutgers!njin!princeton!phoenix!phoenix.princeton.edu!eho
From: eho@clarity.Princeton.EDU (Eric Ho)
Newsgroups: comp.sys.xerox
Subject: timerexpired? barfs from IPLISTENER ...
Message-ID: <EHO.90Jun3010830@word.Princeton.EDU>
Date: 3 Jun 90 05:08:30 GMT
Sender: news@phoenix.Princeton.EDU
Distribution: comp
Organization: Cognitive Science Lab.  Princeton University.
Lines: 24

Does anyone out there know what causes the IPLISTENER breaks when the TIMER
field has a negative value in the TIMEXPIRED? frame ??

All my D-machines (all running Koto) seems to break at the same time.  When I
backtraced it, the TIMEXPIRED? frame has TIMER as -36528 (or some other large
negative numbers) assigned.  Also, in the \IPLISTENER frame, the
\AR.WAKEUP.TIMER is also assigned with a negative value (e.g. -636611).

Also, in the \AR.UPDATE.RESOLUTION frame, I've ARENTRY assigned to
{ARENTRY}#64,134666

It seems that somehow the timer in Koto is seriously screwed, causing havoc to
IP and ARP.

If anyone know what causes this and/or know any workarounds, I'll be most
grateful.

thanks.

--

Eric Ho  
Princeton University
eho@clarity.princeton.edu