HP-UX Virtual Partitions Release Notes (A.04.03)

Known Problems and Workarounds
On sx2000 Integrity Servers, Booting an OS Kernel while in the Wrong Mode May Cause a Panic Instead of
Displaying Error Messages
Chapter 3 21
On sx2000 Integrity Servers, Booting an OS Kernel while in
the Wrong Mode May Cause a Panic Instead of Displaying
Error Messages
Related JAG or Patch ID Number
JAGag06132
Applicable on
❏ vPars A.04.02, A.04.03 on Integrity
Description
On Integrity servers, if you are in vPars mode but instead boot the OS
Kernel (boot vmunix) instead of the vPars Monitor (boot vpmon), normally
an error message is displayed on the console. However, instead of the error
message, you may receive a system panic.
Symptoms
The system panic displays messages similar to the following
EFI\HPUX\AUTO ==> boot vmunix
................
Launching /stand/vmunix
SIZE: Text:29561K + Data:7016K + BSS:7128K = Total:43705K
Console is on virtual console
Booting kernel...
Stored message buffer up to panic:
5028, 0x11, 0x40).
pinned_pdk_malloc_avail_contig(): 0x33000
Bad News: Cannot use the Kernel Stack when interrupted on the ICS.
Bad News: Fault/trap with interrupts disabled and we cared.
reg_dump(): Displaying register values (in hex) from the save state
...
System Panic:
double panic: Bad News!
Workaround
After the system comes back up, make sure the system is in your desired
mode (vPars or nPars) and boot the appropriate item (vpmon for vPars mode
and vmunix for nPars mode).