Installing and Managing HP-UX Virtual Partitions (includes A.04.02)

Crash Processing and Recovery
Crash Processing
Chapter 9
232
Crash Processing
Crash processing for a virtual partition is similar to the crash processing of a non-vPars OS: the OS is
quiesced, portions of memory are written to disk, and in the case of vPars, resources are released to the
Monitor.
When the Monitor crashes, a Monitor dump is created. By default, kernel dumps are not saved.
When there is a HPMC or MCA or when a TOC is issued, the virtual partitions are launched for crash
processing. On PA-RISC, this occurs after saving the Monitor dump, and on Integrity, this occurs before
saving the Monitor dump.
When you enter the crash user interface:
• To let the crash processing continue, do nothing.
• To enter the crash user interface, press any key on the console.
NOTE HP recommends that you let crash processing continue.
Crash User Interface
If you enter the crash user interface, you will see messages similar to the following on the console:
Virtual Partition Activity at Time of Crash
partition 0 (vpar1): active
partition 1 (vpar2): active
partition 2 (vpar3): inactive
The active partitions will be invoked to perform
crash handling. A soft reset will then be generated
to allow additional debugging.
TO OVERRIDE THIS BEHAVIOR, PRESS A KEY WITHIN 10 SECONDS....
CRASH PROCESS STOPPED.
Crash Command Menu
1. Examine memory contents
2. Continue with default crash handling
3. Cause Monitor crash dump to different device
4. Soft reset the machine (memory preserved)
5. Hard reset the machine (memory not preserved)
6. Launch partition 0 (vpar1) for crash processing
7. Launch partition 1 (vpar2) for crash processing
Enter number (1-7):
The menu choices mean:
1. displays memory from <
starting address > for < n > 32-bit words. For example:
Enter Address: 0x1000 4
0x00001000 0x00000000 0x1200a000 0xaa400000 0x00000000
Enter Address: quit
2. continues with the default crash handling