[ ... NetBSD/mips -current trashes kernel profiling ... ]

> Aha!  I now see where the mips went wrong.  When the mips was switched
> to use the proc0 stack, it was *resetting* the stack pointer, which then
> started scribbling over the current stack frames in use by uvm_scheduler.
> It should have been using the *current* stack pointer for proc0.  Doing
> this now allows a profiled kernel to work.

Dah...  It was me who changed the switch_exit().  I now understood
what's going on proc0 stack space.  It would be easy to fix it.

Tohru Nishimura
Information Technology Centre
Nara Institute of Science and Technology