Solaris 10 5/09 Release Notes

Chapter 2 Solaris Runtime Issues

This chapter describes runtime issues that are known to be problems.

Note –

To see which bugs and issues are fixed and no longer apply to the Solaris 10 5/09 software, refer to Appendix A, Table of Integrated Bug Fixes in the Solaris 10 Operating System.

Common Desktop Environment

The following bugs in Solaris 10 OS apply to the Common Desktop Environment (CDE).

Mozilla Crashes After Printing (6824695)

When you use Mozilla to print a page, Mozilla crashes once the page is printed. No error message is displayed.

Workaround: Use Firefox or Thunderbird instead of Mozilla.

Trusted Stripe Disappears From the Screen After Resolution Change (6460624)

When you type the /usr/X11/bin/xrandr -s command to set a smaller screen resolution, trusted stripe is no longer displayed. This affects the Trusted CDE Desktop but not the Trusted Java DS Desktop. No error message is displayed.

Workaround: After the resolution change, restart the Workspace Manager. Select windows -> Restart Workspace Manager from the CDE workspace menu and click OK.

x86: kdmconfig Command Does Not Create System Identification Configuration File for Xorg X Server (6217442)

If you use the JumpStart installation method, the process might use a system identification configuration (sysidcfg) file. This file is used to generate a specific Xsun configuration file for a system. The Xsun configuration portion of a sysidcfg file is created by the command kdmconfig -d filename. However, on systems that use the default Xorg server, the command does not create a file with any Xorg configuration information. Consequently, you cannot use the JumpStart method on these systems without some additional preparatory steps.

Workaround: Before using the JumpStart installation method on a system that uses the Xorg server, perform the following steps.

  1. Prepare a specific xorg.conf file to be used on the system. Store this file in the JumpStart directory of the JumpStart server.

    Create an xorg.conf file with one of these commands:

    • /usr/X11/bin/Xorg -configure

    • /usr/X11/bin/xorgconfig

    • /usr/X11/bin/xorgcfg

  2. Create a finish script that copies the xorg.conf file to the /etc/X11 directory in the system that you want to install. For example, the script might include the following line:

    cp ${SI_CONFIG_DIR}/xorg.conf /etc/X11/Xorg.conf
  3. In the custom JumpStart rules file, include the finish script in the rules entry for systems of the type that you want to install.

  4. Perform the custom JumpStart installation.

For instructions about how to perform a custom JumpStart installation, see the Solaris 10 5/09 Installation Guide: Custom JumpStart and Advanced Installations. Chapter 4 includes information about the JumpStart rules file, while Chapter 5 contains a section about finish scripts.

File Systems

The following file system bugs apply to the Solaris 10 release.

zoneadm attach Fails and Mount Operation is Invalid for Branded Zones (6800618)

Attach operation fails on branded zones, although it succeeds on native (Solaris 10) zones. The following error message is displayed:

zone mount operation is invalid for branded zones.
Cannot generate the information needed to attach this zone.

Workaround: Use the attach -F command for non-native branded zones. For more information on this procedure, see System Administration Guide: Solaris Containers--Resource Management and Solaris Zones.

Taking the Primary Disk Offline in a Mirrored ZFS Root Pool

Do not take the primary disk offline in a mirrored ZFS root configuration. The system will not boot from a disk taken offline in mirrored root-pool configuration.

Workaround: To detach a mirrored root disk for replacement or take it offline, boot from another mirrored disk in the pool. Choose one of the following methods:

lucreate Fails When Destination File System Is ZFS and Locale Is Japanese EUC (6750725)

If you use the lucreate command to create a ZFS root file system and the LOCALE is set to a non-English locale, the creation of the ZFS dump volume fails. The following error message is displayed:

ERROR: Unable to determine dump device for boot environment <{c1t1d0s0}>.
ERROR: Unable to create all required file systems for boot environment <zfsUp6>.
ERROR: Cannot make file systems for boot environment <zfsUp6>.

Workaround: Choose one of the following workarounds:

boot -L Does Not Work After Converting UFS to ZFS (6741743)

When Solaris Live Upgrade is used to convert a UFS root filesystem to ZFS, the bootlst command is not copied to the correct location. This error prevents the boot -L command from working. The following error message is displayed:

Evaluating: boot -L
The file just loaded does not appear to be executable.
Boot device: /pci@1f,0/pci@1/scsi@8/disk@1,0:a  File and args: 

Can't mount root

Error in Fcode execution !!!
Evaluating: boot
The file just loaded does not appear to be executable.

Workaround: Copy the bootlst command from /platform/`uname -m`/bootlst to /root pool/platform/`uname -m`/bootlst. For example, if the root pool is rpool, type the following command:

# cp -p /platform/`uname -m`/bootlst /rpool/platform/`uname -m`/bootlst

x86: Unable to Use reboot Command to Boot 32-Bit Kernel (6741682)

The bootadm command fails to construct a properly formatted GRUB menu entry when you boot a system in the 32-bit mode by using the following commands:

As a result, the system boots in the 64-bit mode. The faulty menu.lst file might appear as follows:

findroot rootfs0
kernel /platform/i86pc/kernel/unix
module /platform/i86pc/boot_archive

In the previous example, the kernel line does not contain the multiboot information and is therefore incorrect. No error message is displayed.

Workaround: Edit the /boot/grub/menu.lst file manually and add the following information:

title Solaris 10 10/08
findroot rootfs0
kernel /platform/i86pc/multiboot kernel/unix
module /platform/i86pc/boot_archive

After making these changes, the system boots in the 32-bit mode.

Note –

The changes you make to the menu.lst file persist over system reboots.

Alternately, you can edit the GRUB menu at boot time, adding the kernel/unix boot argument, as shown in the following example:

grub edit> kernel /platform/i86pc/multiboot kernel/unix

Note –

Changes made by editing the GRUB menu at boot time do not persist over system reboots.

For more information, see Modifying Boot Behavior on x86 Based Systems in System Administration Guide: Basic Administration.

zpool attach Might Create an Illegal Root Pool (6740164)

When you attach a device to a root pool to create a mirrored root pool, zpool attach might create an illegal root pool if a whole disk is added to the pool. A ZFS root pool must be created with disk slices, not whole disks. If you attempt to boot from the whole disk that was added to the mirrored root pool, the system will not boot.

Workaround: Perform the following steps:

  1. Detach the disk from the pool. For example

    # zpool detach rpool c0t2d0
  2. Change the disk label to a VTOC (SMI) label. For example:

    # format -e
    Select disk c0t2d0
    format> label
    [0] SMI Label
    [1] EFI Label
    Specify Label type[0]:0
    Ready to label disk, continue? yes
    format> quit
  3. Add a disk slice back to the pool to create a mirrored root pool. For example:

    # zpool attach rpool c0t2d0s0

See also zpool attach Command Does Not Copy bootblock Information (6668666).

SPARC: Solaris Live Upgrade Does Not Create a menu.lst File (6696226)

On the SPARC platform, a menu.lst file needs to be created in the root pool's dataset. No error message is displayed.

Workaround: Create the menu.lst file manually. For example, if you have two ZFS boot environments, zfs1008BE and zfs10082BE, in the ZFS root pool, rpool, type the following commands:

# mkdir -p /rpool/boot
# cd /rpool/boot
# vi menu.lst

Add the following entries to the menu.lst file:

title zfs1008BE
bootfs rpool/ROOT/zfs1008BE
title zfs10082BE
bootfs rpool/ROOT/zfs10082BE

zpool attach Command Does Not Copy bootblock Information (6668666)

If you use the zpool attach command to add a disk to a ZFS root pool, the bootblock information is not copied to the newly added disk. This problem does not affect mirrored ZFS root pools that are created with an initial installation. System does not boot from alternate disk in the mirrored root pool.

Workaround: Choose one of the following workarounds:

x86: ata Timeouts During Boot (6586621)

ata driver timeouts might occur during system boot on Intel multiprocessor systems. These timeouts occur when the root device is on a drive with the HBA controller bound to the legacy ata driver. These timeouts lead to a momentary hang, hard hang, or a panic during system boot with console messages similar to the following:

scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: reset bus, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: early timeout, target=0 lun=0
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):
        Error for command 'read sector'   Error Level: Informational
gda: [ID 107833 kern.notice]           Sense Key: aborted command
gda: [ID 107833 kern.notice]           Vendor 'Gen-ATA ' error code: 0x3
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):
        Error for command 'read sector'   Error Level: Informational
gda: [ID 107833 kern.notice]           Sense Key: aborted command
gda: [ID 107833 kern.notice]           Vendor 'Gen-ATA ' error code: 0x3
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: abort request, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: abort device, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: reset target, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: reset bus, target=0 lun=0
scsi: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0 (ata0):
        timeout: early timeout, target=0 lun=0
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):
        Error for command 'read sector'   Error Level: Informational
gda: [ID 107833 kern.notice]           Sense Key: aborted command
gda: [ID 107833 kern.notice]           Vendor 'Gen-ATA ' error code: 0x3
gda: [ID 107833 kern.warning] WARNING: /pci@0,0/pci-ide@1f,2/ide@0/cmdk@0,0 (Disk0):

Workaround: Choose one of the following workarounds:

Note –

To avoid performance degradation, workaround 3 or workaround 4 should only be used temporarily until workaround 5 can be used .

zfs snapshot -r Fails When File System Is Busy (6462803)

This issue is caused because of a problem with the way synchronous I/O is handled when a file system is unmounted. When more than one ZFS BE exists in a ZFS root pool, a recursive snapshot might fail.

cannot create snapshot 'rpool@today': dataset is busy

Workaround: Choose one of the following workarounds:

zoneadm install Fails With a ZFS Legacy Mount (6449301)

If a non-global zone is initially configured with a ZFS file system to be mounted with the `add fs subcommand and specifies mountpoint=legacy, the subsequent zone installation fails. The following error message is displayed.

ERROR: No such file or directory:
cannot mount </zones/path/root/usr/local> in non-global zone to install:
the source block device or directory </path/local> cannot be accessed

Workaround: Add access to a ZFS file system after installing the non-global zone.

ZFS and UNIX/POSIX Compliance Issues

ZFS is designed to be a POSIX compliant file system and in most situations, ZFS is POSIX compliant. However, two edge case conditions exist when ZFS does not meet the POSIX compliance tests:

  1. Updating ZFS files system capacity statistics.

  2. Modifying existing data with a 100 percent full file system.

Related CRs:

fdisk -E Can Sweep Disk Used by ZFS Without Warning (6412771)

If you use the fdisk -E command to modify a disk that is used by a ZFS storage pool, the pool becomes unusable and might cause an I/O failure or system panic.


Do not use the fdisk command to modify a disk that is used by a ZFS storage pool. If you need to access a disk that is used by a ZFS storage pool, use the format utility. In general, disks that are in use by file systems should not be modified.

ZFS and Third-Party Backup Product Issues

The following are the issues with Brightstor ARCserve Backup products.

BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support

The BrightStor ARCserve Backup (BAB) Client Agent for UNIX (Solaris) can be used to backup and restore ZFS files.

However, ZFS NFSv4-style ACLs are not preserved during backup. Traditional UNIX file permissions and attributes are preserved.

Workaround: If you want to preserve ZFS files with NFSv4-style ACLs, use the tar command with the -p option or the cpio command with the -P option to write the ZFS files to a file. Then, use BAB to backup the tar or cpio archive.

ZFS GUI Should Check For /usr/lib/embedded_su at the Beginning of Each Wizard (6326334)

If you add the SUNWzfsg package from a Solaris 10 5/09 release to a system that runs a pre-Solaris 10 6/06 release, which does not have the embedded_su patch, the ZFS Administration application wizards are not fully functional.

If you attempt to run the ZFS Administration application on a system without the embedded_su patch, you will only be able to browse your ZFS configuration. The following error message is displayed:

/usr/lib/embedded_su: not found


Add the embedded_su patch (119574-02) to the system that runs a pre-Solaris 10 6/06 release.

Fails to Sync File System on Panic (6250422)

If a host panics with file system I/O occurring to a target, which is connected by using the Solaris iSCSI software initiator, the I/O might not be able to flush or sync to the target device. This inability to flush or sync might cause file system corruption. No error message is displayed.


Use the journaling file system like UFS. Starting with Solaris 10, UFS logging is enabled by default. For more information about UFS, see What’s New in File Systems? in System Administration Guide: Devices and File Systems.

Upgrading From Some Solaris Express or Solaris 10 Releases Requires Remounting of File Systems

After you upgrade an NFSv4 server from Solaris Express 6/05 to Solaris Express 7/05 or later (including all Solaris 10 updates), your programs might encounter EACCES errors. Furthermore, directories might erroneously appear to be empty.

To prevent these errors, unmount and then remount the client file systems. In case unmounting fails, you might need to forcibly unmount the file system by using umount -f. Alternatively, you can also reboot the client.

NFSv4 Access Control List Functions Might Work Incorrectly

NFSv4 Access Control List (ACL) functions might work improperly if clients and servers in the network are installed with different previous Solaris 10 releases. The affected ACL functions and command-line utilities that use these functions are the following:

For more information about these functions and utilities, see their respective man pages.

For example, errors might be observed in a network that includes the following configuration:

The following table illustrates the results of the ACL functions in client-server configurations with different Solaris 10 releases.


Client S10 OS 

Server S10 OS 


get ACL 

S10 Beta 

S10 OS 

fabricated ACL * 

get ACL 

S10 OS 

S10 Beta 

works ok 

set ACL 

S10 Beta 

S10 OS 

works ok 

set ACL 

S10 OS 

S10 Beta 


Workaround: For the NFSv4 ACL functionality to work properly, perform a full installation of the Solaris 10 OS on both the server and the client.

Access Problems Between Solaris NFSv4 Clients and NFSv4 Servers

In the current Solaris 10 version, Solaris implementation of NFSv4 Access Control Lists (ACL) is now compliant with RFC 3530 specifications. However, errors occur for NFSv4 clients that use the Solaris 10 Beta 2 or Beta 1 versions. These clients cannot create files in the NFSv4 servers that are using the current Solaris 10 release. The following error message is displayed:

NFS getacl failed for server_name: error 9 (RPC: Program/version mismatch)

Workaround: None.

Using mkfs Command to Create File System Might Fail on Very Large Disks (6352813)

The mkfs command might be unable to create a file system on disks with a certain disk geometry and whose sizes are greater than 8 Gbytes. The derived cylinder group size is too large for the 1-Kbyte fragment. The large size of the cylinder group means that the excess metadata cannot be accommodated in a block.

The following error message is displayed:

With 15625 sectors per cylinder, minimum cylinders
per group is 16. This requires the fragment size to be
changed from 1024 to 4096.
Please re-run mkfs with corrected parameters.

Workaround: Use the newfs command instead. Or, assign a larger fragment size, such as 4096, when you use the mkfs command.

System Crash Dump Fails on Devices Greater Than 1 TByte (6214480)

The system cannot generate a dump on a partition that is equal to or greater than 1 Tbyte in size. If such a device is on a system, the following might occur after the system boots subsequent to a system panic:

Workaround: Configure the size of your system's dump device to less than 1 Tbyte.

Hardware–Related Issues and Bugs

The following hardware–related issue and bugs apply to the Solaris 10 release.

x86: System Fails to Plumb and Panics While Plumbing the Fourth 5709 Interface with 1 Gbyte RAM (6822680)

Certain x86 systems fail to plumb the fourth 5709 interface with 1 Gbyte of RAM. The system might panic or the following error message is displayed:

ifconfig: plumb: bnx<X>: Invalid argument

This bug affects Dell PowerEdge R610 and R710 servers.

Workaround: Perform the following steps:

  1. Use more than 1 Gbyte of RAM.

  2. Create a hostname.bnxX for each interface.

  3. Reboot your system.

  4. Download and install the latest BNX driver 4.6.2.

  5. Modify the bnx.conf file to use the default setting for tx_descriptor_count.

x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (6810093)

Upgrading the ConnectX firmware to version 2.6.000 or higher on a running system might cause problems in some HCAs and x64 platforms. This issue affects only Mellanox-branded HCAs. Sun-branded PCIe HCAs, EMs, NEMs, and SPARC platforms are not affected.

You might be unable to boot the system or the systrem might hang during boot. ibd (IPoverIB) instance numbers might change and prevent the system from booting and plumb ibd devices.

Workaround 1: Before rebooting the system after updating the firmware using cxflash, remove the ibd<x> instances from the /etc/path_to_inst file and /dev directory. Perform the following steps:

  1. Log in as the root user. The device tree information might look like this:

    # ls -R /devices | grep 15b3

    Note –

    Device specifics vary depending on the Mellanox-branded card installed.

  2. Edit the path_to_inst file. Perform the following steps:

    1. Make a backup copy of the existing path_to_inst file.

      # cp /etc/path_to_inst /etc/path_to_inst.backup
    2. Open the path_to_inst file:

      # vi /etc/path_to_inst
    3. Search for lines that contain ibd and hermon, and delete those lines.

    4. Save the changes and close the file.

  3. Remove the entries in the /dev directory:

    rm /dev/ibd?*
  4. Reboot the system. The system boots normally, and the corresponding device tree looks like this:

    # ls -R /devices | grep 15b3

Workaround 2: If you reboot the system before updating the path_to_inst file and /dev directory, the system might hang. In such a case, perform the following steps:

  1. Power off the system and remove the HCA from the bus.

  2. Reboot the system without the HCA installed.

  3. When system is back on, follow steps 2 through 3 listed in Workaround 1.

  4. Power off the system.

  5. Re-intsall the HCA. Reboot the system.

  6. If the system reboots, but ibd interfaces do not automatically plumb, the /etc/hostname.ib<?> files might not be appropriate for the current device configuration. Manually rename the files to reflect the correct configuration.

Unrecoverable Machine-Check Exception on PCIe (6797934)

Some IBM systems either hang or panic after install. The following panic message is displayed:

Unrecoverable Machine-Check Exception

Workaround 1: Add the following line to the /etc/system file after installation to avoid system hang:

set pcie:pcie_aer_ce_mask=0x11C1

Workaround 2: If the system panics during install or during boot after the install, then use this workaround. Boot the system, with -kd option and set it in the kmdb debugger:

::bp pcie`pcie_initchild
pcie_aer_ce_mask/W 11C1
:d all

When the system comes up append the following line to the /etc/system file to make the changes permanent:

set pcie:pcie_aer_ce_mask=0x11C1

x86: i86_mwait Work Does Not Function as Designed (6736444)

Systems with the Intel Xeon Processor MP 7400 series running the Solaris 10 5/09 OS might experience reduced performance and increased power consumption under light utilization. This problem might occur when CPUs do not quiesce, preventing power management while idle. No error message is displayed.

Workaround: Add the following line to the /etc/system file and reboot the system:

set idle_cpu_prefer_mwait=0

fwflash Does Not Support ConnectX and hermon HCAs (6731804)

The standard fwflash command needs a plug-in to support firmware update on the ConnectX HCA flash device. This plug-in is not yet available in the Solaris 10 5/09 release.

Workaround: A standalone version of the utility is available to enable Solaris 10 users to update their firmware. Perform the following steps:

  1. Download the utility and man page from the Customer Download Center at On this page search for Solaris InfiniBand (IB) Updates 3. Follow the instructions for downloading the package and untar the files. Do not install the package since you need to extract only some of the files.

  2. Rename the original .tar file:

    # mv ib_updates_3_s10u6.i386.tar ib_updates_3_s10u6.i386.tar-orig
  3. Unzip the compressed .tar file:

    #gunzip ib_updates_3_s10u6.i386.tgz
  4. Extract the cxflash utility from the .tar file:

    # tar -xvf ib_updates_3_s10u6.i386.tar usr/sbin/cxflash

    This will extract the relative path below your working directory:

    # ls -lR usr
    total 2
    drwxrwxrwx   2 staff    staff        512 Mar  9 09:20 sbin
    total 88
    -rwxr-xr-x   1 staff    staff      44976 Jan 26 13:39 cxflash
  5. Copy the cxflash file to /usr/sbin. This utility can be used to flash firmware onto hermon and ConnectX HCAs.

    # ls -l firmware
    total 1952
    -rw-r--r--   1 staff    staff     487336 Jan 30 18:29 SUN-375-3548_2.5.100.bin
    -rw-r--r--   1 staff    staff     487436 Jan 30 18:29 SUN-375-3549_2.5.100.bin

    Note –

    The firmware directory which is created when the files are extracted, contains the firmware files for Sun-branded HCA cards and Express Modules. If you have a different versions of the HCA card, please obtain firmware of minimum 2.5.000 revision from your HCA card vendor.

L2ARC is Disabled in the Solaris 10 5/09 Release (6730309)

The output of the zpool upgrade -v command identifies L2ARC cache devices as available. However, cache devices are not available in the Solaris 10 5/09 release. Various error messages are displayed:

Workaround: None.

Issues With HP NC326i Adapter and bge Driver (6691658)

bge fails to operate normally with the HP NC326i device. No error message is displayed.

Workaround: None.

SPARC: 19.55% Performance Regression for the NCP Device Driver (6660074)

Performance regression occurs for the Niagara Crypto Provider (NCP) device driver on Sun SPARC® Enterprise T5220 machines with the Solaris 10 5/09 release. No error message is displayed.

Workaround: Add the following line to the /platform/sun4v/kernel/drv/ncp.conf configuration file:


USB Floppy Drive Fails to Mount (6650724)

Floppy disks are not automatically mounted when inserted into USB floppy drives. No error message is displayed. The pcfs file system on the floppy disk is not accessible.

Workaround: The file system on the floppy disk can be mounted manually by running the mount command. For example:

mount -F pcfs /vol/dev/dsk/c3t0d0/noname /rmdisk

Error Message Is Displayed When Disconnecting USB Storage Devices (6624786)

The following error message is displayed when a USB storage device is disconnected:

Disconnected device was busy, please reconnect.

This message is displayed even when the device is unmounted successfully.

Workaround: None. The error message can be safely ignored.

The (ZFS) ARC Allocates Memory Inside The Kernel Cage Preventing DR (6522017)

ZFS can potentially allocate kernel memory across all system boards on systems with very large memory configurations. One free system board is required for dynamic memory reconfiguration so that the memory from the board to be dynamically reconfigured can be copied to the free board. The dynamic memory reconfiguration means that you cannot dynamically reconfigure memory on systems with very large memory configurations that have ZFS running. High-end SunFireTM servers can relocate kernel pages so that this issue is avoided. These servers must have kernel page relocation (KPR) enabled for domains with more than 32 cores. No error message is displayed

Workaround: Reduce the amount of kernel memory that ZFS can allocate by setting the zfs_arc_max parameter in the /etc/system file. The following example sets the maximum size to 512 Mbytes.

set zfs_arc_max = 0x20000000

mpathadm Does Not Display Load-Balance Setting Specific to Device

The mpathadm show logical-unit subcommand lists the load balancing global configuration value for the Current Load Balance property. However, entries in the csi_vhci.conf that change the load-balance type for a specific product are not reflected in the mpathadm output even when the setting is active.

Registration Tool Prevents Power Management on Some Framebuffers (6321362)

If the background processes for the registration tool are left running, the Elite3D and Creator3D framebuffers stop power management. This failure reduces the power savings when the system is in a power-managed state. Under certain conditions, sys-suspend might also hang. No error message is displayed. The system might hang during a system suspend or resume operation.


Run the following command approximately 60 seconds after each login:

# pkill -f basicreg.jar
# pkill -f swupna.jar

SPARC: Sun Crypto Accelerator 4000 Board Versions 1.0 and 1.1 Not Supported in Solaris 10 OS

A new cryptographic framework is provided in Solaris 10 OS. However, versions 1.0 and 1.1 of the Sun Crypto Accelerator 4000 board's software and firmware do not utilize this framework. Consequently, these versions are not supported in the Solaris 10 OS.

The 2.0 release uses the new framework. This release is available as a free upgrade to current Sun Crypto Accelerator 4000 users who plan to use Solaris 10 OS. Because the Sun Crypto Accelerator 4000 is an export-controlled product, you must contact Sun Enterprise Services or your local sales channel to obtain the free upgrade. Additional information is available on the Sun Crypto Accelerator 4000 web page at Sun's products site.

Certain USB 2.0 Controllers Are Disabled

Support for certain USB 2.0 controllers has been disabled because of incompatibilities between these devices and the EHCI driver. The following message is displayed:

Due to recently discovered incompatibilities with this 
USB controller, USB2.x transfer support has been disabled. 
This device will continue to function as a USB1.x controller. 
If you are interested in enabling USB2.x support please refer 
to the ehci(7D) man page. 
Please refer to for Solaris Ready products 
and to for additional compatible 
USB products.

For the latest information about USB devices, see

Supported USB Devices and Corresponding Hub Configurations

This Solaris release supports both USB 1.1 and USB 2.0 devices. The following table is a summary of USB devices that work in specific configurations. Connection types can either be direct to the computer or through a USB hub. Note that USB 1.1 devices and hubs are low speed or full speed. USB 2.0 devices and hubs are high speed. For details about ports and speeds of operation, see the System Administration Guide: Devices and File Systems.

Table 2–1 USB Devices and Configurations

USB Devices 

Connection Types 

USB 2.0 storage devices 

Direct, USB 1.1 hub, USB 2.0 hub 

USB 1.1 devices except audio 

Direct, USB 1.1 hub, USB 2.0 hub 

USB 1.1 audio devices 

Direct, USB 1.1 hub 

USB 2.0 audio devices 

Not supported 

x86: Limitations Exist With Certain Device Drivers in Solaris 10 OS

The following list describes limitations with certain drivers and interfaces in this release of Solaris 10 for x86 platforms:

Checkpoint Resume

This functionality is turned off for all device types. In the DDI_SUSPEND code in your detach() function, you should return DDI_FAILURE.

Power Management

This functionality is unavailable to USB devices. Do not create power management components. Write your driver so that pm_raise_power() and pm_lower_power() are called only when power management components are created.

DVD-ROM/CD-ROM Drives on Headless Systems

Power management of interactive devices such as removable media is linked with power management of your monitor and the graphics card that drives your monitor. If your screen is active, devices such as the CD-ROM drive and diskette remain at full-power mode. These devices might switch to low-power mode on a system without a monitor. To restore power to the CD or diskette, type volcheck to obtain the latest status from each removable device.

Alternatively, you can disable power management on your system by using the Dtpower GUI. By disabling power management, these devices are constantly at full power.

x86: Manual Configuration Required to Specify Non-US English Keyboards

By default, the kdmconfig program specifies Generic US-English(104-Key) as the keyboard type that is connected to the system. If the system's keyboard is not a US-English keyboard, you must manually specify the keyboard type during installation. Otherwise, installation continues by using the default keyboard specification that is inconsistent with the system's actual keyboard type.

Workaround 1: If the system's keyboard is not a US-English keyboard, perform the following steps during installation:

  1. When the Proposed Window System Configuration For Installation is displayed, press Esc.

    Note –

    The information on the Proposed Window System Configuration For Installation, which includes the keyboard type, is displayed only for 30 seconds. If you want to change configuration settings, you must press Esc before the 30 seconds lapse. Otherwise, the installation continues by using the displayed settings.

  2. Change the keyboard type to the type that corresponds to your system's keyboard.

  3. Press Enter to accept the changes and continue with the installation.

Workaround 2: If you want to change the keyboard type in a system that is already running Solaris 10 OS, use the kdmconfig program. Choose the option that applies to the type of X server your system is running.

SPARC: jfca Driver for Certain Host Bus Adapters That Are Connected to Tape Devices Might Cause Errors (6210240)

The jfca driver for the following host bus adapters (HBAs) might cause system panics or I/O failures when these HBAs are connected to tape devices:

The jfca driver for these HBAs is prone to race conditions when certain operations are being run, and thus causes the errors. The operations are the following:

Error messages similar to the following examples might be displayed:

Workaround: Do not connect tape devices to either the SG-PCI1FC-JF2 or SG-PCI2FC-JF2 HBA.

Contention Exists Between Certain Devices That Share the Same Bus (6196994)

A bus contention occurs if Quad Fast-Ethernet (QFE) cards share the same bus with any of the following adapters:

The infinite-burst parameter of the ce driver that is used by these adapters is enabled by default. Consequently, little or no bus time is available for the QFE ports that share the same bus.

Workaround: Do not place QFE cards on the same bus as the network adapters in the list.

Some DVD and CD-ROM Drives Fail to Boot Solaris (4397457)

The default timeout value for the SCSI portion of the SunSwiftTM PCI Ethernet/SCSI host adapter (X1032A) card does not meet the timeout requirements of Sun's SCSI DVD-ROM drive (X6168A). With marginal media, the DVD-ROM occasionally experiences timeout errors. The only exceptions are Sun Fire 6800, 4810, 4800, and 3800 systems. These systems overwrite the SCSI timeout value by means of OpenBoot PROM.

Workaround: For other platforms, use the on-board SCSI interfaces or DVD-ROM compatible SCSI adapters, such as the following examples:

iPlanet Directory Server 5.1 Issues

This section provides important information for users of iPlanetTM Directory Server 5.1 who are upgrading to the new Solaris 10 release.

Installing Directory Server 5.1

Sun Java System Directory Server 5 2005Q1 replaces iPlanet Directory Server 5.1 that was integrated in the Solaris 9 Operating System. In Solaris 10 OS, this new Directory Server can be installed as part of the Sun Java Enterprise System.

Note –

For information about the Sun Java System Directory Server 5 2005Q1, refer to the documentation for the Sun Java System at

Solaris 10 OS continues to support Directory Server 5.1. You might need to install Directory Server 5.1 under the following circumstances:

In Solaris 10 release, you install the Directory Server 5.1 manually. Follow these steps:

  1. Insert the Solaris 10 Software - 5 CD into your CD-ROM drive.

  2. Become superuser.

  3. In a terminal window, install the Directory Server.

    # cd /cdrom/cdrom0/Solaris_10/Product/
    # pkgadd -d . IPLTnls IPLTnspr IPLTnss IPLTjss IPLTpldap \
    IPLTdsr IPLTdsu IPLTadmin IPLTcons IPLTadcon IPLTdscon \
    IPLTadman IPLTdsman

    To install Simplified Chinese localization packages, issue the following additional command:

    # pkgadd -d . IPLTcdsu IPLTcadmin IPLTccons IPLTcadcon \
    IPLTcdscon IPLTcadman IPLTcdsman

    To install Japanese localization packages, issue the following additional command:

    # pkgadd -d . IPLTjdsu IPLTjadmin IPLTjcons IPLTjadcon \ 
    IPLTjdscon IPLTjadman IPLTjdsman
  4. After installation is complete, configure iPlanet Directory Server 5.1. Refer to Chapter 11, Sun ONE Directory Server Configuration, in System Administration Guide: Naming and Directory Services (DNS, NIS, and LDAP) .

Migrating to the Sun Java System Directory Server 5 2005Q1

Caution – Caution –

The database formats of the two Directory Server versions are incompatible. Thus, if you are a Directory Server 5.1 user, Sun recommends that you migrate your database to a database that is formatted for the Sun Java System Directory Server 5 2005Q1.

To perform a migration, both versions of the Directory Server must exist in the system that has been upgraded to the Solaris 10 OS. If you are a DS 5.1 user, but are using the compressed archive (.tar.gz) delivery format, you can skip immediately to the migration instructions in Step 2.

  1. On a terminal window, check whether iPlanet Directory Server 5.1 packages are present in your system.

    $ pkginfo | grep IPLT

    If the following packages appear as output, then you can go to Step 2 to proceed with the migration. The output indicates that the iPlanet Directory Server 5.1 packages are in the system.

    system  IPLTadcon  Administration Server Console
    system  IPLTadman  Administration Server Documentation
    system  IPLTadmin  Administration Server
    system  IPLTcons   Console Client Base
    system  IPLTdscon  Directory Server Console
    system  IPLTdsman  Directory Server Documentation
    system  IPLTdsr    Directory Server (root)
    system  IPLTdsu    Directory Server (usr)
    system  IPLTjss    Network Security Services for Java
    system  IPLTnls    Nationalization Languages and Localization Support
    system  IPLTnspr   Portable Runtime Interface
    system  IPLTnss    Network Security Services
    system  IPLTpldap  PerLDAP

    If the packages do not exist, then install the iPlanet Directory Server 5.1 packages first. Refer to the 4-step procedure in the preceding section Installing Directory Server 5.1. After installation is complete, go to Step 2 to proceed with the migration.

  2. Migrate your iPlanet Directory Server 5.1 database to the current version. For instructions, refer to the documentation collection for the Sun Java System Directory Server at

After migrating your data, make sure you continue to back up directory data in the same way as you backed up directory data before migration. Future disaster recovery might require the migrated database.

Localization Issues

This section describes localization issues that apply to Solaris 10 OS.

Swedish Software Translations Note

Swedish software translations are no longer updated since the Solaris 10 8/07 release except the ones translated by communities. Thus, updated messages are displayed in English.

Workaround: None.

Multiple Input Method Switcher Applications Appear in Trusted Java DS

When you log in to the Trusted Java DS with UTF-8 or Asian locales, the Input Method Switcher application, iiim-panel, appears per label by default. Thus in multiple label environment, multiple iiim-panel appears, which could be confusing to the user.

No error message is displayed.

Workaround: Stop using the iiim-panel. Perform the following steps:

To switch the input language, you can also use Hotkey. To enable Hotkey, perform the following steps:

Note –

When Attach to each application is selected, the language switcher list will not be displayed for GTK applications. You can switch input language by using Hotkey.

Wnn8 Japanese Input Method

Wnn8 Japanese Input method cannot be used if the Wnn8 servers are not enabled.

Workaround: Enable the Wnn8 servers:

# svcadm enable wnn8/server

In addition, select Wnn8 as the Japanese Language engine by running the iiim-properties command.

Input Method Cannot Be Enabled With Primary Administrator Rights (6475081)

A user who has the Primary Administrator right can not use the input method for specific locales which prevents that user from entering characters normally. The input method status is not displayed in the workspace. No error message is displayed.

Workaround: Add the following lines to the /etc/security/exec_attr file:

Primary Administrator:solaris:cmd:::/usr/bin/csh:uid=0;gid=0
Primary Administrator:solaris:cmd:::/usr/bin/ksh:uid=0;gid=0
Primary Administrator:solaris:cmd:::/usr/bin/sh:uid=0;gid=0

For information about the file format, see the exec_attr(4) man page.

New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)

When you upgrade the OS to the Solaris 10 6/06 or Solaris 10 11/06 release, the input method framework and individual input methods get upgraded from rev.10 to rev.12. However, ChuYin is not in the list of supported input methods. Also, you cannot use the function keys F2 and F3 to switch methods

Workaround: Use PinYin to type traditional Chinese characters with Hanyu PinYin. Use Ctrl+Shift to switch input methods.

AltGr Does Not Work As Mode Switcher in Some Russian Locales (6487712)

The AltGr key does not work as a mode switcher for the Russian Xsun layout inru_RU.KOI8-R and ru_RU.ANSI1251 locales.

Workaround 1: Switch to the ru_RU.UTF-8 or the ru_RU.ISO8859-5 locale.

Workaround 2: Use IIIMFTM instead of the Russian keyboard layout.

Arabic Text Not Appearing in ar Locales

If your x86 system is using Xorg as the default Xserver, the Arabic font (iso7759-6) does not appear in the ar locale. This error does not occur if you are using XSun instead of XOrg.

Workaround: Follow these steps.

  1. As superuser, edit /usr/dt/config/Xservers.

    • Uncomment or add the following line:

      :0 Local local_uid@console root /usr/openwin/bin/Xsun :0 
      -nobanner -defdepth 24
    • Comment out the following line:

      :0 Local local_uid@console root /usr/X11/bin/Xorg :0
  2. Reboot the system.

Alternatively, you can log in to ar_EG.UTF-8 or other UTF-8 locales.

Several Arabic Fonts Do Not Work in GNOME (6384024)

In GNOME when you select certain Arabic fonts, the characters do not display. This problem appears when you select fonts for applications, the desktop, or the window title using the GNOME font properties menu. The affected fonts include:

No error message is displayed.


Use any of the newly delivered Kacst family of fonts to display Arabic characters in GNOME applications.

Unable to Switch Input Language on Session-Saved Applications (6360759)

Multiple language input is supported in UTF-8 locales, but the language switch is not working with session-saved applications where mouse button 1 is clicked first after login. This problem occurs with the Java Desktop System (Java DS). No error message is displayed.


Click mouse button 1 on the background workspace or Launch Menu before clicking any application.

Keyboard Shortcuts in Mozilla in ES Locale Are Unusual and Ambiguous (6288620)

The keyboard shortcuts in Mozilla 1.7 are unusual, especially in Spanish locale. For example, Ctrl-S is being used for copying as well as for saving. No error message is displayed.


Identify the shortcut keys assigned to user actions from menu in the product.

Migration Note to UTF-8 locales

When migrating to UTF-8 locales, the files affect the method that you use to import or export data.

Microsoft Office Files

Microsoft Office files are encoded in Unicode. StarOffice applications can read and write the Unicode encoded files.

HTML Files

HTML files authored using HTML editors such as Mozilla Composer, or HTML files saved by a web browser, usually contain a charset encoding tag. After exporting or importing, you can browse such HTML files with the Mozilla Navigator web browser, or edit the files with Mozilla Composer, according to the encoding tag in the HTML file.

Fixing Broken HTML File

Some HTML files might be displayed in garbage characters. This problem is typically due to the following reasons:

To find the charset encoding tag in the HTML file, perform the following actions:

  1. Open the file with Mozilla.

  2. Press Ctrl-i, or click View to open the View menu.

  3. Click Page Info.

The charset information is in the bottom of the General tab, for example:

Content-Type text/html; charset=us-ascii

If the string charset=us-ascii does not match the actual encoding of the file, the file might appear broken. To edit the encodings of the HTML file, perform the following actions:

  1. Open the file with Mozilla Composer.

  2. Open the File menu.

  3. Select Save as Charset.

  4. Choose the correct encoding. Mozilla Composer automatically converts the encoding and the charset tag as appropriate.

Emails Saved As Portable Format

Modern mails are tagged with the MIME charset tag. The Email and Calendar application accepts MIME charset tags. You do not need to perform any encoding conversion.

Plain Text Files

Plain text files do not have a charset tag. If the files are not in UTF-8 encoding, encoding conversion is needed. For example, to convert a plain text file encoded in Traditional Chinese big5 to UTF-8, execute the following command:

iconv -f big5 -t UTF-8 inputfilename

 > outputfilename

You can also use the File System Examiner for the encoding conversion.

You can use the Text Editor to read and write character encoding text automatically or by specifying an encoding explicitly when opening or saving a file.

To start Text Editor, click Launch, then choose Applications->Accessories->Text Editor.

File Names and Directory Names

If file names and directory names using multibyte characters are not in UTF-8 encoding, encoding conversion is needed. You can use File System Examiner to convert file and directory names and the contents of plain text files from legacy character encodings to UTF-8 encoding. Refer to the online Help for File System Examiner for more information.

To start File Systems Examiner, click Launch, then choose Applications->Utilities->File System Examiner.

When you access non-UTF-8 file or directory names on Microsoft Windows via SMB using File Manager, you can access the non-UTF-8 file or directory names without encoding conversion.

Launching Legacy Locale Applications

For applications that are not ready to migrate to Unicode UTF-8, you can create a launcher on a front panel to start the application in legacy locales. You can also launch the applications directly from the command line. Perform the following steps to create a launcher for an application.

  1. Right-click on the panel where you want to place the launcher.

  2. Choose Add to Panel->Launcher.

  3. Use the following format to type the entry in the Command field in the Create Launcher dialog:

    env LANG=locale LC_ALL=
    locale application name

    For example, if you want to launch an application called motif-app from /usr/dt/bin in the Chinese Big5 locale, enter the following text in the Command field of the Create Launcher:

    env LANG=zh_TW.BIG5 LC_ALL=zh_TW.BIG5 /usr/dt/bin/motif-app
  4. Click OK to create the launcher on the panel.

When you need to run CLI (command line interface) applications which are specific to a legacy locale, open a Terminal window in the legacy locale first and then run the CLI applications in the same Terminal window. To open a Terminal window in a legacy locale, enter the following command:

eng LANG=locale LC_ALL=locale GNOME-TERMINAL –disbable-factory.

Instead of opening a new Terminal window in a legacy locale, you can switch the locale setting from UTF-8 to a legacy locale in the current Terminal window by changing the encoding the Set Character Encoding menu in the Terminal window. Then you must also set the LANG and LANG environment variables to the current shell.

Hardware for Some Keyboards Layouts Type 6 and 7 Not Available

Software support for some keyboard layouts has been added to the Solaris OS. This software gives users greater flexibility for keyboard input by modifying standard U.S. keyboard layouts to their own language needs.

Currently, no hardware is available for the following keyboard layout types:




French Canadian 









Malta UK 

Malta US 


Brazil Portuguese 


Serbia and Montenegro 



Workaround: Choose one of the following workarounds:

Networking Issues

The following networking bugs apply to the Solaris 10 release.

DR and showdevices Do Not Work After XSCF Reboot (6821108)

After rebooting the XSCF service processor on OPL systems, IPsec communications are lost. The following error message is seen on XSCF service processor:

XSCF> showdevices -d 0

Can't get device information from DomainID 0.

The following message is seen in the /var/adm/messages file on the domain:

Apr  7 11:19:20 domain-0 sckmd: [ID 205163 daemon.error] 
PF_KEY error: type=ADD, errno=17: File exists, diagnostic code=0: No diagnostic

This problem occurs because the existing Security Associations (SAs) on the domain are not deleted properly, and so the addition of the new SAs fail.

Workaround 1: Reboot the XSCF service processor twice. Half the SAs are deleted the first time and the remaining half are deleted the second time. The second addition succeeds and IPsec communication is reestablished.

Workaround 2: Delete the IPsec SAs twice on each domain before rebooting the service processor.

If you do not use IPsec for anything else on the system, the ipseckey flush will display all the SAs. If you use IPsec for other things, perform the following steps to display all SAs:

  1. Get the IP addresses:

    # /usr/platform/SUNW,SPARC-Enterprise/sbin/prtdscp
    Domain Address:
    SP Address:
  2. Delete the SPIs twice using the ipseckey and prtdscp utilities:

    # ipseckey delete ah spi 0xff00 dst 
    `/usr/platform/SUNW,SPARC-Enterprise/sbin/prtdscp -s`
    #  ipseckey delete ah spi 0xff00 dst 
    `/usr/platform/SUNW,SPARC-Enterprise/sbin/prtdscp -s`
    # ipseckey delete ah spi 0xff dst 
    `/usr/platform/SUNW,SPARC-Enterprise/sbin/prtdscp -d`
    # ipseckey delete ah spi 0xff dst 
    `/usr/platform/SUNW,SPARC-Enterprise/sbin/prtdscp -d`

    When the service processor reboots, the keys are added correctly.

x86: bnx Driver Does Not Support Broadcom NetXtreme II 5709 Chipset (6637053)

The Broadcom NetXtreme II 5709 (BCM5709) chipset is not supported in the Solaris 10 5/09 release.

Workaround: Download the bnx driver from the web site.

Note –

Existing chipsets might experience performance regression issues when the downloaded driver is installed.

SPARC: NFS/RDMA Connection Errors (6229077)

Connection errors might occur between an NFS server and client that are using Remote Direct Memory Access (RDMA). Because of these errors, the buffer pool resources are exhausted and the system panics. The following error message is displayed:

rpcib: WARNING: rib_rbuf_alloc: No free buffers!

Workaround: Choose one of the following workarounds:

For more information, see the mount_nfs(1M) and nfs(4) man pages.

Login Fails on iSCSI Target With Two Portals and One Bad Portal (6476060)

If an iSCSI target or an array returns more than one IP address as part of its send target response, the initiator takes into account only the last address in the list and not the first one, as it used to prior to this release. As a result, if the last IP address is bad or invalid, the connection to this target fails.

Workaround: Return the different target portal group tags (TPGT) for each entry in its send target response. The initiator tries to establish a connection to all the IP addresses so that the connection succeeds.

System Domain of Interpretation Is Not Configurable (6314248)

The system Domain of Interpretation (DOI) is not configurable. When the Solaris Management Console is used to create a new trusted network template, the Solaris Management Console sets the DOI to 0 and Solaris Trusted Extensions does not function correctly. Various error messages are displayed.

Workaround: Set the DOI to 1 using the Solaris Management Console.

IP Forwarding Disabled by Default in Solaris 10 OS

In this Solaris release, IP forwarding is disabled by default. This setting applies to both IPv4 and IPv6 regardless of other system configurations. Systems with multiple IP interfaces that formerly forwarded IP packets by default no longer have this automatic feature. To enable IP forwarding in multihomed systems, administrators must manually perform additional configuration steps.

Workaround: The command routeadm enables IP forwarding. The configuration changes that are the result of routeadm usage persist across system reboots.

For more information about IP forwarding, see the routeadm(1M) man page.

Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)

A zone can be configured so that the zone's IP address becomes part of an IP Network Multipathing (IPMP) group. The configuration process is documented in How to Extend IP Network Multipathing Functionality to Shared-IP Non-Global Zones in System Administration Guide: Solaris Containers-Resource Management and Solaris Zones.

If all the network interfaces in the IPMP group fail, a zone does not boot if it has an IP address that is part of the IPMP group.

The following example illustrates the result if you attempt to boot the zone.

# zoneadm -z my-zone boot 
zoneadm: zone 'my-zone': bge0:1: 
could not set default interface for multicast: Invalid argument 
zoneadm: zone 'my-zone': call to zoneadmd failed

Workaround: Repair at least one network interface in the group.

Security Issues

The following security issues applies to the Solaris 10 release.

Nonpassword Logins Fail With pam_ldap Enabled (6365896)

After the account management PAM module for LDAP (pam_ldap) is enabled, users must have passwords to log in to the system. Consequently, nonpassword-based logins fail, including those logins that use the following tools:

Workaround: None.

Solaris Commands and Standards

The following section describes behavior changes in certain commands and standards in Solaris 10 OS.

SPARC: Applications Noncompliant With 8–byte Aligned Mutexes Fail (6729759)

Objects of type mutex_t and pthread_mutex_t must start at 8-byte aligned addresses. Applications that do not satisfy this requirement fail. The following error message is displayed:

*** _THREAD_ERROR_DETECTION: lock usage error detected ***
"mutex is misaligned"
"condvar is misaligned"

Workaround: Setting the environment variable to the following values causes alignment errors to be reported on stderr:

Users should test their applications with the THREAD_ERROR_DETECTION environment variable set to one of these values and request corrections to noncompliant applications.

winbind Fetches Only the First 1000 Active Directory Users

This bug occurs while using the Samba server with winbind in an Active Directory environment. The Solaris 10 5/09 release includes the Samba 3.0.28 software version. When querying all the users or more than 1000 users from the Active Directory server, winbind fetches only the first 1000 results.

Workaround: None.

PgAdmin III 1.6 Does Not Support PostgreSQL version 8.3

PgAdmin III 1.6 cannot be used to administer PostgreSQL 8.3 version. PgAdmin 1.6 does not understand catalog structures in the new PostgreSQL version. Various error messages are displayed.

Workaround: Upgrade to PgAdmin III version 1.8.

Changed Man Pages for Solaris Trusted Extensions Are in Reference Manual Only

The following Solaris Trusted Extensions man pages are revised for this release:

The revised man pages cannot be viewed using the man command. To view the revised man pages, see the Solaris Trusted Extensions Reference Manual.

Bash 3.00 No Longer Sets Some Environment Variables

Solaris 10 OS includes Bash 3.00. This shell no longer automatically exports the following variables to the environment:

This new behavior applies even if the shell assigns default values to these variables.

Workaround: Export these variables manually.

New ln Utility Requires -f Option

The behavior of /usr/bin/ln has changed to adhere to all of the standards from SVID3 through XCU6. If you use the ln command without the -f option to link to an existing target file, the link is not established. Instead, a diagnostic message is written to standard error, and the command proceeds to link any remaining source files. Finally, the ln command exits with an error value.

For example, if file b exists, the syntax ln a b generates the following message:

ln: b: File exists

This behavior change affects existing shell scripts or programs that include the ln command without the -f option. Scripts that used to work might now fail in Solaris 10 OS.

Workaround: Use the -f option with the ln command. If you have existing scripts that execute the link utility, make sure to modify these scripts to comply with the command's new behavior.

New tcsh Rejects setenv Variable Names That Use a Dash or an Equals Sign

In Solaris 10 OS, tcsh has been upgraded to version 6.12. This version no longer accepts environment variables whose names use a dash or an equals sign. Scripts that contain setenv lines and that work in earlier Solaris versions might generate errors in the current Solaris 10 release. The following error message is displayed:

setenv: Syntax error

For more information, refer to the tcsh man page for the Solaris 10 OS.

Workaround: Do not use the dash or equals sign in names for environment variables.

STDIO getc Family EOF Condition Behavior Change

Applications that were built in strict standard C conformance mode are affected by the behavior changes of certain library functions. An example is applications that were compiled by using the cc -Xc or c89 compilation mode. The behavior has changed for the following library functions:

A formal interpretation of the 1990 C Standard requires that after an end-of-file condition is set, no more data is returned from the file on subsequent input operations. The exception is if the file pointer is repositioned or the error and end-of-file flags are explicitly cleared by the application.

The behavior for all other compilation modes remains unchanged. Specifically, the interfaces can read additional newly written data from the stream after the end-of-file indicator has been set.

Workaround: Call fseek() or clearerr() on the stream to read additional data after the EOF condition has been reported on the stream.

Output Columns of the ps Command Have Been Widened

Due to larger UIDs, processor ids, and cumulative execution time, the columns of the ps command output have been widened. Customer scripts should not assume fixed output columns.

Workaround: Scripts should use the -o option of the ps command.

For more information, see the ps(1) man page.

Solaris Volume Manager

The following Solaris Volume Manager bug applies to the Solaris 10 release.

Solaris Volume Manager metattach Command Might Fail

If you have a Solaris Volume Manager mirrored root (/) file system in which the file system does not start on cylinder 0, all submirrors you attach must also not start on cylinder 0.

If you attempt to attach a submirror starting on cylinder 0 to a mirror in which the original submirror does not start on cylinder 0, the following error message is displayed:

can't attach labeled submirror to an unlabeled mirror

Workaround: Choose one of the following workarounds:

Note –

By default, the JumpStart installation process starts swap at cylinder 0 and the root (/) file system somewhere else on the disk. Common system administration practice is to start slice 0 at cylinder 0. Mirroring a default JumpStart installation with root on slice 0, but not cylinder 0, to a typical secondary disk with slice 0 that starts at cylinder 0, can cause problems. This mirroring results in an error message when you attempt to attach the second submirror. For more information about the default behavior of Solaris installation programs, see the Solaris 10 Installation Guides.

Sun Java Desktop System

This section describes issues that apply to the Sun Java Desktop System (Java DS) in the Solaris 10 OS.

Email and Calendar

This section describes issues related to Email and Calendars.

Problem With Changing Authentication Type (6246543)

After you change the authentication type for the incoming mail server, Email and Calendar might not work correctly.

Workaround: Restart Email and Calendar.

Login Issues

This section describes login issues.

Login Error Message

You might encounter the following error message when you log in to a Java Desktop System session:

Could not look up internet address for hostname.
This will prevent GNOME from operating correctly.
It may be possible to correct the problem by adding 
hostname to the file /etc/hosts

Workaround: Ensure that your hostname is set up correctly in the /etc/hosts file. Perform the following steps:

  1. Set the hostname in the /etc/hosts file as follows: localhost loghost hostname

    hostname is the name of your system.

  2. Ensure that your hostname is listed in the /etc/nodename file. This file must also contain the following line: localhost loghost hostname

Help System

Wrong Help Window Opened For Volume Control (6253210)

If you use the Yelp browser to open the online help for Volume Control, the help file for the Keyboard Accessibility panel application is opened instead.

Workaround: None.

Mozilla Browser

Cannot Print Certain Documents From the Mozilla Browser

You cannot print documents from the Mozilla browser if the documents contain Unicode characters that are not in the Basic Multilingual Plane (BMP).

Workaround: None.

System-Level Issues

User Preferences Not Fully Compatible

User preferences in your home account for an earlier version of the GNOME Desktop might be partly incompatible with the version on the Java DS Release 3.

Workaround: Reset your preferences. Perform the following steps:

  1. Log out of the Java Desktop System.

  2. Click Session and choose Failsafe terminal.

  3. Log in.

  4. In the failsafe terminal window, enter the following commands:

    % gnome-cleanup exit
  5. Log in again.

    Your GNOME preferences are now reset.

Problems With Online Registration of StarOffice Software (6208829)

You might be unable to complete the online registration of the StarOffice software if the software cannot find Mozilla on the system. The software must be able to locate the Email and Calendar application to successfully send documents.

Workaround: Add /usr/sfw/bin to your PATH. Perform the following steps.

  1. Open a terminal window.

  2. Issue the following command:

    % export PATH=/usr/sfw/bin:$PATH
  3. To start the StarOffice software, issue the following command:

    % soffice
  4. Complete the StarOffice registration procedure.

Problems With Sound Recorder

The slide bar and the side counter do not work when the Sound Recorder is recording a new.wav file.

Workaround: None.

Nautilus ACL MASK is Not in Sync With Group Permissions (6464485)

The Group permissions in the Permissions tab should be the same as the Mask permissions in the Access Tab, but on some occasions they appear out of sync.

Workaround: Click the Close button, and then click Reload. View the file properties again. The Group permissions and the Mask permissions will now be in sync again. The permissions are set to what you changed the Mask to in the previous step.

strftime(3c) Should Support GNU Extension in %-m And %-d (6448815)

The Java DS menu bar and some applications, like Evolution, incorrectly display Chinese date. The incorrect date is displayed in the %-m M %-d D format where M and D are the month and date in Chinese respectively.

Workaround: Perform the following steps:

  1. Backup the /usr/share/locale/LC_MESSAGES/gnome-panel*.mo file.

  2. Download gnome-panel.gnome-2-16.zh_CN.po from and save it under the /tmp directory.

  3. Edit the file gnome-panel.gnome-2-16.zh_CN.po and replace all occurrences of %-m with %Om, and %-d with %e.

  4. Generate a new gnome-panel.gnome-2-16.zh_CN.po file.

    msgfmt -v -o /tmp/gnome-panel.gnome-2-16.zh_CN.po

    Copy the file back to the /usr/share/locale/LC_MESSAGES/ directory.

  5. Log out of the system and re-login.

x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card

If your Solaris 10 system has a single physical video card, you cannot configure the system for full-screen magnification. For such a configuration, you must use a separate configuration file in which you define settings for a dummy driver. First, make sure that the Xserver is not running. Then perform the following steps:

  1. Log in to a command-line session.

    • If you are using the GNOME Display Manager, follow these steps:

      1. Log in to a session as superuser.

      2. At the prompt, type svcadm disable application/gdm2-login .

      3. Log in again as superuser.

    • If you are using dtlogin, follow these steps:

      1. In the dtlogin window, click Options and select Command Line Login.

      2. Log in as superuser.

  2. Create a new xorg.conf file.

    # /usr/X11/bin/Xorg -configure

    The command creates the file in the root (/) directory.

  3. Copy the new configuration file to the /etc/x11 directory and rename the file xorg.conf.

    # cp / /etc/X11/xorg.conf
  4. Modify the configurations in the file by using the following sample configurations:

    • Add a new monitor section.

      Section "Monitor"
       	Identifier   "monitor_dummy"
       	ModelName    "dummy"
       	HorizSync    10-200
         	VertRefresh  20-90
    • Add a new device section.

      Section "Device"
         BoardName    "dummy"
         Driver       "dummy"
         Identifier   "device_dummy"
         VendorName   "dummy"
         videoram	10000

      Note –

      You might need to adjust the videoram value, depending on the screen width, height, and color depth of your particular graphics card. The value in Kbytes must be large enough for the intended screen. For example, you can compute the value by using the formula width * height * bpp/8.

    • Add a new screen section.

      Section "Screen"
         DefaultDepth 24
         SubSection "Display"
           Depth      24
           Modes      "1280x1024"
         Device       "device_dummy"
         Identifier   "screen_dummy"
         Monitor      "monitor_dummy"

      Note –

      You might need to adjust the resolution value for your particular system setup.

  5. Look for the following line under the ServerLayout section:

    Screen      0  "Screen0" 0 0
  6. Insert the following line below the line in the previous step:

    Screen      1  "screen_dummy" RightOf "Screen0"

    This new line defines Screen1, a second dummy screen that is notionally to the right of Screen0, the physical and primary screen.

  7. Save the changes.

  8. Reboot the system from the appropriate command-line session:

    • If you are using GDM, perform the following:

      1. Type svcadm enable application/gdm2-login.

      2. Reboot the system.

    • If you are using dtlogin, reboot the system and log in.

  9. Start the Gnopernicus screen reader.

  10. Change the Startup Mode to Magnifier.

  11. Click Preferences, then select Magnifier.

  12. Click Add/Modify.

  13. Assign the following values for Magnifier preferences:

    • For Source: 0.1

    • For Zoomer Placement:

      • Left and Top: 0

      • Bottom and Right: maximum

  14. Click Apply.

    Because of the overlaying full-screen magnification zoomer, the Gnopernicus windows become invisible. However, full-screen magnification is now available.

Certain View Options Might Cause File Manager to Fail (6233643)

The File Manager might fail if you use the following View options:

Depending on the View options that you use, the following error messages might be displayed:

Workaround: None. Every time these problems occur, restart File Manager or click the Restart Application button on the crash dialog box.

System Administration

This section describes system administration bugs in Solaris 10 OS.

SPARC: Solaris Volume Manager GUI Fails to Start (6671736)

The Solaris Volume Manager GUI fails to start successfully. However, no system panic is detected.

Workaround: Remove the following lines from the /var/sadm/smc/toolboxes/smc/smc.tbx file.


SPARC: FKU 137137-xx Does Not Support Third-Party Volume Manager Software

The FKU 137137-xx patch does not support third-party Volume Manager software, with some exceptions. This lack of support is due to prepatch, postpatch, and postbackout implementation. If users use unsupported third-party Volume Manager software, they cannot apply the FKU patch. The following error message is displayed during patch installation:

unsupported root slice type xxxxx

However, the Fujitsu and Veritas Volume Manager software is supported.

Workaround: None.

Do Not Use patchadd -M to Install Patches on a System With Non-Global Zones

On a system with non-global zones, it is recommended not to use the patchadd -M option. The current implementation of patchadd -M applies all the patches to the global zone first, and only then to the non-global zones. This is sub-optimal, because if an issue occurs after a number of patches have been applied to the global zone but not to the non-global zone, the zones may be significantly out of sync with each other, making the situation potentially difficult to recover.

Workaround: patchadd -a -M can be used to construct a valid install sequence for a set of patches and to ensure that the patches should install without an issue.

For more information, see the Best Practices article on the BigAdmin Patching Hub, at

::findleaks Command Fails (6720107)

The mdb debugger ::findleaks command fails on the Solaris 10 5/09 OS. The following error message is displayed:

mdb: couldn't walk 'modctl': unknown walk name

Workaround: Before using the ::findleaks command, type the ::load krtld command.

Solaris 10 5/09 DVD Media Might Not be Automatically Mounted by vold (6712352)

The Solaris 10 5/09 DVD does not mount by default during runtime. No error message is displayed.

Workaround: Perform the following steps:

  1. Become superuser.

  2. Disable vold:

    • On Solaris 10 Systems:

      # svcadm disable -t volfs
    • On Solaris 8 and Solaris 9 systems:

      /etc/init.d/volmgt stop
  3. Mount the media manually by using the # mount -F hsfs path to block device path to mount point command. For example:

    # mount -F hsfs /dev/rdsk/c0t2d0s2 /mnt

Cannot Log In to Solaris Management Console After Enabling Solaris Trusted Extensions (6639493)

The SolarisTM Management Console hangs and does not allow root login to the Solaris Management Console after enabling Solaris Trusted Extensions. The following error message might be displayed the Solaris Management Console hangs:

Configuring the Management Server...

Workaround: Perform the following steps:

  1. Configure Solaris Trusted Extensions and start the Solaris Management Console.

  2. Choose Open ToolBox from the Console menu.

  3. Select localhost if it is listed.

  4. If localhost is not listed, then type localhost.

  5. Choose the Policy=TSOL toolbox.

  6. Log in again to the Solaris Management Console as root.

  7. (Optional) If the second login to the Solaris Management Console fails, repeat steps 1 through 5 by typing instead of localhost in step 3.

zoneadm attach Command Might Fail (6550154)

When you attach a zone, if the original host and the new host have packages at the same patch level but at different intermediate patch histories, the zone attach might fail. Various error messages are displayed. The error message depends on the patch histories of the two hosts.

Workaround: Ensure that the original host and the new host machines have had the same sequence of patch versions applied for each patch.

Solaris is Unable to Handle Mode Switches Between Legacy and AHCI Modes for the SATA Controller (6520224)

In systems which have an AHCI compliant SATA controller, the BIOS setup typically enables the controller to be set in either AHCI, legacy, or RAID modes. Solaris supports AHCI and legacy modes.

The SATA mode setting in BIOS must not be changed after an initial Solaris installation. The SATA mode setting must also not be changed before or after a Solaris upgrade. If the SATA mode BIOS setting is modified after installing Solaris, the system will reset and fail to boot without indicating what led to the failure.

Workaround: If boot failure is encountered as a result of changing the BIOS setting, revert back to the original setting in order to boot Solaris.

Deferred Activation Patching (6486471)

Starting with patch 119254-42 and 119255-42, the patch installation utilities, patchadd and patchrm, have been modified to change the way that certain patches delivering new features or existing files that are incompatible with the running system are handled. This utilities modification affects the installation of these patches on any Solaris 10 release. These “deferred-activation” patches handle the large scope of change delivered in Kernel patches better.

In deferred Activation patching, a loopback file system, lofs, is used to create a copy of the root file system. The original files being patched are copied to a safe location and the lofs copy of the root file system is patched. Then the original file is lofs mounted back over the new file as it is patched. This means the running system remains consistent over the duration of patching, new features are not active and any incompatible change is hidden until the user reboots.

Users must reboot as soon as possible after applying a Deferred Activation Patch, but they do not have to reboot immediately, they can still add further patches then reboot.

The patch README provides instructions on which patches require a reboot.

Note –

Sun strongly recommends that patch operations are carried out in a single-user mode, especially when this is recommended by the patch README.

If you are running non-global zones or have lofs disabled, consider the following points when installing or removing deferred-activation patches:

No error message is displayed.

Workaround: Sun recommends Solaris Live Upgrade to manage patching. Solaris Live Upgrade prevents the problems of patching a running system. Solaris Live Upgrade reduces the amount of downtime involved in patching and reduces risk by providing fallback capability if problems occur. For more information, see Solaris 10 5/09 Installation Guide: Solaris Live Upgrade and Upgrade Planning.

Possible Error With 32-bit Applications Getting File System State on Large File Systems (6468905)

When run on large file systems, for example ZFS, applications using statvfs(2) or statfs(2) to get information about the state of the file system exhibit an error. The following error message is displayed:

Value too large for defined data type

Workaround: Applications should use statvfs64() instead.

Using patchadd With the -R Option To Specify an Alternative Root Path From Systems That Are Not Zones Aware Should Be Restricted (6464969)

On systems running a Solaris release that is not zones aware, using patchadd -R, or any command that accepts the -R option to specify an alternate root path for a global zone that has non-global zones installed, will not work.

In contrast with the error message that is displayed by using the luupgrade [-t, -T, -p, -P] command, no error message regarding the use of appropriate command-level restrictions is displayed in this instance.

There is no indication that the -R option did not work. As a result of the failure of the command, Solaris 10 packages or patches are not installed on any of the installed non-global zones.

This problem occurs while installing and uninstalling packages or patches.

Note –

The -R option works if the alternate boot environment has configured non-global zones, but no installed non-global zones. However, to avoid a potential problem, or if you are not sure whether there are any installed non-global zones used as the alternate root path, restrict the use of the -R option in all instances.

For more information, see the following man pages :

Workaround 1: Upgrade the OS to at least the Solaris 10 1/06 release.

If you are running the Solaris 10 3/05 release, install the following patches to enable the use of commands that accept the -R option to create an alternate root path:

Workaround 2: Restrict the use of the patchadd -R command or any command that accepts the -R option to create an alternate root path.

Instead, boot the alternate root, for example, the Solaris 10 release, as the active OS. Then install and uninstall the Solaris 10 packages and patches without using the -R option.

Sun Patch Manager Tool 2.0 Not Compatible With Previous Versions

A system that runs the Sun Patch Manager Tool 2.0 can manage remote systems that run Patch Manager Tool, including Sun Patch Manager Tool 1.0.

However, a system with an earlier version of Patch Manager Tool cannot manage remote systems that run Patch Manager Tool 2.0. Earlier versions include the following:

Note –

Common Information Model/Web Based Enterprise Management (CIM/WBEM) support for Patch Manager Tool does not exist in the Solaris 8 OS. Consequently, remote management with Patch Manager does not apply to Solaris 8 systems.

Cannot Delete Existing Diskless Clients From the System (6205746)

If you use the smdiskless command to delete a diskless client, the command fails. The diskless client is not removed from the system databases. The following error message is displayed:

Failing with error EXM_BMS.

Workaround: Unshare the /export partition before adding the client.

SPARC: smosservice delete Command Does Not Successfully Remove All Directories (6192105)

If you use the smosservice delete command to remove a diskless client service, the command does not successfully remove all the service directories.

Workaround: Follow these steps.

  1. Make sure that no clients exist that use the service.

    # unshare /export/exec/Solaris_10_sparc.all
    # rm -rf /export/exec/Solaris_10_sparc.all
    # rm -rf /export/exec/.copyofSolaris_10_sparc.all
    # rm -rf /export/.copyofSolaris_10
    # rm -rf /export/Solaris_10
    # rm -rf /export/share
    # rm -rf /export/root/templates/Solaris_10
    # rm -rf /export/root/clone/Solaris_10
    # rm -rf /tftpboot/inetboot.sun4u.Solaris_10
  2. Remove the following entry from the /etc/bootparams file.

    fs1-24 boottype=:os

    Note –

    Remove this entry only if this file server does not provide functions or resources for any other services.

  3. Remove the following entry from the /etc/dfs/dfstab file.

    share -F nfs -o ro /export/exec/Solaris_8_sparc.all/usr
  4. Modify the /var/sadm/system/admin/services/Solaris_10 file.

    • If the file server is not Solaris_10, delete the file.

    • If the file server is Solaris_10, remove all entries after the first three lines. The deleted lines indicate the service USR_PATH and SPOOLED ROOT packages in /export/root/templates/Solaris_10 and the supported platforms.