Known Bugs

The following is a list of bugs that are known to exist in this release of the IDN feature.

VerExec Error Occurs When a Solaris 2.6 Domain Is Rebooted From OBP (4254715)

Errors that are related to the IDN feature can occur on domains running the Solaris 2.6 operating environment. Some messages can be safely ignored; however, some messages are related to setting the OBP variable idn-smr-size to a value other than zero.

Workaround: The Solaris 2.6 operating environment does not support the IDN feature. Do not change the default value of idn-smr-size on domains that are running the Solaris 2.6 operating environment.

IDN Driver Can Panic if idn_slab_mintotal Is Set to a Value Other Than Zero (4273317)

Parameter values set outside of the allowed range can result in panics occurring on the domain. You must ensure that you use a value that is within the allowed range of values.

The following is a list of parameters that can cause a panic if the value set in the idn.conf(4) file is outside of the allowed range.

• idn_slab_mintotal

• idn_slab_bufcount

• idn_smr_bufsize

Workaround: No workaround exists for this bug. The domain will continue to panic because of the incorrect values in the idn.conf(4) file any time the IDN driver is loaded. You must ensure that you use values that are within the allowed range.

Setting idn_protocol_nservers Value to the Minimum Value of One Causes Panic (4275051)

Setting the idn.conf(4) parameter idn_protocol_nservers to one can cause the domain to panic. The idn.conf(4) parameters are initialized when the domain is rebooted and the IDN driver is loaded. If the domain panics, the event detector daemon reboots the domain, and the domain panics again, causing an unrecoverable error.

Workaround: Do not set this parameter to one. If this error occurs, reboot the domain to single-user mode and remove the /etc/hostname.idnX file to prevent the IDN driver from being automatically loaded at reboot.

Remote Domain Reporting Master Domain Without CPU ID (4275420)

Certain combinations of CPU IDs and domain IDs in a domain responding to a connect request can cause incorrect information being sent in the connect request.

Workaround: None

IDN Driver Does Not Implement MIB-II Kernel Statistics (4276084)

The IDN driver does not implement MIB-II kernel statistics for this release. Thus, network management tools that display MIB-II kernel statistics will not be able to display statistics about IDNs.

Workaround: No workaround exists for this bug. It will not be fixed in this release.

Setting idn_msgwait_nego to the Minimum Value (1 Second) Can Cause IDN Operations to Fail (4277617)

Setting the idn.conf(4) parameter idn_msgwait_nego to 1 second can cause IDN operations to fail. The idn.conf(4) parameters are initialized when the domain is rebooted. If this error occurs, you must reset the value and reboot the domain before you can execute IDN operations.

Workaround: Do not set this parameter to one. This bug will not be fixed in this release.