Sun Microsystems Sun Enterprise 10000 Dynamic Reconfiguration User Manual page 110

TABLE A-11
Error Message
obp_info: missing slot
number [non-fatal]
sbus node without upa-
portid [non-fatal]
sysio_num out of range
[non-fatal]
DR Error: cannot open
/dev/openprom. . .
errno_description
94 Sun Enterprise 10000 Dynamic Reconfiguration User Guide • February 2000
OBP Error Messages (Continued)
Probable Cause
This message indicates that corrupted
or incorrect values were found in the
OBP structures, meaning that the
information in the OBP Configuration
window will not be correct.
This message indicates that corrupted
or incorrect values were found in the
OBP structures, meaning that the
information in the OBP Configuration
window will not be correct.
This message indicates that corrupted
or incorrect values were found in the
OBP structures, meaning that the
information in the OBP Configuration
window will not be correct.
The DR daemon could not open the
entry point for the domain's OBP
information, meaning that no
information will appear in the OBP
Configuration window. This error is
not fatal.
Suggested Action
This is a non-fatal error. If
this error persists, reboot the
domain. If the error persists
after the reboot, report it to
your Sun service
representative, providing as
much information about the
error as possible.
This is a non-fatal error. If
this error persists, reboot the
domain. If the error persists
after the reboot, report it to
your Sun service
representative, providing as
much information about the
error as possible.
This is a non-fatal error. If
this error persists, reboot the
domain. If the error persists
after the reboot, report it to
your Sun service
representative, providing as
much information about the
error as possible.
Determine what caused this
error by using the open(2)
man page and the
errno_description. The DR
daemon may have
encountered a resource limit.
If so, stop the daemon then
restart it. Also, check the size
of the DR daemon. It should
be between 300- and 400-
Kbytes. If it is not within this
range, stop the daemon then
restart it. If you cannot
recover the domain from this
error or symptoms of a
memory leak exist, report
this error to your Sun service
representative, providing as
much information from the
system logs as possible.