Incidentally, Greg Oster replied to me, and indicated that it looks like
raidframe was waiting for allocating kernel memory.  He indicated that
(until the actual bug(s) can be found and squashed) bumping up 
NKMEMPAGES should alleviate the symptoms.  I've doubled mine (from
roughly 8k to roughly 16k) and haven't had a crash (knock on wood!)
since then.

+j

On Thu, Sep 20, 2001 at 10:47:24PM -0700, Jeff Rizzo wrote:
> On Thu, Sep 20, 2001 at 09:47:23PM -0400, David Maxwell wrote:
> > If you get this again, can you check if you can C-A-F2 etc to the other
> > wsconsoles. My 5 disk raid machine (1.5U or so) has done the same thing
> > a couple of times. DDB works, wsconsole works, but the machine is
> > spinning in the idle loop. It won't reply on the network, or let
> > anything be typed on the console.
> 
> This machine is serial console only, so I won't be able to help here...
> 
> > 
> > I'll append the info on my wait states for comparison.
> 
> I will keep it in mind.  Nice (kind of) to know that I'm not the only
> one seeing *something*.
> 
> +j

-- 
Jeff Rizzo                                         http://boogers.sf.ca.us/~riz