Dynamic Reconfiguration User's Guide 2.5.1 |
Contents
![]() |
Chapter 7 Messages and DR Error Conditions on Solaris 9 OS and Solaris 10 OS | > 7.2 Console Messages | > 7.2.2 Message Explanation |
Message |
|
Explanation |
Detect the lack of memory resource. |
Remedy |
Detach the board and attach this board again. |
Message |
can't delete kernel cage occupied span; basepfn = X, npages = Y |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
Failed to allocate due to lack of the memory resource |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
Failed to attach the DR driver. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
dr_add_memory_spans: unexpected kphysm_add_memory_dynamic return value X; basepfn=Y, npages=Z |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
Fail to disable interrupt on CPU X. |
Remedy |
Disable interrupt on cpu X with psradm -I and if this command fails again, |
Message |
|
Explanation |
Fail to online CPU X. |
Remedy |
Repeat the action. |
Message |
|
Explanation |
Fail to power-on cpu X |
Remedy |
Repeat the action. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
The thread in the process is bound to the detached CPU X. |
Remedy |
Check if the process bound to the CPU exists by pbind(1M) command. If it exists, unbind from the CPU and repeat the action. |
Message |
dr_pre_release_mem: unexpected kphysm_del_release return value # |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
dr_release_mem_done: mem-unit (X.Y): deleted memory still found in phys_install |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
dr_release_mem_done: target :mem-unit (X.Y): deleted memory still found in phys_install |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
dr_release_mem_done: unexpected kphysm_del_release return value # |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
The selected target board can no longer fit all the kernel memory of the source board since it was last selected. |
Remedy |
Please repeat the action. If the problem remains, please contact our customer service. |
Message |
|
Explanation |
Detected a degraded device. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
The board is connected. |
Remedy |
Please check the board status and if board is disconnected please |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
The board is not connected. |
Remedy |
Please check the board status and if board is connected please contact |
Message |
drmach_board_deprobe: cpu (X) on board (Y) has bad state (#). |
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be minor error in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Detected inconsistency of the memory unit information in DR driver's internal data. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Device suspension failed |
Remedy |
Repeat the action. If the message persists, please contact our customer service. |
Message |
|
Cause |
The device cannot be resumed. |
Remedy |
Please contact our customer service. |
Message |
dr_stop_user_threads: failed to stop thread: process=<name>, pid=# |
Cause |
Cannot stop the user thread. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
The DR driver cannot stop all the user process in the list |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Kernel data migration failed as a result of DR detach. |
Remedy |
Please contact our customer service |
Message |
ngdrmach:drmach_board_deprobe: fjsv_memecc_kstat_delete: wrong board number X |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service |
Message |
ngdrmach:drmach_board_deprobe: fjsv_u2ts_kstat_delete: wrong board number X |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service |
Message |
ngdrmach:drmach_board_deprobe: fjsv_u2_ecc_kstat_delete: wrong board number X |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service |
Message |
ngdrmach:drmach_board_deprobe: fjsv_upa_ecc_kstat_delete: wrong board number X |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service |
Message |
|
Cause |
Time of Date Clock on board X has been attached. This may be a minor inconsistency in the system. |
Remedy |
Please contact our customer service |
Message |
|
Cause |
Time of Date Clock on board X has been removed. This may be a minor inconsistency in the system. |
Remedy |
Please contact our customer service |
Message |
|
Cause |
Detaching the system board will result in detaching the last available Time of Date clock. |
Remedy |
Attach another system board before detaching. |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the system. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid argument is passed to the driver. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the system. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid argument is passed to the driver or there may be inconsistency in the system. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to get the property from OBP |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to get the property from OBP |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to get the property from OBP. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to get the property from OBP. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Some devices are still referenced. |
Remedy |
Confirm that all devices in this pci slot are not in use and repeat the action. |
Output |
Console and Standard Output |
Message |
|
Explanation |
The device driver failed in attach or detach operation. |
Remedy |
Repeat the action. If this error message appears again, please contact |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to off-line CPU Y on board X. |
Remedy |
Repeat the action. If this error message appears again, please contact |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to online CPU Y on system board X. |
Remedy |
Online CPU with psradm(1M) -n. If it fails to online CPU, and if this command fails again, respond in the manner directed by command message. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to start CPU Y on system board X. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to stop CPU Y on system board X. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to deprobe the board. |
Remedy |
Respond in the manner directed by the other message. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to deprobe the CPU. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail to probe the board. |
Remedy |
Respond in the manner directed by the other message. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Detect the lack of memory resource. |
Remedy |
Check the size of memory, detach the board and attach again. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
The memory board X is currently involved in other DR operation and can't be detached. |
Remedy |
Repeat the action. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid board number. |
Remedy |
Check the board number and repeat the action. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Kernel cage memory feature 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 |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Operator confirmation for quiesce is required: dr@0:SBX::memory |
Explanation |
There is non-relocatable (kernel) memory on the board. |
Remedy |
The target board with kernel memory cannot be disconnected by DR. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Fail the pre-operation to call OBP. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
CPU Y on system board X is busy during release operation. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Undefined error occurred. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Undefined error occurred. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Detect the lack of memory resource. |
Remedy |
Check the size of available memory and detach the board. If the problem still exists, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid state transition of cpu Y on system board X |
Remedy |
Repeat the action. If the problem still exists, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid state transition of memory on system board X |
Remedy |
Repeat the action. If the problem still exists, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid state transition of pci Y on system board X |
Remedy |
Repeat the action. If the problem still exists, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
The operation to the cpu Y on system board X is in progress. |
Remedy |
Repeat the action. If the problem still exists, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There is a task not suspended in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
The system board cannot be detached because it contains kernel memory and there is no available target memory board. |
Remedy |
Add new system board and then try the detach operation again. |
Output |
Console and Standard Output |
Message |
|
Cause |
DR driver found DR unsafe drivers in the system. |
Remedy |
Unload the unsafe drivers and try the DR operation again. |
Output |
Console and Standard Output |
Message |
|
Cause |
Devices on the list failed to resume |
Remedy |
Please contact our customer service |
Output |
Console and Standard Output |
Message |
|
Cause |
Devices on the list failed to suspend |
Remedy |
Please contact our customer service |
Output |
Console and Standard Output |
Message |
ngdrmach:drmach_attach_board: fail to map the obp area <board #> |
Cause |
The firmware failed to set the information. |
Remedy |
Please contact our customer service. |
Message |
ngdrmach:drmach_attach_board: fail to connect board with the error = 0xX. |
Cause |
The firmware returned the error in the process, and the system recovered. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
Firmware cannot find node.: <devicename or todname> in fjsv_cdr_get_tod_address |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There is insufficient system memory left in the system to support the requirements in fjsv_cdr_get_tod_address. |
Remedy |
Reduce the system load and wait a while. Repeat the action. |
Output |
Console and Standard Output |
Message |
Cannot determine property length: PROM Node 0xX: property components in fjsv_cdr_get_tod_address. |
Cause |
Fail to get property from OBP |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Cannot read property value: PROM Node 0xX: property components in fjsv_cdr_get_tod_address. |
Cause |
Fail to get property from OBP |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Cannot determine property length: PROM Node 0xX: property address in fjsv_cdr_get_tod_address. |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Cannot read property value: PROM Node 0xX: property address in fjsv_cdr_get_tod_address. |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Cannot read property value: PROM Node 0xX: property fma-ranges. |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Cannot determine property length: PROM Node 0xX: property fma-ranges. |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
Cannot read property value: PROM Node 0xX: property dr-status |
Cause |
There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Explanation |
Invalid operation. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Contents
![]() |