Sun Enterprise 10000 Dynamic Reconfiguration User Guide

OpenBoot PROM Error Messages

The following table contains the list of OpenBoot(TM) PROM (OBP) error messages that are sent to the system logs and/or to the SSP applications.

Table A-10 OpenBoot PROM Error Messages

Error Message 

Probable Cause 

Suggested Action 

cpu unit without upa-portid [non-fatal]

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 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. 

OBP_info: bad child units [non-fatal]

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 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. 

obp_info: bad slot number [non-fatal]

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 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. 

obp_info: missing sbus name [non-fatal]

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 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. 

obp_info: missing slot number [non-fatal]

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 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. 

sbus node without upa-portid [non-fatal]

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 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. 

sysio_num out of range [non-fatal]

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 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. 

NGDR Error: cannot open /dev/openprom. . . errno_description

The DR daemon could not open the entry point for the domain OBP information, meaning that no information will appear in the OBP Configuration window. This error is not fatal. 

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.

NGDR Error: close error on /dev/openprom

The DR daemon failed to close the entry point for the OBP driver. 

Determine what caused this error by using the error messages that preceded this error message. Fix the error if possible. 

NGDR Error: dev/openprom busy. Cannot open.

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. 

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.

NGDR Error: get_obp_board_config: invalid board state

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. 

None 

NGDR Error: OBP config: too many CPUs

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). 

Ensure that OBP is operating properly. If it is not, reboot the domain. 

NGDR Error: OPROMCHILD. . . errno_description

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.

Determine what caused this error by using the errno_value or the errno_description that accompanies this error message. Fix the error is possible.

NGDR Error: OPROMGETPROP. . . errno_description

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.

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.

NGDR Error: OPROMNEXT. . . errno_description

An ioctl() performed on the OBP driver entry point failed, specifically the ioctr() used to walk to the next OBP node in the device tree, meaning that the information in the OBP Configuration window will not be complete.

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.

NGDR Error: System architecture does not support this option of this command.

An unsupported option was given to the DR daemon as it walked the OBP tree for the domain, meaning that part of the information in the OBP Configuration window will be incorrect. This error is non-fatal. 

None