Installation guide

LP_ERROR: no IOP for partition (check lp_io_mask)
The value of lp_io_mask# (# represents the current partition
number) is set incorrectly. There are no IO Port modules allocated to
this partition.
LP_ERROR: lp_count > 1, but partitions not initialized
Please execute ’lpinit’ command at >>> prompt
The message indicates that partitions were configured, but not
initialized.
LP_ERROR: must set lp_mem_mode [share or isolate]
The lp_mem_mode console EV is not set or set incorrectly. For logical
partitions, lp_mem_mode must be set to isolate.
Bootstrap address collision, image loading aborted
The kernel’s link address does not match the memory starting
address of the partition. Refer to section Section E.4.8 for instructions
on how to recover from this error.
E.4.11 Understanding Console Firmware Error or Informational
Messages
The console firmware implements several safety checks during certain
events (such as system reset and partition startup). These checks help
prevent cross-partition interference. If an anomaly is detected, one of the
following messages will be displayed on the partition’s console:
Do you really want to reset ALL partitions? (Y/<N>)
This message displays when a system reset has been requested, either
by the operation issuing the init command or as a result of booting
with the boot_reset console EV set to ON. This message is a
warning that if you continue with the reset it will immediately
terminate all partitions and completely reset the system. If a reset is
necessary, shut down the operating system in all operational
partitions before proceeding with the reset.
Auto-Starting secondary partitions...
This message indicates the console firmware is automatically
initializing logical partitions, that is, it automatically executed the
lpinit command. Auto starting occurs after a system reset (or power
on). The console firmware will also boot the operating system in all
partitions if the auto_action console EV is set to BOOT and the
Administering Specific Hardware E–33