LNEXT
ONELCLEAN
UTERMINAL
TERMINAL
NEXT
$V1$
HILINE
PAUSE
CRASH1
|^^^^^^^^^^| | |
| | | TERMINAL |
| TERMINAL | | |
| | | |
-----------\ ------------
// \ ---------| |
__________________ \ | _______________________
/ - - - - - / | | \ - - - - - - - - \
/_________________/ | | _____________________\
| |
-------------------------
---------Terminal
COMPUTER
\\
|^^^^^^^^^^| | |
| | | TERMINAL |
| TERMINAL | | |
| | | |
-----------\ ------------
// \ ---------| |
__________________ \ | _______________________
/ - - - - - / | | \ - - - - - - - - \
/_________________/ | | _____________________\
| |
------------------------- | |
---------| Terminal|
COMPUTER | |
\\
CRASH2
Interrupt from unknown device, vec=0x78AC9948A
Panic: unknown interrupt:
Hardware:
CRASH3
|^^^^^^^^^^| | |
| | | TERMINAL |
| TERMINAL | | |
| | | |
-----------\ ------------
// \ ---------| |
__________________ \ | _______________________
/ - - - - - / | | \ - - - - - - - - \
/_________________/ | | _____________________\
| |
-------------------------
---------Terminal
COMPUTER
\\
GO
A system crash is a serious system malfunction, which halts
system execution and permits no further work by the users!
A system crash may result from software as well as hardware
errors!
Your ability to diagnose the problem will depend on your
experience and on the diagnostic message printed on the system
console (if any).
This tutorial is not intended to teach you how to solve all
of your system problems, but rather to provide some examples.
The list of system error messages can be found
in Section V of your UNIX User's Guide under messages!
in (Section M) of your UNIX User's Reference Manual!
under crash in Section 8 of your UNIX User's Reference Manual!
These serve as useful pointers, and you should try to understand them.
The crash information (if any) printed on the console serves as a guide
for your UNIX software support organization, so please keep a log of it.
Once a crash has occurred, you cannot check much because your
console and terminals are not responding. If your hardware
is functional, you should be able to reboot the system (many
systems will reboot automatically). If the system crashes
continuously, then you must do more than just reboot it.
If the cause of the crash is uncertain, but was precipitated by
running a program written in-house, then you should check the
privileges of the users of the program, and whether setuid
is being executed by them. It is possible that the program does low
level system calls that can cause system crashes.
Another problem that almost invariably results in a system crash is
an incorrectly configured system. An incorrect configuration for
the memory and/or disk size, or incorrect hardware interfaces can
cause system crashes. System reconfiguration and eventual
reloading can restore the system to normal operation!
Often you will need to reboot the system after a crash. Many larger
systems may reboot automatically. Once the system is restored to
normal operation, you should look in the /usr/adm/messages
file for various system error messages that can serve as a clue for
the cause of the system crash!
If you can read crash dumps, then you can set up a system to produce a crash
dump when a crash occurs! Don't panic. If your console message is of
no use, check all hardware connections and try to reboot before calling
your support representative. Be realistic about the problems, their
implications, and your capabilities. Every problem has a solution.