thanks to all who responded...
It seems that this is a known problem with solaris and 400 MHz CPUs with
8MB Cache which is caused by a failed parity check on the E-Cache. Many
suggested to apply the latest kernel-patch (for solaris 2.6 it's 105181-23)
because this one has a ecache scrubber which minimizes the problem but doesn't
Reggi Stuart recommended to get the iscda (initial system crash dumpanalysis)
tool with wich we can analyse the core dumps.
Most of the responses suggested to replace the CPUs.
I think our way will be first to apply this patch 'cause we only have remote
control over the server. If the problem appears again (seems to be relatively
rare) we will let the CPUs be replaced.
Again thanks to all who responded.
U BEFORE POSTING please READ the FAQ located at
. and the list POLICY statement located at
A To submit questions/summaries to this list send your email message to:
A To unsubscribe from this list please send an email message to:
E and in the BODY type:
R unsubscribe sun-managers
. unsubscribe sun-managers firstname.lastname@example.org
L To view an archive of this list please visit:
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:14:23 CDT