> 
> Darn, that was a bit too soon. I guess I should also increase the normal
> kernel stack somehow. Are those numbers in the stack traceback the stack
> pointer? In that case, SHA1Update (or SHA1Transform?) uses an idiotic
> amount of stack (which I would not suspect if I read
> src/sys/lib/libkern/sha1.c).. It must be misleading in this case.
> Oh well, another job for tomorrow :)
> 
Etch. The kernel stack is something ~6K in size, I would feel very bad
about having to increase it. But looking at your stack trace, it may be
something else also that causes the problem. Can you do a ps and ps/a in
ddb also please?

-- Ragge