RE: Tornado/2.0 error message

[johill@lanl.gov (Jeff Hill)]

> >2000-10-23,12:18:11: interrupt: callbackRequest ring buffer full
> 

This indicates that some interrupt service routine
is calling the EPICS routine callbackRequest() to add callback requests
to the callback queue at a rate that is faster than the callback thread
can dispatch the requested callbacks. This might occur if an EPICS
driver was calling scanIORequest() from interrupt level very frequently
or it might occur because some other high priority thread is saturating 
the CPU and preventing the callback thread from running.

> >2000-10-23,09:09:45: 0x78dd64 (tNetTask): arptnew failed on a436d813
> >2000-10-23,09:15:45: 0x78dd64 (tNetTask): arptnew failed on a436d813
> >2000-10-23,09:23:45: 0x78dd64 (tNetTask): arptnew failed on a436d813
> >2000-10-23,09:29:45: 0x78dd64 (tNetTask): arptnew failed on a436d813
> >2000-10-23,09:35:45: 0x78dd64 (tNetTask): arptnew failed on a436d813
> >2000-10-23,09:43:45: 0x78dd64 (tNetTask): arptnew failed on se

Perhaps these errors are resulting from attempts by arp to build an 
Ethernet address <=> IP address association, but there is already
an inconsistent entry in its tables. I would type "arpShow" to see
if there are configuration problems (possibly related to a back plane 
network).

Jeff