Sun Microsystems Sun Enterprise 10000 Dynamic Reconfiguration User Manual page 111

TABLE A-11
Error Message
DR Error: close error on
/dev/openprom
DR Error: dev/openprom
busy. Cannot open.
DR Error:
get_obp_board_config:
invalid board state
DR Error: OBP config: too
many CPUs
DR Error: OPROMCHILD. . .
errno_description
DR Error: OPROMGETPROP. . .
errno_description
OBP Error Messages (Continued)
Probable Cause
The DR daemon failed to close the
entry point for the OBP driver.
The entry point for the domain OBP
information was busy, meaning that no
information will appear in the OBP
Configuration window. This error is
non-fatal.
Communication protocol was
breached over the eligibility of a board
when the SSP application tried to
query the OBP information for a
board. To the SSP, the board is part of
the domain, so the SSP attempts to
drain the board resources. However, to
the DR driver and daemon, the board
is not part of the domain.
The DR daemon found too many CPUs
attributed to a system board in the
OBP structures. To OBP, the board has
more CPUs than it could possibly have
(for instance, five or more).
An ioctr() performed on the OBP
driver entry point failed, specifically
the ioctr() used to walk the child
OBP node in the device tree, meaning
that the information in the OBP
Configuration window will not be
complete.
An ioctl() performed on the OBP
driver entry point failed, specifically
the ioctl() used to acquire the OBP
properties, meaning that the
information in the OBP Configuration
window will be incomplete.
Suggested Action
Determine what caused this
error by using the error
messages that preceeded this
error message. Fix the error if
possible.
Retry the operation. Check
for process that may be
keeping the entry point open
by using the ps(1M)
command. Stop any
processes that are keeping
the entry point open.
None
Ensure that OBP is operating
properly. If it is not, reboot
the domain.
Determine what caused this
error by using the errno_value
or the errno_description that
accompanies this error
message. Fix the error is
possible.
Determine what caused this
error by using the ioctl(2)
man page and the
errno_description that
accompanies this error
message. Fix the error if
possible.
Appendix 95