Hardware–Related Issue and Bugs

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

Japanese 106 keyboard Cannot Be Set Through kdmconfig (6463842)

If the Japanese 106 keyboard is attached to the system and the keyboard type Japanese-106/type7 is selected on kdmconfig, the U.S. layout will be applied to the system after reboot. No error message is displayed.

Workaround: Set the kbd-type by running the eeprom command:

# eeprom kbd-type='Japanese(106)'

Reboot the system.

SPARC: DR: cfgadm -c configure Command Fails on Slot of Starcat and Silverstone (6452077)

This bug affects all existing PCI platforms with hot-pluggable slots when the customer tries to hot-plug and configure a card making a 64-bit MEM request, for example, the Crystal 2R Fibre Channel card.

No error message is displayed. However, the configuration fails and the card is not usable.

Workaround: None. Reboot the system with the card inserted in the slot, and the card is configured and ready for operation.

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.

Workaround:

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 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.

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

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.

• If your system is running the Xsun server, follow these steps:

  1. Run kdmconfig.

  2. Use the Change Keyboard option to change the keyboard type.

  3. Save the configuration.

• If your system is running the default Xorg server, follow these steps:

  1. Run kdmconfig.

  2. Select the Xsun server.

  3. Use the Change Keyboard option to change the keyboard type.

  4. Save the configuration.

  5. Run kdmconfig again to switch to the Xorg server.

SPARC: Power Management in Sun Expert3D and Sun Elite3D Hardware Not Working Under Certain Circumstances (6321362)

Sun Expert3D or Sun Elite3D cards in Sun Blade 1000 or Sun Blade 2000 workstations normally switch to low-power mode after an idle period. However, if these cards are set as the primary head in the Xserver, power management does not work. The affected cards remain at full power and no power savings are realized. No error message is displayed.

Workaround: None.

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:

• 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.

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:

• 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.

hat_getkpfnum() DDI Function Is Obsolete (5046984)

The hat_getkpfnum() DDI function is obsolete. Developers should update their device drivers to not use the hat_getkpfnum() DDI interface. If drivers are using hat_getkpfnum,() warnings similar to the following example are displayed:

WARNING: Module mydrv is using the obsolete hat_getkpfnum(9F)
interface in a way that will not be supported in
a future release of Solaris. Please contact the
vendor that supplied the module for assistance,
or consult the Writing Device Drivers guide,
available from http://www.sun.com for migration
advice.
---
Callstack of bad caller:
       hat_getkpfnum_badcall+93
       hat_getkpfnum+6e
       mydrv_setup_tx_ring+2d
       mydrv_do_attach+84
       mydrv_attach+242
       devi_attach+6f
       attach_node+62
       i_ndi_config_node+82
       i_ddi_attachchild+4a
       devi_attach_node+4b
       devi_attach_children+57
       config_immediate_children+6e
       devi_config_common+77
       mt_config_thread+8b

To determine if a driver is using hat_getkpfnum(), consult the driver source code, or examine the driver's symbols by using nm(). Using the driver mydrv as an example, type the following syntax:

% nm /usr/kernel/drv/mydrv | grep hat_getkpfnum

For guidance about migrating drivers away from hat_getkpfnum(), refer to Appendix B, Summary of Solaris DDI/DKI Services, in Writing Device Drivers.

x86: Using Two Adaptec SCSI Card 39320D Cards on a Sun Fire V65x Server Might Cause the System to Panic (5001908)

Using two Adaptec SCSI Card 39320D cards on a Sun Fire V65x server might cause that system to panic. The panic occurs during initial reboot after you have installed Solaris 10 software. The following error message is displayed:

Initializing system  Please wait... 
1 run-time error M6111: MATH
    - floating-point error: stack underflow

Workaround: Remove the second Adaptec card.

x86: Soft System-Shutdown is Not Supported in Solaris OS on x86 (4873161, 5043369)

The Solaris OS on x86 does not support a soft system-shutdown that is initiated by a command. A command to shut down simulates pressing the power button to turn the power off. On x86-based systems, issuing this command while the Solaris OS is running turns the power off immediately without properly shutting down the operating system. The improper shutdown process might corrupt the file system.

Workaround: Before powering off, shut down the operating system first. Perform the following steps:

1. Become superuser.

2. Use one of the available commands to shut down the Solaris OS properly, such as init, halt, or shutdown. For example:

   # shutdown

3. After the operating system shuts down completely, you can switch off the power by one of two ways:

   • If the system supports soft system-shutdown, issue the command to turn off the power.

   • If the system does not support soft system-shutdown, turn off the power manually by using the power switch.

For more information about the commands to shut down the operating system, see the man pages for the init(1M), halt(1M), and shutdown(1M) commands. For information about turning off your system's power, refer to the system's manuals.

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

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 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)