3-32 Troubleshooting
MPE/iX Monitor Halts
A monitor halt can be caused by either software or hardware. The console may not show a message
describing the condition. The sequence of hex codes that begins with a "Bx00" distinguishes it from the
Bx07 (system halt 7) code of a system abort. Use the procedures in Table 3-18. on page 3-32 to resolve the
problem.
MPE/iX System Abort
A system abort is a condition experienced by the operating system in which either system or data integrity
may be compromised by continued operation. While the causes of system aborts are many, the result is
always the same: the system immediately halts and displays system abort information on the physical
console (Ldev 20). All user activity stops.
A system abort message typically has the following format:
SYSTEM ABORT xxxx FROM SUBSYSTEM xxxx
SECONDARY STATUS: INFO = xxxx, SUBSYS = xxx {this line may not appear}
SYSTEM HALT 7, $xxxx
Use the recovery procedures in Table 3-19. on page 3-32 to resolve the problem.
If you have a system abort message on the console, it is probably unnecessary to copy down the hex display
pattern. However, if there was nothing printed on the console AND the hex display looks like that above (it
includes a "Bx07" sequence) then you have probably experienced a system abort which did not identify
itself on the console display. In this case, write the codes down. The Response Center can determine the
system abort number from this information.
Table 3-18. Monitor Halt Troubleshooting
Symptoms
Recovery Procedure
System halts
1. Record error message on console if one appears.
2. Record the sequence of 4-digit codes at bottom of console display
(Press Control-B first.).
3. Take a memory dump. Refer to the Performing a Memory Dump
section for more information.
4. Restart the system when dump is finished.
All user activity stops.
No message on console (usually).
Sequence of 4-digit codes at bottom of
console display. (Press Control-B first.)
One of the codes is Bx00.
Table 3-19. System Abort Troubleshooting
Symptoms
Recovery Procedure
System halts ("System Halt 7" message).
1. Record entire system abort message on console.
2. Record the sequence of 4 digit codes at bottom of console
display. (Press Control-B first.)
3. Perform a memory dump.
4. Restart the system when dump is finished.
All user activity stops.
System abort message on console (usually).
Sequence of 4 digit codes at bottom of console
display. (Press Control-B first.)
Summary of Contents for 3000/9x9KS Series
Page 14: ...xiv Contents E Sources of Information on the Web ...
Page 28: ...2 8 Install and Configuration Figure 2 4 HP PB I O Slot Location Diagram Kx70 Kx80 ...
Page 44: ...2 24 Install and Configuration ...
Page 68: ...3 24 Troubleshooting HP 3000 Core I O Figure 3 4 HP 3000 Core I O ...
Page 120: ...5 6 Diagnostics ...
Page 128: ...6 8 Replaceable Parts Figure 6 4 Peripheral Bay Expanded View ...
Page 136: ...6 16 Replaceable Parts ...
Page 150: ...7 14 Removal and Replacement Figure 7 11 Peripheral Bay Rear View ...
Page 180: ...7 44 Removal and Replacement Figure 7 35 Cabinet Exploded View Rear ...
Page 209: ...SCSI and I O 8 21 Figure 8 3 A3629A ST19171WD J2 and J6 Jumper Settings ...
Page 217: ...SCSI and I O 8 29 Figure 8 7 A3353A source 2 J3 Jumper Positions ...
Page 218: ...8 30 SCSI and I O Figure 8 8 A3353A source 2 Option Connector Jumper Positions ...
Page 280: ...8 92 SCSI and I O Diagnostics CSTM SCSIDDS SYSMAP IOMAP ...
Page 298: ...8 110 SCSI and I O Diagnostics SCSICD IOMAP SYSMAP ...
Page 302: ...8 114 SCSI and I O ...
Page 308: ...Support Information B 2 HP 9x9KS Block Diagram Figure B 1 HP 3000 9x9KS Block Diagram ...
Page 309: ...B 3 Support Information HP K100 Block Diagram Figure B 2 HP 9000 K100 Block Diagram ...
Page 310: ...Support Information B 4 HP K2x0 K4x0 Block Diagram Figure B 3 HP 9000 K2x0 K4x0 Block Diagram ...
Page 311: ...B 5 Support Information Kx70 Kx80 Block Diagram Figure B 4 HP9000 Kx70 Block Diagram ...
Page 342: ...Memory Configuration Guidelines C 16 ...
Page 350: ...D 8 New System Features ...