Wed, Nov 24, 2004 at 07:11:02PM -0500, John Klos:
> >i believe this is due to the pmap problem, for which there is no 
> >work-around.
> 
> Hmmm. I guess I haven't been following the mailing list about this. My 
> Ultra 5 hasn't had any issues, so I never looked into this. What's broken 
> about the Ultra 1? Is it something specific with certain UltraSPARC CPUs?

I do not believe it is particular to a given CPU, but specific to some
work load.  For example; cause the file cache to use all the available
memory while doing a build, then run sync.

ATM, it appears that either something is trodding on pmap structures or
using them without initializing.  Could be locking, where some mapping
is released and something else tries to access it at the same time.