My first thought is "is it really truly syslogd?"  It's not obvious from
   above whether or not the syslogd message was immediately before the
   trap or some time earlier in the past.  Is it reproducable?  If so, how
   stable is the box without syslogd running?


i've seen sparc64 crash when syslogd started up .... it was a bug
that got squashed a while ago.


.mrg.