Studying a panic
The following list outlines the process for determining which kernel component
caused a system panic.
When the system panics, write down the messages displayed
and enter them in your system log book.
When the machine reboots,
save the kernel dump that is on the dump device
as shown in
``Saving the system dump memory image''.
Put the machine in single-user mode.
on the image.
Use the panic command in crash
to find the routine in which the panic happened.
Note the name (symbol name) of the routine that was executing
when the system panicked.
Quit the crash command.
to determine the driver in which that routine is located.
You can run a script such as the following,
which uses strings.
for FILE in `find /etc/conf/pack.d -name '*.[oa]' -print`
strings $FILE | grep $1 && echo $FILE
If this script were installed as findpanic,
you would run it with one argument
that gives the name of the kernel routine:
This script will output something like:
This indicates that the foo driver
may have been responsible for the system panic.
Additional help from your provider
Examining a memory dump with crash(1M)
© 2004 The SCO Group, Inc. All rights reserved.
UnixWare 7 Release 7.1.4 - 22 April 2004