Re: camac crate init

[Andrew Johnson <anj@aps.anl.gov>]

Garett,

One difference I noticed recently between the mv167 and mv172 is that the
MC68060 in the mv172 doesn't have a separate Interrupt Stack Pointer, so
all tasks need to allow for the stack space taken by the interrupt service
routines.  We found that the task that collected CPU usage statistics had
very little stack space left, and we think that the rare occasions when
our mv172 systems were hanging completely were due to overflowing the
stack of that particular task.  You might want to run a stackCheck on your
system to see whether you have any low HIGH values.

- Andrew
-- 
Complexity comes for free, Simplicity you have to work for.