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
Desktop or Openserver.
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.
For further information, consult TAs 480619 and 482035.
Enter your email address for automatic notification of new posts here
(be sure to whitelist 'feedburner.com' if you use spam filtering)
| Views for this page | ||||
|---|---|---|---|---|
| Today | This Week | This Month | This Year | Overall |
| 1 | 1 | 35 | 449 | 1,300 |
/SCOFAQ/FAQ_scotec3panic_why.html copyright 1997-2003 (various) All Rights Reserved
Have you tried Searching this site?
Unix/Linux/Mac OS X support by phone, email or on-site: Support Rates
This is a Unix/Linux resource website. It contains technical articles about Unix, Linux and general computing related subjects, opinion, news, help files, how-to's, tutorials and more. We appreciate comments and article submissions.
Add your comments