Hardware–Related Issue and Bugs

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

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

Using USB 2.0 Hubs With USB 1.x Devices Might Cause System Panic (6209619)

If you use USB 1.x devices downstream from a USB 2.0 hub, the system might panic. The following might be one of the error messages that is displayed:

BAD TRAP: type=31 rp=2a100f8d6a0 addr=38 mmu_fsr=0 occurred 
in module "usba" due to a NULL pointer

Workaround: Do not use any of the following connection configurations with USB 1.x devices:

• USB 1.x devices with a connection to a USB 2.0 hub that is connected to a USB 2.0 system port

• USB 1.x devices that are connected to a USB 2.0 PCI card's ports

Instead, connect the USB 1.x devices directly to the system's USB 1.1 ports. Alternatively, you can use a USB 1.1 external hub that is connected to a USB 2.0 system port or a PCI card's port.

x86: EHCI Driver Unusable in Certain Motherboards (6204987)

The system software in the ICH5R controller in certain motherboards fails to take control of EHCI hardware from the BIOS. The following error message is displayed:

ehci_init_ctrl: Unable to take control from BIOS. EHCI support disabled.

Consequently, you cannot use the EHCI driver.

Workaround: None.

Using FireWire–1394 Storage Devices Might Cause System Panic (6203680)

If you use FireWire-1394 mass storage devices with the removable media volume daemon (vold), the system might panic. Hard drives and CD or DVD drives are examples of such storage devices. The error message that might be displayed includes the entry “bad mutex.”

Workaround: Perform these steps before connecting FireWire–1394 mass storage devices to the system:

1. Become superuser.

2. Stop the Volume Management daemon to disable removable media management:

   # /etc/init.d/volmgt stop

For more information about the daemon, see the vold(1M) man page.

Pausing USB Audio Devices During Play or Record Operation Might Cause System Deadlock (6200924)

While a USB audio device is playing or recording, if you pause the device by using sdtaudiocontrol, for example, the driver might hang. You might need to reboot the system.

Workaround: Do not pause USB audio devices.

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.

Some Keyboard Keys Not Functioning With Num Lock Key On (6173972)

If the Num Lock key is turned on while you are running certain Java applications, other keys might cease to function. Some of the affected keys are the following:

• Back Space

• Delete

• Enter

• Tab

• Zero on the number keypad

Workaround: Turn off the Num Lock key.

SPARC: GigaSwift Fast and Gigabit Ethernet Devices With Revision IDs Lower Than 32 Might Cause System Panic (5090222)

A GigaSwift Fast or a Gigabit Ethernet card with a Revision ID (rev_id) that is lower than 32 might cause a system to panic. The panic is observed in the following systems that are running Solaris 10 OS:

• Sun Blade 1500

• Sun Blade 2500

• Sun Fire V210

• Sun Fire V240

• Netra 240

• Sun Fire V440

• Netra 440

The following error message is displayed:

panic: pcisch-1: Fatal PCI bus error(s)

Workaround: Follow these steps.

1. Determine the rev_id of the device.

   kstat ce:instance | grep rev

2. If the rev_id is lower than 32, replace the card with a later model that has a rev_id equal to or higher than 32.

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.

Some Systems With USB 2.0 Hardware Might Hang or Panic (5030842)

Systems with certain USB 2.0 hardware might frequently hang or panic when running this Solaris release. These problems are associated with USB 2.0 devices that are not based on the NEC chip set. When these problems occur, the following error message about the Enhanced Host Controller Interface (EHCI) is displayed:

WARNING: /pci@0,0/pci8086,244e@1e/pci925,1234@2,2 (ehci1):
This controller is not supported.
Please refer to www.sun.com/io for Solaris Ready products
and to www.sun.com/bidadmin/hcl for additional compatible USB products

Workaround: Depending on your system's hardware configuration, choose one of the following options:

• Replace the USB 2.0 host controller hardware with hardware that is based on the NEC chip set. USB 2.0 hardware that is based on the NEC chip set is known to work well with the Solaris OS.

• On systems whose USB 2.0 host controller hardware is built into the motherboard and that have spare PCI slots, perform the following steps:

  1. Add a PCI-based USB 2.0 card that is based on the NEC chip.

  2. Become superuser.

  3. Disable USB 2.0 on the motherboard and enable USB 2.0 support only through the PCI card. Issue the following commands:

     # update_drv -d -i '"pciclass,0c0320"' usba10_ehci
     # update_drv -a -i '"pci1033,e0"' usba10_ehci
     # reboot

  4. For faster operation, connect your USB 2.0 devices to the card's ports instead of the original ports on the motherboard.

• Even if you cannot add new USB hardware to your system, you can still disable your system's EHCI by performing the following steps:

  1. Become superuser.

  2. Issue the following commands:

     # update_drv -d -i '"pciclass,0c0320"' usba10_ehci
     # reboot

pci, instance #0 (driver name: pci_pci)
usb, instance #0 (driver name: usba10_ohci)
usb, instance #1 (driver name: usba10_ohci)
usb, instance #0 (driver name: usba10_ehci)

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)