Thanks to the following folks, who all told me more-or-less the same
thing - poorly CPU or poorly cache:
Jim Craven <craven@cg.NRCan.gc.ca>
Lucia Gonzalez <firstname.lastname@example.org>
Dylan Carlson <email@example.com>
Richard Felkins <firstname.lastname@example.org>
Adrian Stovall <email@example.com>
Scott Kulp <firstname.lastname@example.org>
"Schultz, Juergen" <Juergen.Schultz@m.dasa.de>
"Newman, Timothy L" <email@example.com>
Sun confirmed it was a CPU problem and replaced the CPU (we have a
maintenance contract). It turned out that they had to replace the
whole mainboard since the CPU was a fixture. I notice that the new
mainboard had a /huge/ heatsink and no fan - obviously a redesign because
we have had to replace two Ultra-1 CPU fans in the last year (including
the one on this machine).
Cheers again everyone,
Original message below:
> I have an Ultra1/170 running Sol 7 that has experienced a couple of
> crashes recently with the error:
> panic[cpu0]/thread=70cf7340: CPU0 Ecache SRAM Data Parity Error:
> AFSR 0x00000000.00400002 AFSR 0x00000000.37effff0
> Does this mean that one of the memory SIMMs is misbehaving? If so, any
> ideas how to find out which one from that lot above? Or indeed to deciper
> it into something more practical?
> Any info gratefully received.
-- Dr Chris Stoddart: Unix SysAdmin, Department of Computer Science, Sheffield University, U.K.
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:13:25 CDT