Skip Navigation Links | |
Exit Print View | |
Oracle Solaris 10 8/11 Release Notes Oracle Solaris 10 8/11 Information Library |
3. Oracle Solaris Runtime Issues
The rstchown Parameter is Obsolete
Recommended Adoption of SHA-256 and SHA-512 crypt Plug-ins for Password Encryption
Trusted Stripe Disappears From the Screen After a Resolution Change (6460624)
ZFS Dynamic LUN Expansion Restriction (6241086)
The config/local_only Property in sendmail Must Not Be Set to true (6970172)
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)
BrightStor ARCserve Backup Client Agent for UNIX (Solaris) and ZFS Support Issue
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
SPARC: System Might Hang if the Elastic Policy is Set (6989192)
System Panic Might Occur During DR operations for Crypto (7048323)
SPARC: Disk Warning Is Displayed When Booting the Oracle Solaris OS (7047435)
SPARC: Dynamic Reconfiguration Operations Fail on an OPL Platform (7060498)
x86: System Shuts Down If ata Disks or Controllers Are Replaced on a Running Machine (7059880)
SPARC: System Panic Might Occur When Executing Bulk Crypto Operations on sun4v T3 Machines (7041435)
Message Signaled Interrupt (MSI-X) Cannot Be Retargeted When the apix Module Is Loaded (7058060)
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-ROM and CD-ROM Drives Fail to Boot the Oracle Solaris 10 OS (4397457)
SPARC: Copy Relocation Does Not Work (7083331)
Swedish Software Translations Note
Multiple Input Method Switcher Applications Appear in Trusted Java Desktop System
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)
x86: 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)
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
BIND 9.6 Denies Recursion To Non-Local Networks (7046009)
Configuring Tunnels With the Same Source Address (4152864)
System Domain of Interpretation Is Not Configurable (6314248)
IP Forwarding Disabled by Default in the Oracle Solaris 10 OS
Oracle Solaris Commands and Standards
SPARC: Incorrect Results Are Displayed for the cpustat Command on a T4 1.2 Chip
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
Email and Calendar Application
Problem With Changing Authentication Type (6246543)
Wrong Help Window Opened For Volume Control (6253210)
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)
Package Database Contains Path Names That Do Not Exist (7054481)
SPARC: 64-bit Version of the libsoftcrypto Library Is Slow (7048794)
patchrm Command Is Not Supported After Applying Patch 144500/144501 (7033240)
lucreate Introduces Latency on Slower UFS Systems (7051757)
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
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 8/11 Release
The following hardware-related issues and bugs apply to this Oracle Solaris 10 release.
sun4v systems running the Oracle Solaris 10 8/11 operating system that have the power management (PM) elastic policy set on the ILOM service processor might hang when you log in or execute commands.
Workaround: Do not set the PM elastic policy on a system that is running the Oracle Solaris 10 8/11 operating system. Instead, use the PM performance policy.
When performing dynamic reconfiguration (DR) operations for crypto on T2 platforms, the system might shut down because of a system panic.
You might see error messages similar to the ones shown in the following example:
panic[cpu0]/thread=30159724a00: mutex_destroy: bad mutex, lp=300bde6a190 owner=301eb4cc100 thread=30159724a00 000002a106c675f0 n2cp:n2cp_cwq_q_unconfigure+c4 (300bdd6d000, 300bde6a030, 1000, 300bde6a190, 1122f40, 0) %l0-3: 000000000180c000 0000000000000000 00000000018baf10 00000000018bac00 %l4-7: 0000000000000000 0000000000000000 0000000000000000 000000007bb88c00 000002a106c676a0 n2cp:n2cp_offline_cpu+150 (300bde6a018, 2000, 300bdd6d000, 0, 0
Workaround: Unload the n2cp driver.
When a hard disk drive is hot-plugged and you boot the Oracle Solaris OS, the following warning message is displayed:
'genunix: WARNING: preconfig failed: disk' when configure hard disk drive for removal
Ignore this warning message.
Dynamic reconfiguration (DR) operations might fail on an OPL platform when a memory board is being removed from a domain.
You might see error messages similar to the ones shown in the following example:
unconfigure SB3: Device busy: dr@0:SB3::pci6 XSB#01-3 could not be unconfigured from DomainID 2 due to operating system error.
Workaround: Execute the DR operations after disabling the fmd service. For example:
Disable the fmd service.
# svcadm disable fmd
Perform the DR operations.
Enable the fmd service.
# svcadm enable fmd
Hot-plug is not supported for ata devices. A system panic occurs and the system shuts down if ata disks or controllers are removed or replaced on a running machine. Also, do not use the modunload command to unload the ata driver.
When executing bulk crypto operations, a system panic message is displayed in the common/os/cpu.c file on sun4v T3 machines and the system shuts down.
You might see error messages similar to the ones shown in the following example:
panic[cpu57]/thread=3015d0a2580: assertion failed: t->t_affinitycnt > 0, file: ../../common/os/cpu.c, line: 461 000002a1007d4830 genunix:assfail+78 (1122cb8, 1122c00, 0, 135e400, 1cd, 1981800) %l0-3: 000003006157e000 0000000000STEP DETECTED PANIC
Workaround: Disable ulcwq by adding the following line in the /platform/sun4v/kernel/drv/n2cp.conf file:
n2cp-use-ulcwq=0;
After modifying the n2cp.conf file, reboot the system or run the update_drv n2cp command.
MSI-X cannot be retargeted when the apix module is loaded. When you use the dladm set-linkprop command to specify CPUs for a NIC, the dladm show-linkprop command does not reflect the updated CPU information for the NIC.
Workaround: Use the pcitool command.pcitool path-of-root-complex -i interrupt -w targeted-CPU
For example:
# pcitool /pci@400 -i b -w 8
The following output is displayed:
# 0x7,0xb -> 0x8,0xb
For information about the pcitool command, refer to the pcitool(1M) man page.
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 cause the kmdb command to fail.
For further information, refer to the README file that accompanies the XCP1093 firmware at the download site.
Upgrading the ConnectX firmware to version 2.6.0 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, and NEMs, and SPARC platforms are not affected.
You might be unable to boot the system or the system might hang during boot. ibd (IPoverIB) instance numbers might change and prevent the system from booting and plumbing ibd devices.
Choose one of the following workarounds.
Workaround 1: Before rebooting the system after updating the firmware using cxflash, remove the ibdx instances from the /etc/path_to_inst file and the /dev directory. Perform the following steps:
Log in as the root user and list the relevant devices.
The device tree information might look like the following example:
# 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.
Make a backup copy of the existing path_to_inst file.
# cp /etc/path_to_inst /etc/path_to_inst.backup
In the path_to_inst file, search for lines that contain ibd and hermon, and delete those lines. Save 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 the /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.
Once the system is back on, follow steps 2 and 3 in Workaround 1.
Power off the system.
Reinstall the HCA.
Reboot the system.
If the system reboots but the ibd interfaces do not automatically plumb, you might have to manually rename the /etc/hostname.ib<?> files to reflect the current device 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 Sun Fire 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: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 file 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 frame buffers stop power management. This failure reduces 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
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.oracle.com/technetwork/server-storage/solaris/overview/usb-faq-140616.html.
This Oracle Solaris 10 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 3-1 USB Devices and Configurations
|
This release of Oracle Solaris 10 for x86 platforms has the following limitations related to certain drivers and interfaces:
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.
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 drive remain in 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 drive, use the volcheck command 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 remain in full power mode.
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, the installation will use the default keyboard specification, which is inconsistent with the system's actual keyboard type.
Choose one of the following workarounds.
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 screen is displayed, press Esc.
Note - The information on the Proposed Window System Configuration For Installation screen, 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: To change the keyboard type on a system that is already running the 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.
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 preceding 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 the Sun 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)