Technical data

System Dump Analyzer
SHOW CPU
Spinlocks currently owned by CPU 00
IOLOCK8 Address : 80185E50
Owner CPU ID : 00 IPL : 08
Ownership Depth : 0001 Rank : 14
CPUs Waiting : 0000 Index : 34
SDA> EXAMINE R5
R5: 8047FC40 "@üG."
SDA> SHOW PROCESS
Process index: 000D Name: NETACP Extended PID: 33C0010D
-----------------------------------------------------------
Process status: 00148001 RES,NOACNT,PHDRES,LOGIN
.
.
.
SDA> SHOW CPU 01
CPU 01 Processor crash information
----------------------------------
CPU 01 reason for Bugcheck: CPUEXIT, Shutdown requested by another CPU
Process currently executing: no processes currently scheduled on this CPU
Current IPL: 31 (decimal)
.
.
.
No spinlocks currently owned by CPU 01
SDA> EXAMINE R5
R5: 83ED5E00 ".^í."
SDA> SHOW PROCESS
%SDA-E-BADPROC, no such process
This SDA session illustrates the output of the SHOW CPU command in the
analysis of a crash dump from a VAX 8800 multiprocessing system with two
active processors. The first SHOW CPU command displays the crash information
particular to CPU 00, which initially posted an INVEXCEPTN bugcheck from
within process NETACP and then requested CPU 01 to take a bugcheck
(CPUEXIT) as well. That the crash occurred at IPL 8 signifies, perhaps, that
a driver fork process is involved.
The second instance of the SHOW CPU command (SHOW CPU 01) corroborates
that CPU 01 was requested to crash by CPU 00.
Significantly, the second SHOW CPU command changes both the SDA current
CPU context and current process context. The two EXAMINE R5 commands are
executed under different CPU contexts; the values they produce differ. In the
CPU context of CPU 00, the current process context is that of process NETACP.
There is no current process on CPU 01; thus, SDA process context is initially
undefined when its CPU context is changed to that of CPU 01.
SDA–97