> 
> In case anyone else cares, the problem seems to stem from the calls to
> pmap_enter() and pmap_remove() in /sys/arch/vax/vax/mem.c:mmrw()
> ... my guess so far is that for some reason the second time the
> pmap_enter() is called, the memory region isn't being mapped into
> memory properly, so the eventual call to pmap_remove() fails.  The
> code in ps that's triggering the bug is 
>
I have rewritten large parts of the vax mm code lately, and as a result
of that pmap_enter() and pmap_remove() disappeared from mem.c.
There are also lots of other changes, and I will commit it when I'm
satisfied with the stability. There are a significant speedup of
the vm code also.

-- Ragge