DR Driver Error Messages (Sun Enterprise 10000 Dynamic Reconfiguration User Guide)

Sun Enterprise 10000 Dynamic Reconfiguration User Guide

DR Driver Error Messages

The following table contains the DR driver failures that are sent to the system logs and to the SSP applications. In general, refer to the descriptions of the daemon and PSM errors for details about what goes to the system logs and what goes to the SSP.

Note -

All of the possible DR driver failure messages are related to the three probable causes given in the table. Likewise, all of the failure messages have one suggested action.

Table A-6 DR Driver Error Messages


Error Message	Probable Cause	Suggested Action
`DR: Error: initiate_attach: ioctl failedDR: Error: complete_attach: ioctl failedDR: Error: abort_attach: ioctl failedDR: Error: get_cpu_info: ioctl failedDR: Error: get_mem_config: ioctl failed`	An `ioctl()` failure (that is, a failure that was encountered by the DR daemon when it tried to use the DR driver) can occur at three separate levels.At the first level--within the DR daemon, errors occur when the DR daemon and the DR driver are not interacting properly. The driver could be missing; the DR driver files in the `/devices/pseudo` directory could be missing, or the file permissions could be wrong. The DR daemon could also be experiencing memory corruption or resource limitations. The `ioctl()` failure message is followed by a message in the form: `Daemon (errno` `#error_number): error description`.	The context of the `ioctl()` failure (that is, which function precedes the `ioctl()` failed portion of the message), combined with the text of the error message, indicates what failed. Use the error number to identify the probable cause by checking the information on the `ioctl`(2) man page. You can also use the `/usr/include/errno.h` header file if the `ioct`l(2) man page does not have a specific reference for the error number.
`DR: Error: get_mem_cost: ioctl failedDR: Error: get_mem_drain: ioctl failedDR: Error: update_attach: ioctl failedDR: Error: ioctl failed, error draining resourcesDR: Error: detach_board: UNCONFIGURE ioctl failedDR: Error: detach_board: DISCONNECT ioctl failedDR: Error: abort_detach: CANCEL ioctl failedDR: Error: abort_detach: CONFIGURE ioctl failedDR: Error: get_dr_state: ioctl failedDR: Error: get_dr_status: ioctl failed`	At the second level--within the platform independent module (PIM) layer of the DR driver, an `ioctl` failure could indicate busy resources, failing I/O devices on the system board, or improper interaction between the PIM and the platform specific module (PSM) layers. The `ioctl()` failure message is followed by a PIM message in the form: `PIM (error #errornumber):` `errno_description`.At the third level--the PSM layer, an `ioctl()` failure could indicate busy resources, failing I/O devices on the system board, memory detach failures, CPU detach failures, or internal failures encountered by the PSM driver. The error description usually cites specific physical devices that are failing or includes detailed explanations for a memory or CPU detachment failure. The `ioctl()` failure message is followed by a PSM message that appears in the following form: `PSM (error #errornumber):` `errno_description`.Note that failures in the PSM layer do not have corresponding `errno` values. PSM failure messages use an error number. You can find explanations of the error numbers in the `/usr/include/sys/sfdr.h` header file.	The context of the `ioctl()` failure (that is, which function proceeds the `ioctl()` failed portion of the message), combined with the text of the error message, indicates what failed. Use the error number to identify the probable cause by checking the information on the `ioctl`(2) man page. You can also use the `/usr/include/errno.h` header file if the `ioct`l(2) man page does not have a specific reference for the error number.