CORRECTION: Parity errors

2007-12-24 19:34:00

Hi again,

My original post listed the wrong type of
machine. It's an Ultra *10*, not an Ultra 5.
Sorry 'bout that.

-Gary

-----Original Message-----
From: Gary Richardson [mailto:grichardson at watercove.com]
Sent: Monday, March 19, 2001 8:47 AM
To: 'codeprof at codeprof.com'
Subject: Parity errors

Hi,

I have an Ultra 5 running Solaris 7 that acts as an NIS slave on my network.
Over the weekend it rebooted multiple times and I found this error in the
messages
file:

Mar 18 03:23:27 washburn savecore: reboot after panic:
Mar 18 03:23:27 washburn simba1: PBM generated system error.
Mar 18 03:23:27 washburn simba-1: generated partiy error.
Mar 18 03:23:27 washburn simba0: PBM generated system error.
Mar 18 03:23:27 washburn simba-0: generated partiy error.
Mar 18 03:23:27 washburn pci0: PCI SERRpci0: PBM detected parity error.

I've searched the sun-managers archives as well as SunSolve but can't seem
to find any info about these errors. Has anyone seen similar errors before?
If so, can ya let me know which piece of the machine is having problems?
Usually when I've seen parity errors it's been a problem with memory, but
in this case it's not showing the errors I'm used to seeing when I've
seen the parity errors.

Any info would be greatly appreciated! Thanks!

-Gary

Gary Richardson
Sr. Unix Administrator
Watercove Networks, Inc.
Email: grichardson at watercove.com

_______________________________________________
codeprof mailing list
codeprof at codeprof.com
http://www.codeprof.com/execute/ask/?codeinfoid=2487

Comments

Got something to say?

You must be logged in to post a comment.