Solaris 9 9/05 HW Release Notes

System Administration Bugs

The following System Administration bugs apply to the Solaris 9 9/05 HW release.

`localeadm` Add Region Function Broken for Individual CDROM After Creating a New Config File (6350486)

The localeadm utility does not install ceu and nam regions properly by using media CD or net CD images. No error message is displayed.

Workaround: Use DVD Solaris images instead of CD images.

`patchadd` Might Fail for Some Patches (6460360)

patchadd might fail for some patches when you have not logged in as root but have become root by running the su command.

The following error message is displayed:

patch has not been installed

Workaround: If root login is disabled, temporarily enable the root login and login as root. Install the patch and disable the root login.

SPARC: Panics That Occur During Suspend and Resume Cycles Might Cause the System to Hang (5062026)

A system panic that occurs while you are performing a suspend-and-resume (cpr) cycle might cause the system to hang. More typically, this problem is observed in Sun Blade^TM 2000 workstations that have the XVR-1000 graphics accelerator installed. Rarely, other SPARC based systems might similarly hang during a panic. When the panic occurs, the core dump is not saved, and no prompt appears on the console. The problem might be more prevalent if the kernel debugger (kadb) is active.

Workaround: Upgrade to OBP version 4.17 or later.

SPARC: Stopping the System by Using Keyboard Sequences Might Cause a System Panic (5061679)

If you attempt to stop the system by pressing keyboard sequences such as Stop-A or L1-A, the system might panic. An error message similar to the following example is displayed:

panic[cpu2]/thread=2a100337d40: pcisch2 (pci@9,700000): 
consistent dma sync timeout

Workaround: Do not use keyboard sequences to force the system to enter OpenBoot^TM PROM.

x86: Universal Serial Bus Architecture Modular DeBugger Not Configured Automatically When Only New Framework Is Loaded (4982529)

The Universal Serial Bus Architecture (USBA) Modular DeBugger (mdb ) commands might not be automatically configured on some x86 systems.

Workaround: To access the USBA mdb commands, run the following command to load the usba mdb module manually after starting mdb:

> ::load usba

After the usba mdb module is loaded, you can obtain a list of all the USB commands by running the following command:

> ::dcmds ! grep usb

x86: Pressing the F4 Key During BIOS Bootup Fails to Boot the Service Partition (4782757, 5051157)

You are booting a Sun LX50 which has a Service partition and the Solaris 9 9/05 HW (x86 Platform Edition) software is installed. Pressing the F4 function key to boot the Service partition, when given the option, causes the screen to go blank. The system then fails to boot the Service partition.

Workaround: Do not press the F4 key when the BIOS Bootup Screen is displayed. After a time-out period, the Current Disk Partition Information screen is displayed. Select the number in the Part# column that corresponds to type=DIAGNOSTIC. Press the Return key. The system boots the Service partition.

Solaris WBEM Services 2.5 Daemon Cannot Locate `com.sun` Application Programming Interface Providers (4619576)

The Solaris WBEM Services 2.5 daemon cannot locate providers that are written to the com.sun.wbem.provider interface or to the com.sun.wbem.provider20 interface. Even if you create a Solaris_ProviderPath instance for a provider that is written to these interfaces, the Solaris WBEM Services 2.5 daemon does not locate the provider.

Workaround: To enable the daemon to locate such a provider, stop and restart the Solaris WBEM Services 2.5 daemon.

# /etc/init.d/init.wbem stop

# /etc/init.d/init.wbem start

Note –

If you use the javax API to develop your provider, you do not need to stop and restart the Solaris WBEM Services 2.5 daemon. The Solaris WBEM Services 2.5 daemon dynamically recognizes javax providers.

Some `com.sun` Application Programming Interface Method Invocations Fail Under XML/HTTP Transport Protocol (4497393, 4497399, 4497406, 4497411)

If you choose to use the com.sun application programming interface rather than the javax application programming interface to develop your WBEM software, only Common Information Model (CIM) remote method invocation (RMI) is fully supported. Other protocols, such as XML/HTTP, are not guaranteed to work completely with the com.sun application programming interface.

The following table lists examples of invocations that execute successfully under RMI but fail under XML/HTTP:

Method Invocation	Error Message
`CIMClient.close()`	`NullPointerException`
`CIMClient.execQuery()`	`CIM_ERR_QUERY_LANGUAGE_NOT_SUPPORTED`
`CIMClient.getInstance()`	`CIM_ERR_FAILED`
`CIMClient.invokeMethod()`	`XMLERROR: ClassCastException`

Cannot Modify File-System Mount Properties With Solaris Management Console Mounts and Shares Tool (4466829)

The Solaris Management Console Mounts and Shares tool cannot modify mount options on system-critical file systems such as root (/), /usr, and /var.

Workaround: Choose one of the following workarounds:

Use the remount option with the mount command.
# mount -F file-system-type -o remount, additional-mount-options \ device-to-mount mount-point
Note –
Mount property modifications that are made by using the -remount option with the mount command are not persistent. In addition, all mount options that are not specified in the additional-mount-options portion of the previous command inherit the default values that are specified by the system. See the man page mount_ufs(1M) for more information.
Edit the appropriate entry in the /etc/vfstab file to modify the file system mount properties, then reboot the system.