Is there a fix for this that ought to be pulled up for 1.5.1?
   (Ultra10)


there are probably several dozen bug fixes for sparc64 that "ought
to be" pulled up for 1.5.1 that have been missed.  there are also
quite a number of quite useful/essential changes that aren't going
to be easy to get into a 1.5 tree...


the suggestion is normally to run a -current kernel as it is just
so much more stable. :-(  post-1.5 releases will obviously get
this much better.... 


i find your panic vaguely familiar, but i don't recall exactly what
was the cause or how to fix it.


.mrg.