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

Applicable on vPars A.04.xx on Integrity
Description On Integrity servers, if you are in vPars mode and you boot the OS Kernel
(boot vmunix) instead of the vPars Monitor (boot vpmon), an error message is typically
displayed on the console. You may, however, receive a system panic message, instead of an
error message.
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 the mode you
want (vPars or nPars), then boot the appropriate item (vpmon for vPars mode and vmunix
for nPars mode).
• Booting of Monitor Fails After a LAN Boot is Attempted
Related JAG or Patch ID Number JAGaf62265
Applicable on vPars A.04.xx on Integrity
Description Booting the vPars Monitor fails after a LAN boot is attempted.
Symptoms If a boot of the vPars Monitor is attempted after a failed LANboot, the vPars
Monitor boot fails with the an error message similar to the following:
HPUX> boot vpmon
> System Memory = 223 MB
Could not allocate enough memory for Kernel.
kernel loading failed
Workaround Do either of the following:
— Perform a reboot of the nPartition using the parconfig reset command
— Install patch PHKL_34088 or later
• Panic Caused by Unequal Amounts of Allocated ILM
Related JAG or Patch ID Number JAGaf64296
Applicable on vPars A.04.xx on PA
Description Unequal amounts of ILM allocated from cells may cause a system panic.
Symptoms The system panics when unequal amounts of ILM are allocated from the cells
to the nPartition. In other words, each cell is not providing an equal amount of ILM to the
nPartition. While booting the kernel, you may see the following error message:
Can't allocate mem for pfdats
Workaround Install both of the following patches:
— Patch PHKL_33929 or later
— Patch PHKL_33930 or later
Known Problems and Workarounds 13