APLawrence.com -  Resources for Unix and Linux Systems, Bloggers and the self-employed

Unix (3.2v4.2) and ODT FAQ

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.

My SCO Unix machine had a panic. How do I find out why?

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.

Got something to add? Send me email.

(OLDER)    <- More Stuff -> (NEWER)    (NEWEST)   

Printer Friendly Version

-> My machine had a panic. How do I find out why? (SCO Unix)

Printer Friendly Version

Have you tried Searching this site?

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.

Contact us

Printer Friendly Version

Writing in C or C++ is like running a chain saw with all the safety guards removed. (Bob Gray)


Unix/Linux Consultants

Skills Tests

Unix/Linux Book Reviews

My Unix/Linux Troubleshooting Book

This site runs on Linode