Sun Microsystems Sun Fire V440 Diagnostics And Troubleshooting Manual page 144

About Unexpected Reboots
Sometimes, a system might reboot unexpectedly. In that case, ensure that the reboot
was not caused by a panic. For example, L2-cache errors, which occur in user space
(not kernel space), might cause Solaris software to log the L2-cache failure data and
reboot the system. The information logged might be sufficient to troubleshoot and
correct the problem. If the reboot was not caused by a panic, it might be caused by a
Fatal Reset error or a RED State Exception. See "How to Troubleshoot Fatal Reset
Errors and RED State Exceptions" on page 142.
Also, system ASR and POST settings can determine the system response to certain
error conditions. If POST is not invoked during the reboot process, or if the system
diagnostics level is not set to max, you might need to run system diagnostics at a
higher level of coverage to determine the source of the reboot if the system message
and system console files do not clearly indicate the source of the reboot.
How to Troubleshoot a System With the
Operating System Responding
Before You Begin
Log in to the system controller and access the sc> prompt. For information, see:
"About the sc> Prompt" on page 169
This procedure assumes that the system console is in its default configuration, so
that you are able to switch between the system controller and the system console.
See:
"About Communicating With the System" on page 164
"Access Through the Network Management Port" on page 168
126 Sun Fire V440 Server Diagnostics and Troubleshooting Guide • July 2003