Dynamic Reconfiguration User's Guide 2.5.1 |
Contents
![]() ![]() |
Chapter 6 Messages and DR Error Conditions on Solaris 8 OS | > 6.2 Console Messages | > 6.2.2 Message Explanation |
Message |
|
Cause |
Failed to get internal data for DR process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Cause |
Detected invalid internal data for DR. There may be a inconsistency in the system. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
The system board status does not allow the specified DR command. |
Remedy |
Check the system board status by drcstat command and re-execute correct DR command. |
Output |
Console and Standard Output |
Message |
|
Cause |
Invalid system board status for the command. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to perform platform dependent DR operation. There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to perform platform dependent DR operation. There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to perform platform dependent DR operation. There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Internal data conflict detected in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Specified system board is already connected. |
Remedy |
Check the system board status by drcstat command and re-execute correct DR command. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to get information from the firmware. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
The firmware failed to set the information. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to connect the system board. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Any device(s) cannot be found on the system board. |
Remedy |
Please check if more than one DR operations have been executed in parallel. Even if this is not the case and this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Real time class process was found. |
Remedy |
Stop real time process before DR operation or change to the other schedule class by priocntl(1M) command. |
Output |
Console and Standard Output |
Message |
|
Cause |
Fail to stop user process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Any device(s) cannot be found on the system board. |
Remedy |
Please check if more than one DR operations have been executed in parallel. Even if this is not the case and this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Invalid system board status. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
The firmware failed to set the information. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to disconnect the system board. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to suspend the system for memory copy. |
Remedy |
Check other error message at the same time. |
Message |
|
Cause |
Failed to stop kernel thread. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Received unknown command. |
Remedy |
Execute correct DR operation. If this error message appears again, please contact our customer service. |
Message |
|
Cause |
Failed to bring back the system board status to the previous status. There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to get kernel symbol due to internal data conflict. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to create minor node. This may be DR Driver internal error. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to perform platform dependent DR operation. There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to perform platform dependent DR operation. There may be inconsistency in the system. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to initialize platform dependent data structure. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Invalid node type device is found on the system board. |
Remedy |
Please check if more than one DR operations have been executed in parallel. Even if this is not the case and this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to get the unit number from the firmware. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
Cause |
Failed to create the device node. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to attach the DR driver. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Cause |
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 |
|
Cause |
Failed to initialize the platform depend data structure. |
Remedy |
Please contact our customer service. |
Message |
|
Cause |
Failed to attach the DR driver. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Message |
|
Cause |
Invalid system board number is specified. |
Remedy |
Check the system board number and repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
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 |
|
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 |
|
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 |
|
Cause |
Detected a degraded device. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
|
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 |
|
Cause |
Failed to create minor node. This may be DR driver internal error. |
Remedy |
Please contact our customer service. |
Message |
fjsv_alloc_map_area: can't alloc vmem. |
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 |
fjsv_alloc_map_area: can't find pagesize(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 |
fjsv_alloc_map_area: wrong pagesize(#). |
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 |
fjsv_cdr_add_fma_job: jobp or mlp is NULL. |
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 |
fjsv_cdr_add_fma_job: kmem_zalloc failed. |
Cause |
Allocating work memory failed in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
fjsv_cdr_alloc_cache_func: fjsv_cdr_get_scf_addr failed. |
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 |
fjsv_cdr_alloc_cache_func: fma size(0xX) is bigger than PAGESIZE. |
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 |
fjsv_cdr_alloc_cache_func: jobp is NULL. |
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 |
fjsv_cdr_alloc_cache_func: kmem_zalloc failed. |
Cause |
Allocating work memory failed in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
fjsv_cdr_alloc_cache_func: loop size(0xX) is bigger than PAGESIZE. |
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 |
fjsv_cdr_alloc_cache_func: startup_size(0xX) is bigger than PAGESIZE. |
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 |
fjsv_cdr_alloc_fma_job: fjsv_cdr_add failed. |
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 |
fjsv_cdr_alloc_fma_job: jobp or mlp is NULL. |
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 |
fjsv_cdr_alloc_fma_job: mlp is NULL. |
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 |
fjsv_cdr_check_cache: CPU version(#) is different. |
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 |
fjsv_cdr_check_cache: jobp is NULL. |
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 |
fjsv_cdr_check_dr_status: kmem_zalloc failed. |
Cause |
Allocating work memory failed in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
fjsv_cdr_check_dr_status: prom_finddevice failed. |
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 |
fjsv_cdr_check_dr_status: prom_getprop failed. |
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 |
fjsv_cdr_check_error: reqp is NULL. |
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 |
fjsv_cdr_check_mbox: find FJSV_MBOX_FAILURE. |
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 |
fjsv_cdr_check_mbox: reqp is NULL. |
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 |
fjsv_cdr_delete_cache_func: jobp is NULL. |
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 |
fjsv_cdr_delete_fma_job: jobp is NULL. |
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 |
fjsv_cdr_delete_job: jobp is NULL. |
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 |
fjsv_cdr_delete_memlist: mlp is NULL. |
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 |
fjsv_cdr_delete_req: reqp is NULL. |
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 |
fjsv_cdr_fma_clear_data: CPU#: sfmmu_dtlb_lock failed. |
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 |
fjsv_cdr_fma_clear_data: CPU#: sfmmu_mtlb_unlock failed. |
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 |
fjsv_cdr_fma_clear_data: can't get map_size. |
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 |
fjsv_cdr_fma_clear_data: jobp is NULL. |
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 |
fjsv_cdr_fma_copy_data: CPU#: sfmmu_dtlb_lock failed. |
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 |
fjsv_cdr_fma_copy_data: CPU#: sfmmu_mtlb_unlock failed. |
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 |
fjsv_cdr_fma_copy_data: can't get map_size. |
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 |
fjsv_cdr_fma_copy_data: fjsv_cdr_check_mbox failed. |
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 |
fjsv_cdr_fma_copy_data: jobp is NULL. |
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 |
fjsv_cdr_get_jobp: reqp is NULL. |
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 |
fjsv_cdr_get_mem_range: prom_finddevice failed. |
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 |
fjsv_cdr_get_mem_range: prom_getprop failed. |
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 |
fjsv_cdr_get_mem_range: prom_getprop returns error. |
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 |
fjsv_cdr_job_disp: reqp is NULL. |
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 |
fjsv_cdr_make_job: fjsv_alloc_map_area failed. |
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 |
fjsv_cdr_make_job: kmem_zalloc failed. |
Cause |
Allocating work memory failed in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
fjsv_cdr_make_job: the number of CPUs is zero. |
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 |
fjsv_cdr_make_req: jobp is NULL. |
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 |
fjsv_cdr_make_req: kmem_zalloc failed. |
Cause |
Allocating work memory failed in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
fjsv_delete_map_area: wrong pagesize(#). |
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 |
fjsv_flush_cache_line: CPU#: sfmmu_dtlb_lock failed. |
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 |
fjsv_flush_cache_line: CPU#: sfmmu_mtlb_unlock failed. |
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 |
fjsv_flush_cache_line: jobp is NULL. |
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 |
fjsv_pa_is_target: jobp is NULL. |
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_deprobe_board: fjsv_cdr_alloc_detach_mlist() failed. |
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_deprobe_board: fjsv_cdr_make_job() failed. |
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_deprobe_board: fjsv_cdr_make_req() failed. |
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_move_memory: CPU version(#) is different. |
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_move_memory: FMA failed. rtn = #. |
Cause |
The firmware returned the error in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Message |
sfdr_move_memory: failed to quiesce OS for copy-rename |
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 |
sfdr_move_memory: fjsv_cdr_make_job() failed. |
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_move_memory: fjsv_cdr_make_req() failed. |
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_move_memory: prom_fjsv_fma_start failed. |
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_move_memory: prom_fjsv_fma_end failed. rtn = # |
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_move_memory: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_move_memory:fjsv_cdr_alloc_cache_func() failed. |
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_move_memory:fjsv_cdr_alloc_fma_job() failed. |
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_move_memory:fjsv_cdr_fma_clear_data() failed. |
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_move_memory:fjsv_cdr_fma_copy_data() failed. |
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_op: detect dr-status = ###### |
Cause |
dr-status is specified in OBP, and the system can't continue the DR process. |
Remedy |
Please contact our customer service. |
Output |
Console and Standard Output |
Message |
sfdr_probe_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. |
Output |
Console and Standard Output |
Message |
sfdr_probe_board:fail to connect board. retval = #. |
Cause |
The firmware returned the error in the process. |
Remedy |
Repeat the action. If this error message appears again, please contact our customer service. |
Output |
Console and Standard Output |
Contents
![]() ![]() |