Dynamic Reconfiguration User's Guide 2.5.1

6.2.2.4 Memory Messages

Message	nodeid (0xX) is not memory node
Cause	Failed to get device type.
Remedy	When a memory nullified system board is attached, this message always appears. This message can be ignored in such a case. It the message comes out in other cases, please contact our customer service.

Message	no board number for nodeid (0xX)
Cause	Failed to get the system board number from the firmware. There may be inconsistency in the system.
Remedy	Please contact our customer service.

Message	board # memlist already present in phys_install
Cause	Internal data conflict is detected. DR driver internal data conflict may be the cause.
Remedy	Please contact our customer service.

Message	protocol error: mem-unit (#.#) not released
Cause	Memory release did not successfully complete.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	protocol error: mem-unit (#.#) missing target indicator
Cause	Memory release did not successfully complete.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	invalid state transition for mem-unit (#.#)
Cause	Invalid memory device status.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	kphysm_del_status
Cause	Memory release did not successfully complete.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	mem-unit (#.#) release in-progress
Cause	Releasing the memory.
Remedy	Wait several minutes more. Release operation may wait for completing I/O. It is better to reduce system load, if you can. If this error message appears again after a while, try cancel operation and re-execute from the beginning.
Output	Console and Standard Output

Message	internal error: no memlist for board #
Cause	Detect the conflict of memory unit information. DR driver internal data conflict may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	address (0xX) not on page boundary
Cause	Internal data conflict is detected.
Remedy	Please contact our customer service.

Message	size (0xX) not on page boundary
Cause	Internal data conflict is detected.
Remedy	Please contact our customer service.

Message	failed to add back (base=0xX, npgs=0xX) = #
Cause	Failed to add back the memory.
Remedy	Please contact our customer service.

Message	failed to add back to cage (base=0xX, npgs=0xX) = #
Cause	Failed to add back the memory information to the internal data.
Remedy	Please contact our customer service.

Message	unexpected state (#) for mem-unit (#.#)
Cause	The memory status does not allow to connect the memory. This is DR driver internal data conflict.
Remedy	Check if more than one DR operations have been executed in parallel.
Output	Console and Standard Output

Message	kcage_range_add failed. (#)
Cause	Detect the internal data conflict or lack of memory resource. Memory cannot be connected to the active OS.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	kphysm_add_memory_dynamic failed. (#)
Cause	Failed to connect the memory to the active OS.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	failed to quiesce OS for copy-rename
Cause	Failed to suspend the system.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	mem-unit (#.#) memlist not in phys_install
Cause	Memory unit information was not put in internal data. DR driver internal data conflict may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	kernel cage is disabled
Cause	Kernel cage memory function is disabled.
Remedy	Ensure /etc/system is edited to enable kernel cage memory. (See "2.3.1 How to enable DR and Kernel cage memory")
Output	Console and Standard Output

Message	devlist[#] empty (expected #)
Cause	Memory unit cannot be found.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	ineligible mem-unit (#.#) for detach
Cause	The system board you chose is already used as the target system board of another detach operation.
Remedy	Check if another DR operation is in progress. If not, repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	protocol error: kphysm_del_span_query [bd=#, bp=0xX, n=#]
Cause	Internal data conflict detected in the system.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	no available target for mem-unit (#.#)
Cause	Candidate system board for the memory copy cannot be found.
Remedy	There is no candidate system board in the partition. If possible, connect new system board with same memory configuration as the outgoing system board.
Output	Console and Standard Output

Message	unable to allocate memhandle for mem-unit (#.#)
Cause	Internal data conflict detected in the system.
Remedy	Please contact our customer service.

Message	kcage_range_delete(0xX, 0xX)=#, failed
Cause	Failed to setup destination system board for memory copy.
Remedy	Please contact our customer service.

Message	kphysm_del_span (0xX, 0xX) = #, failed
Cause	Internal data conflict detected in the system.
Remedy	Please contact our customer service.

Message	kphysm_del_span_query(0xX, 0xX) failed
Cause	Internal data conflict detected in the system.
Remedy	Please contact our customer service.

Message	no memlist for mem-unit (#.#)
Cause	Detected conflict of the memory unit information in DR driver's internal data.
Remedy	Please contact our customer service.

Message	Can't get nuclues base address
Cause	Internal data conflict detected in the system.
Remedy	Please contact our customer service.

Message	obp-memory: can't get the property for node 0xX
Cause	Failed to get the memory information from the firmware.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.

Message	no ###### property for node (0xX)
Cause	Failed to get the system board number from the firmware. There may be inconsistency in the system.
Remedy	Please contact our customer service.

Message	failed to attach mem node branch to node tree. (error=#)
Cause	Failed to connect the memory to the OS.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.

Message	failed to detach mem node branch (######) from the node tree. (error=#)
Cause	Failed to remove the memory node from OS.
Remedy	Please contact our customer service.

Message	fail to initialize device information.
Cause	Failed to initialize device information.
Remedy	Please contact our customer service.

Message	failed to get memhandle for nodeid 0xX
Cause	Internal data conflict detected in the system.
Remedy	Please contact our customer service.

Message	mem-unit (#.#) has non-relocatable page(s).
Cause	Target memory contains kernel memory or failed to reserve detached memory.
Remedy	Repeat the action. If this error message appears again, please contact our customer service.
Output	Console and Standard Output

Message	sfdr_get_memlist: can't get memlist on board #.
Cause	The system failed to get the memory information on that board. Internal data conflict in DR driver or Firmware may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	sfdr_post_detach_mem_unit: can't get fma-ranges. No remaining memory is attached.
Cause	Internal data conflict is detected. DR driver internal data conflict may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	sfdr_post_detach_mem_unit:can't get s_basepa from 0xX
Cause	Internal data conflict is detected. DR driver internal data conflict may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	sfdr_post_detach_mem_unit:can't get t_basepa from 0xX
Cause	Internal data conflict is detected. DR driver internal data conflict may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output

Message	sfdr_pre_release_mem: no available target for mem-unit (#.#). The candidate has no-obp-sb-cX.
Cause	The system board to which the kernel memory can be copied was found. However, because of no-obp-sb-cX, it couldn't be a candidate.
Remedy	If you intentionally want to move the kernel memory to the board with no-obp-sb-cX by the drc command, please reply Yes to the inquiring message. (Please refer to section 6.1.3.3 "Inquiring Messages" in detail) When using the adrc command, because "No" is always replied automatically, please use the drc command instead. If you don't want to move the kernel memory to the board with no-obp-sb-cX, please change the system configuration.
Output	Console and Standard Output

Message	sfdr_move_memory:can't get fma-ranges on board #.
Cause	The system failed to get the memory information on that board. Internal data conflict in DR driver or Firmware may be the cause.
Remedy	Please contact our customer service.
Output	Console and Standard Output