Most managers said there is a problem with the memory module U312. The cheaper
way is that I may need to reseat it first before replacing it. But since it
is transient, I don't have to worry about it until I see that error message
repeating again and again.
Special thanks to Lars-Peter who sent me the picture of the SS2 board with
the chips location and Claus Assmann who pointed me to the archive site
"aurora.latech.edu" to get the memory check summary. If any of you
happened to have the summary of the memory check info, would you please mail
it to me.
Thanks so much to all listed below, and I'm truly sorry if I miss any.
firstname.lastname@example.org (Dave Curado)
Steve Elliott <email@example.com>
firstname.lastname@example.org (Lars-Peter Sward)
Claus Assmann <email@example.com>
firstname.lastname@example.org (Sean Ward)
Steve Lodin <email@example.com>
Steve J Lacey <firstname.lastname@example.org>
email@example.com (Jeanne Gee)
Larry Chin <Larry_Chin@cchtor.cch.com>
firstname.lastname@example.org (Miguel A. Rozsas)
Jun Wu <jun@CURIE.SSCTR.BCM.TMC.EDU>
email@example.com (Peter Watkins)
firstname.lastname@example.org (Jerry Symanski - NRaD Code 761)
email@example.com (Andy Feldt)
firstname.lastname@example.org (Martin J. Burke)
Dave Gunter <email@example.com>
firstname.lastname@example.org (Jim Shore)
> Dear Sun Managers,
> Have any of you seen these error messages before? Please let me know what
> they mean. I extracted it by typing # /etc/dmesg | more
> dump on sd0b fstype spec size 32748K
> Parity error reported at 0xf35558, actual address is 0xf35554.
> Parity Error, ctx = 0x6, virt addr = 0xf35554
> pme = c3001bbe, phys addr = 1bbe554
> Parity Error Register 91<ERROR,CHECK,ERR24>
> bad module/chip at: U312
> pid 6288 killed: parity error
> parity error at 1bbe554 is transient.
> page 1bbe000 back in service.
> System operation can continue
> Thanks, Aline...
This archive was generated by hypermail 2.1.2 : Fri Sep 28 2001 - 23:08:54 CDT