Fault.memory.memlink-Uc Fault Did Not Cause Panic As Stated By System Message (Cr 6940599); Timestamp For An Oracle Ilom Fault/Critical Event Might Be Off By One Hour (Cr 6943957) - Sun Oracle Netra SPARC T4-1B Product Notes

fault.memory.memlink-uc Fault Did Not
Cause Panic as Stated by System Message
(CR 6940599)
When a fault.memory.memlink-uc interconnect fault is detected, the server
module should shut down to protect memory integrity. On intermittent occasions,
this fault has been reported during boot operations without the server module
shutting down.
Although this irregular behavior might indicate that the system was able to recover
from the memory link error and restore a healthy boot-up state, the safest course is to
power down, then power up the server module.
Recovery Action: Log into Oracle ILOM on the SP and power cycle the host.
-> stop /SYS
Are you sure you want to stop /SYS (y/n)? y
Stopping /SYS
-> start /SYS
Are you sure you want to start /SYS (y/n) ? y
Starting /SYS
Timestamp for an Oracle ILOM Fault/Critical
Event Might Be off by One Hour (CR 6943957)
The timestamp reported in an email generated in an Oracle ILOM fault/critical event
might be one hour later than the timestamp recorded in the event log.
Workaround: Check the timestamp recorded in the event log. If that timestamp does
not match the timestamp reported in the email, use the event log time.
Known Product Issues 19