"A process will continually scrub the memory, and is capable of correcting any
one error per 64-bit word of memory."
at http://www.stringliterals.com/?tag=opensolaris.
If this is true what is the process and how is it accessed?
--
This message posted from opensolaris.org
___
Simon, when I call:
~$ smbios -t SMB_TYPE_MEMARRAY
I receive:
ID SIZE TYPE
47 15 SMB_TYPE_MEMARRAY (physical memory array)
Location: 3 (system board or motherboard)
Use: 3 (system memory)
[b]ECC: 6 (multi-bit ECC)[/b]
Number of Slots/Sockets: 6
Memory Error Data: Not Supported
Max Capacity: 2576
Yes, you are correct. Thanks.
--
This message posted from opensolaris.org
___
zfs-discuss mailing list
zfs-discuss@opensolaris.org
http://mail.opensolaris.org/mailman/listinfo/zfs-discuss
Thanks for the info everyone!
I will now setup scrubbing and verify ecc alerts.
Miles, AMD and intel's new xeon with the integrated memory controller ought to
behave and interact with opensolaris the same way, yes?
--
This message posted from opensolaris.org
___
Is there a method to view the status of the rams ecc single or double bit
errors? I would like to confirm that ecc on my xeon e5520 and ecc ram are
performing their role since memtest is ambiguous.
I am running memory test on a p6t6 ws, e5520 xeon, 2gb samsung ecc modules and
this is what is o
