In most cases, the PANIC error message is displayed on the console. Look in the /var/adm/log/osmlog file for other messages that preceded the panic and may contain valuable information about what went wrong.
Kernel error messages report driver errors and errors in other parts of the kernel such as the process scheduling subsystem and the file subsystem. Monitoring these message regularly is an important step in preventing serious system problems; studying these messages after a system problem develops is an important part of troubleshooting the system. Reading the PANIC error message can give valuable information about the cause of the system failure.
Kernel error messages usually have the format:
class: [ddname:] [routine] messageclass is usually one of the following: CONFIG, NOTICE, WARNING, FATAL, or PANIC. Messages that have INIT for class are generated by the init(1M) process. These messages usually occur during system initialization. A few of the init messages indicate error conditions, but many more are just informational messages.
ddname names the driver or subsystem having problems.
The actual peripheral is usually identified by a pair of numbers
of the form major/minor.
This identifies the device number of the peripheral
where the error occurred.
The routine element indicates
the subsystem that detected the condition;
these portions of the error message
are included mostly to help support staff
in tracking difficult system problems.
PANIC messages are not usually logged in the /var/adm/log/osmlog file, but other messages that occurred before the panic are usually logged and can provide valuable information about the cause of the panic. The PANIC message is usually displayed on the system console or can be viewed with the panic function of the crash(1M) command.