Sun Microsystems Sun Enterprise 10000 Dynamic Reconfiguration User Manual page 76

TABLE A-3
Error Message
DR: Error:
get_mem_cost: ioctl
failed
DR: Error:
get_mem_drain: ioctl
failed
DR: Error:
update_attach: ioctl
failed
DR: Error: ioctl
failed, error
draining resources
DR: Error:
detach_board:
UNCONFIGURE ioctl
failed
DR: Error:
detach_board:
DISCONNECT ioctl
failed
DR: Error:
abort_detach: CANCEL
ioctl failed
DR: Error:
abort_detach:
CONFIGURE ioctl
failed
DR: Error:
get_dr_state: ioctl
failed
DR: Error:
get_dr_status: ioctl
failed
60 Sun Enterprise 10000 Dynamic Reconfiguration User Guide • February 2000
Memory Allocation Error Messages (Continued)
Probable Cause
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
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.
Suggested Action
See above.