A P P E N D I X  A

Release Notes Supplement for Solaris 10 3/05 HW1

This appendix provides information about issues specific to the Solaris 10 3/05 HW1 OS release.

Note - The information in this appendix applies only to platforms still running the temporary Solaris 10 3/05 HW1 release. It does not apply to systems running the Solaris 10 3/05, Solaris 10 3/05 HW2, or Solaris 10 1/06 OS. For information about the HW2 OS, which also is replaced by the Solaris 10 1/06 OS, see Appendix B.

Issues and Bugs

If you are using hardware still running the temporary Solaris 10 3/05 HW1 OS (a specific form of the Solaris 10 3/05 OS that initially shipped on certain hardware), take into account the following issues as well as those published in the Solaris 10 Release Notes (part number 817-0552) on http://docs.sun.com.

Solaris Install Launcher Exiting Causes Reboots (6300863)

In some situations, installation of Solaris 10 3/05 HW1 fails when the Solaris Install Launcher fails to find find_device.out, reboots, then reaches the same point and calls for a reboot again.

Workaround: Specify the - text option when booting:

boot net - text

UltraSPARC IV+ Large Pages (32 MB and 256 MB) Should Be Deactivated (6287398 and 6313025)

In Solaris 10 3/05 HW1, the UltraSPARC IV+ large pages feature is available, but should not be used. Running an application that attempts to map to large pages might cause the application to execute improperly and result in a core dump or hang.

Workaround: The kernel update (KU) patch 118822-18 includes an interim fix, which deactivates the large pages feature.

Note - Avoid installing KU patch 118822-16 on UltraSPARC IV+ systems, because that specific dash version includes a function that attempts to use large pages.

page_get_replacement_page Might Fail With Large Pages (6266922)

When cfgadm (1M) removes memory from a running system, the system may hang when running applications that use large pages, such as Oracle. The kernel fails to find memory on other boards to replace large pages of data from the memory being removed. There are no error messages for this condition.

Workaround: Do not use dynamic reconfiguration (DR) with Oracle. If the cfgadm operation is hung, kill it and retry when the large pages are freed.

prtdiag Still Shows System Board After the Board Is Removed From the Domain Using DR (6298989)

If an UltraSPARC IV+ board is removed from a Sun Fire E20K or E25K system's domain via dynamic reconfiguration, the prtconf and prtdiag programs still report the nodes corresponding to the UltraSPARC IV+ CPUs as being in the system. These reports remain until the system is rebooted.

Workaround: Between the time of removing a board using DR and rebooting the domain, take into account the incorrect node information in reports.

System Fails With "transport rejected bad packet" Message Under Stress I/O Condition (6261607)

During stressed I/O conditions, I/O fails with a TRAN_BADPKT message such as the following:

WARNING:/ssm@0,0/pci@18,700000/SUNW,qlc@3,1/fp@0,0/ssd@w500000e010e9a152,0 (ssd68): transport rejected bad packet

Workaround: None

Systems Panic Due to Limit on Max Number of lgrps (6256111)

This problem appears only in large machines such as a fully loaded Sun Fire E25K system. During booting, this error message appears and the system panics:

More leaf lgrps in system than are supported!

This problem only occurs during the boot itself. If your system boots normally, the problem is not occurring.

Workaround: Try using fewer CPUs on the affected systems. For example, if this error occurs on a Sun Fire E25K system, try booting with fewer than 120 CPU cores. Use DR to b ring the remaining boards into the active domain.

Race Condition Between EF/kcfd and IPsec Algorithm Availability (6266083)

This problem might occur on a freshly installed system or a system that imports a large number of new Service Management Facility (SMF) manifests during the boot. After these booting conditions, IPsec (part of svc:/network/initial:default) might be initialized prior to the encryption framework (svc:/system/cryptosvc:default). Because authentication or encryption algorithms are not available, creation of IPsec security associations might fail with an error message such as this:

PF_KEY error: type=ADD, errno=22: Invalid argument, diagnostic code=40: Unsupported authentication algorithm

For example, this might occur when using DR on a Sun Fire E25K system, which involves IPsec services.

Workaround: Before performing operations that use IPsec services, perform the following steps after a boot that imports a large number of new SMF manifests:

1. Issue this command after booting:

ipsecalgs -s

2. If /etc/inet/secret/ipseckeys exists on the system, also issue this command:

ipseckey -f /etc/inet/secret/ipseckeys

Now you can perform actions that create IPsec security associations, such as using DR on a Sun Fire E25K system.

This procedure needs to be repeated only when a large number of new SMF manifests are imported during the boot.

Solaris 10 3/05 HW1 Operating System SPARC Patch List

This section provides patch information that applies only to SPARC systems running the Solaris 10 3/05 HW1 OS. It does not apply to systems running the Solaris 10 3/05, Solaris 10 3/05 HW2, or Solaris 10 1/6 OS. See also the Solaris 10 Release Notes at http://docs.sun.com.

The patches that are listed in this appendix have been applied to the Solaris 10 3/05 HW1 Operating system in one of the following ways:

The showrev -p command provides a list of all patches that were applied to the installed system, regardless of how these patches were applied. The Solaris 10 3/05 HW1 software includes a known and tested level of patches. However, patches cannot be backed out of the Solaris 10 3/05 HW1 release.

Note - The Solaris 10 3/05 HW1 software contains special patches that perform tasks that are specific to the Solaris release installation images. These patches are specific to each Solaris software release and do not apply to other systems or releases of the Solaris software. Do not attempt to download or install these patches on other systems or installations of the Solaris OS.