Troubleshooting Red State Exception Memory Errors
(Doc ID 1012214.1)
Last updated on NOVEMBER 24, 2020
Applies to:Sun Fire V890 Server - Version Not Applicable to Not Applicable [Release N/A]
Sun Fire V490 Server - Version Not Applicable and later
Sun Fire V880 Server - Version All Versions and later
Sun Fire V480 Server - Version Not Applicable and later
Sun Fire V880z Visualization Server - Version All Versions and later
When scanning error messages from any of the message files you will usually see the failing DIMM(s) being printed out for you, but when decoding a Red State Exception you won't have this luxury.
Debugging Red State Exceptions (w/ CE/UE errors) you must be able to manually decode the bad DIMM(s) from the AFSR and AFAR data given in the Red State Exception error output. This output is printed to the ttya port or the rsc console logs at the time of error.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!