This article is from a FAQ concerning SCO operating systems. While some of the information may be applicable to any OS, or any Unix or Linux OS, it may be specific to SCO Xenix, Open This is an old article about SCO Unix and is only left here for historical purposes. There is lots of Linux, Mac OS X and general Unix info elsewhere on this site: Search this site is the best way to find anything.
There are a number of situations which can cause panics. First off, write down the actual panic message displayed on the screen when the machine crashed. Also, write down the values of CS and EIP from the register dump.
Next, reboot the system into single-user mode and run the
following command to produce a panic report:
echo panic -w /tmp/panic.out | crash -d /dev/swap
This produces a report in the file /tmp/panic.out. With the original panic message and this report, someone may be able to help you; without this information, it's just about impossible to say what went wrong. In particular the section of the report listing the kernel stack may be useful in diagnosing what caused the panic.
If you found something useful today, please consider a small donation.
Got something to add? Send me email.
It is the the duty of a Webmaster to allocate URIs which you will be able to stand by in 2 years, in 20 years, in 200 years. (Tim Berners-Lee)