2. Oracle Solaris Runtime Issues
Recommended Adoption of SHA-256 and SHA-512 crypt(3C) Plug-ins for Password Encryption
Problem When Printing to a Local Printer With Thunderbird 3 (6978760)
Trusted Stripe Disappears From the Screen After a Resolution Change (6460624)
The config/local_only Property in sendmail Must Not Be Set to true (6970172)
SPARC: Console sync Command Can Hang While Attempting a Crash Dump (6967825)
32-bit x86: Unable to Use reboot Command to Boot Kernel (6741682)
zpool attach Command Does Not Copy bootblock Information (6668666)
x86: ata Driver Timeouts During Boot (6586621)
zoneadm install Command Fails With a ZFS Legacy Mount (6449301)
ZFS and UNIX/POSIX Compliance Issues
fdisk -E Command Can Sweep Disk Used by ZFS Without Warning (6412771)
ZFS and Third-Party Backup Product Issues
BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support
ZFS GUI Should Check for /usr/lib/embedded_su Patch at the Beginning of Each Wizard (6326334)
Failure to Synchronize File System on Panic (6250422)
Upgrading From Some Oracle Solaris 10 Releases Requires Remounting of File Systems
NFSv4 Access Control List Functions Might Work Incorrectly
System Crash Dump Fails on Devices Greater Than 1 TByte in Size (6214480)
Hardware-Related Issues and Bugs
x64: PCI Subsystem ID Changes in ConnectX Firmware 2.6.0 From Mellanox (6810093)
The ZFS ARC Allocates Memory Inside the Kernel Cage Preventing DR (6522017)
mpathadm Command Does Not Display Load-Balance Setting Specific to Device
Registration Tool Prevents Power Management on Some Frame Buffers (6321362)
Certain USB 2.0 Controllers Are Disabled
Supported USB Devices and Corresponding Hub Configurations
x86: Limitations Exist With Certain Device Drivers in the Oracle Solaris 10 OS
DVD-ROM/CD-ROM Drives on Headless Systems
x86: Manual Configuration Required to Specify Non-U.S. English Keyboards
Contention Exists Between Certain Devices That Share the Same Bus (6196994)
Some DVD and CD-ROM Drives Fail to Boot the Oracle Solaris 10 OS (4397457)
iPlanet Directory Server 5.1 Issues
Installing Directory Server 5.1
Migrating to the Sun Java System Directory Server 5 2005Q1
Swedish Software Translations Note
Multiple Input Method Switcher Applications Appear in Trusted Java DS
New ChuYin Input Method Not Supported in Upgrade to IIIMF rev.12 (6492129)
AltGr Key Does Not Work As a Mode Switcher in Some Russian Locales (6487712)
Arabic Text Not Appearing in ar Locales
Several Arabic Fonts Do Not Work in GNOME Desktop (6384024)
Unable to Switch Input Language on Session-Saved Applications (6360759)
Keyboard Shortcuts in Mozilla 1.7 in ES Locale Are Unusual and Ambiguous (6288620)
Migration Note for UTF-8 Locales
Emails Saved As Portable Format
File Names and Directory Names
Launching Legacy Locale Applications
Hardware for Some Keyboard Layouts Type 6 and 7 Not Available
SPARC: NFS/RDMA Connection Errors (6229077)
System Domain of Interpretation Is Not Configurable (6314248)
IP Forwarding Disabled by Default in the Oracle Solaris 10 OS
Zone Not Booting When IP Address Belongs to a Failed IP Network Multipathing Group (6184000)
Nonpassword Logins Fail With pam_ldap Enabled (6365896)
Oracle Solaris Commands and Standards
winbind Command Fetches Only the First 1000 Active Directory Users
Changed Man Pages for Trusted Extensions Are in Reference Manual Only
Bash 3.00 No Longer Sets Some Environment Variables
New ln Utility Requires -f Option
New tcsh Version Rejects setenv Variable Names That Use a Dash or an Equal Sign
STDIO getc Family EOF Condition Behavior Change
Output Columns of the ps Command Have Been Widened
Solaris Volume Manager Does Not Remove Devices Correctly If fdisk Does Not Have Valid Entries
Solaris Volume Manager metattach Command Might Fail
Problem With Changing Authentication Type (6246543)
Wrong Help Window Opened For Volume Control (6253210)
Cannot Print Certain Documents From the Mozilla Browser
User Preferences Not Fully Compatible
Nautilus ACL MASK Is Not Synchronized With Group Permissions (6464485)
strftime(3c) Should Support GNU Extension in %-m And %-d (6448815)
x86: Cannot Configure Full-Screen Magnification on Systems With One Video Card
Certain View Options Might Cause File Manager to Fail (6233643)
The Availability Suite Module sdbc Fails to Load During Boot (6952222)
Oracle Solaris 10 9/10 Clock Stops on Oracle VM 2.2 (6952499)
SPARC: FKU 137137-xx Patch Does Not Support Third-Party Volume Manager Software
Solaris 10 10/09 DVD Media Might Not Be Automatically Mounted by vold (6712352)
Sun Patch Manager Tool 2.0 Incompatible With Previous Versions of the Tool
Cannot Delete Existing Diskless Clients From the System (6205746)
SPARC: smosservice delete Command Does Not Successfully Remove All Service Directories (6192105)
4. End-of-Software Support Statements
A. Previously Documented Bugs That Were Fixed in the Oracle Solaris 10 9/10 Release
The following hardware–related issues and bugs apply to the Oracle Solaris 10 release.
The Oracle Solaris 10 9/10 release includes a new feature that provides enhanced observability of CPU performance data through kstats. This feature is disabled by default, and enabled by adding the set cu_flags=1 entry to the /etc/system file and rebooting the system. Before enabling this feature on any Mx000 SPARC OPL platform, update the OBP platform firmware to XCP1093 or later. Failure to update the OBP platform firmware before enabling the feature can result in a subsequent failure of an externally initiated reset (XIR), cause OBP to hang, or the kmdb command to fail.
For further information, refer to the README that accompanies the XCP1093 firmware at the download site.
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:
Log in as the root user. The device tree information might look like this:
# ls -R /devices | grep 15b3 /devices/pci@0,0/pci10de,5d@e/pci15b3,634a@0 /devices/pci@0,0/pci10de,5d@e/pci15b3,634a@0/ibport@1,ffff,ipib /devices/pci@0,0/pci10de,5d@e/pci15b3,634a@0/ibport@1,ffff,ipib:ibd0 /devices/pci@0,0/pci10de,5d@e/pci15b3,634a@0/ibport@2,ffff,ipib /devices/pci@0,0/pci10de,5d@e/pci15b3,634a@0/ibport@2,ffff,ipib:ibd1 /devices/pci@0,0/pci10de,5d@e/pci15b3,634a@0:devctl
Note - Device specifics vary depending on the Mellanox-branded card installed.
Edit the path_to_inst file. Perform the following steps:
Make a backup copy of the existing path_to_inst file.
# cp /etc/path_to_inst /etc/path_to_inst.backup
Open the path_to_inst file:
# vi /etc/path_to_inst
Search for lines that contain ibd and hermon, and delete those lines.
Save the changes and close the file.
Remove the entries in the /dev directory:
rm /dev/ibd?*
Reboot the system. The system boots normally, and the corresponding device tree looks like this:
# ls -R /devices | grep 15b3 /devices/pci@0,0/pci10de,5d@e/pci15b3,5@0 /devices/pci@0,0/pci10de,5d@e/pci15b3,5@0/ibport@1,ffff,ipib /devices/pci@0,0/pci10de,5d@e/pci15b3,5@0/ibport@1,ffff,ipib:ibd0 /devices/pci@0,0/pci10de,5d@e/pci15b3,5@0/ibport@2,ffff,ipib /devices/pci@0,0/pci10de,5d@e/pci15b3,5@0/ibport@2,ffff,ipib:ibd1 /devices/pci@0,0/pci10de,5d@e/pci15b3,5@0:devctl
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:
Power off the system and remove the HCA from the bus.
Reboot the system without the HCA installed.
When system is back on, follow steps 2 through 3 listed in Workaround 1.
Power off the system.
Re-intsall the HCA. Reboot the system.
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.
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 SunFire 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
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.
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.
Workaround:
Run the following command approximately 60 seconds after each login:
# pkill -f basicreg.jar # pkill -f swupna.jar
A new cryptographic framework is provided in Oracle 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 Oracle 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 Oracle 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.
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 www.sun.com/io for Solaris Ready products and to www.sun.com/bigadmin/hcl for additional compatible USB products.
For the latest information about USB devices, see http://www.sun.com/io_technologies/USB-Faq.html.
This 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
|
The following list describes limitations with certain drivers and interfaces in this release of Oracle Solaris 10 for x86 platforms:
This functionality is turned off for all device types. In the DDI_SUSPEND code in your detach() function, you should return DDI_FAILURE.
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.
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.
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:
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.
Change the keyboard type to the type that corresponds to your system's keyboard.
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 Oracle Solaris 10 OS, use the kdmconfig program. Choose the option that applies to the type of X server your system is running.
If your system is running the Xsun server, follow these steps:
Run kdmconfig.
Use the Change Keyboard option to change the keyboard type.
Save the configuration.
If your system is running the default Xorg server, follow these steps:
Run kdmconfig.
Select the Xsun server.
Use the Change Keyboard option to change the keyboard type.
Save the configuration.
Run kdmconfig again to switch to the Xorg server.
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:
SG-PCI1FC-JF2
SG-PCI2FC-JF2
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:
Link reset
Loop reset
Switch reset
Repeated link failures
Error messages similar to the following examples might be displayed:
I/O failure messages
jfca: [ID 277337 kern.info] jfca4: Sequencer-detected error. Recover immediately. last message repeated 18376 times jfca: [ID 716917 kern.notice] jfca4: ExgWarning: SendVerify(1): SHOULD ABORT THE ORIG I/O PKG=30007520bd8! scsi: [ID 107833 kern.warning] WARNING: /pci@1e,600000/SUNW,jfca@3,1/fp@0,0/st@w2100001086108 628,1 (st3): SCSI transport failed: reason 'timeout': giving up
System panic message
panic[cpu1]/thread=2a100497cc0: BAD TRAP: type=31 rp=2a1004978d0 addr=a8 mmu_fsr=0 occurred in module "jfca" due to a NULL pointer dereference
Workaround: Do not connect tape devices to either the SG-PCI1FC-JF2 or SG-PCI2FC-JF2 HBA.
A bus contention occurs if Quad Fast-Ethernet (QFE) cards share the same bus with any of the following adapters:
Sun GigaSwift adapter
Sun Dual Gigabit Ethernet and Dual SCSI/P adapter
Sun Quad Gigaswift Ethernet adapter
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.
The default timeout value for the SCSI portion of the SunSwift 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 Oracle 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:
X1018A (SBus: F501-2739-xx)
X6540A (PCI: F375-0005-xx)