Technical data
System Dump Analyzer
SHOW CRASH
• Identity of the system, including an indication of its VAXcluster membership
and the location of the primary CPU in a multiprocessing configuration.
• CPU IDs of both the primary CPU and the CPU that initiated the bugcheck.
In a uniprocessor system, these IDs are identical.
• Two bit masks indicating which processors in the system are active and which
are available for booting, respectively.
• For each active processor in the system, the name of the bugcheck that
caused the failure. Generally, there will be only one significant bugcheck
in the system. All other processors typically display the following as their
reason for taking a bugcheck:
CPUEXIT, Shutdown requested by another CPU
Subsequent screens of the SHOW CRASH command display information about
the state of each active processor on the system at the time of the system failure.
The information in these screens is identical to that produced by the SHOW CPU
command, including the general-purpose registers, processor-specific registers,
stack pointers, and records of spin lock ownership. The first such screen presents
information about the processor that caused the crash; others follow according to
the numerical order of their CPU IDs.
Examples
1.
$ ANALYZE/SYSTEM
OpenVMS VAX System analyzer
SDA> SHOW CRASH
System crash information
------------------------
Time of system crash: 25-FEB-1993 11:18:06.84
Version of system: OpenVMS VAX VERSION 6.0
System Version Major ID/Minor ID: 10/11
VAXcluster node: BIGTOP, a VAX 8800 - primary CPU (left) was booted
Primary CPU ID: 01
Bitmask of CPUs active/available: 00000003/00000003
SDA> SHOW PROCESS
%SDA-E-BADPROC, no such process
When issued from within the analysis of a running system, the SHOW
CRASH command displays the time the ANALYZE/SYSTEM command
was issued as the ‘‘Time of system crash.’’ The display indicates that the
OpenVMS VAX system in use is a VAX 8800 multiprocessing system, the left
CPU of which is the primary CPU. The bit mask indicates that there are two
processors available and both are running.
Note that no SDA current process is defined at this time.
SDA–99