SPARC T3 and T4 Platforms may see Dropped or Double Character Input from USB Keyboards

Asset ID:	1-79-1390261.1
Update Date:	2012-09-26
Keywords:

Solution Type Predictive Self-Healing Sure

Solution 1390261.1 : SPARC T3 and T4 Platforms may see Dropped or Double Character Input from USB Keyboards

Applies to:

SPARC T4-2 - Version Not Applicable and later
SPARC T3-1 - Version Not Applicable and later
SPARC T4-4 - Version Not Applicable and later
SPARC T4-1 - Version Not Applicable and later
SPARC T3-4 - Version Not Applicable and later
Information in this document applies to any platform.

Purpose

Make Field and Customers aware that SPARC T3 and T4 Platforms (& related Netra Platforms) may see dropped or double characters while typing on the keyboard if appropriate patches aren't applied.

Details

PROBLEM DESCRIPTION

On Oracle's SPARC T3 and T4 servers, all USB ports/connectors available to users are connected to an internal USB 2.0 (ehci) controller through an onboard USB 2.0 hub.

When a full/low speed USB 1.0/1.1 keyboard and mouse are connected to a USB port through this USB 2.0 hub, keyboard input might drop characters or might display double characters.

NOTE: These errors occur when the ehci (USB 2.0) driver fails to detect keystrokes and mouse control input due to "Missed Micro-Frame" errors.

WORKAROUND

Currently, a workaround has been implemented for this issue where an internal USB hub is manually bound to the ohci (USB 1.0/1.1) driver. This binding causes a variable named ehci_forced_port_to_companion to instruct the ehci (USB 2.0) driver to transfer ownership of a specific port on the USB controller to the ohci (1.0/1.1) driver. Once the ohci driver is bound to a particular port on the USB controller, the ohci driver will be also be used by the internal USB hub connected to that port and all USB connectors on that hub.

This workaround is available in the following forms:

o Oracle Solaris 11 OS -- Oracle Solaris 11 Support Repository Update 3 (SRU3)
o Oracle Solaris 10 8/11 -- <SunPatch:147004-03>

For earlier supported versions of Oracle Solaris 10, apply the Solaris 10 8/11 SPARC Bundle, followed by patch <SunPatch:147004-03>.

NOTE: As a general practice, you should download and install all the latest available patches (for Oracle Solaris 10 OS) or latest SRU package (for Oracle Solaris 11 OS). To download Oracle Solaris patches and/or SRU packages, go to:

   http://support.oracle.com

SUPPLEMENTARY NOTES

On T3-1, T4-1, T3-2, and T4-2 (including Netras), the rear USB connectors as well as the virtual keyboard, virtual mouse, virtual CD-ROM, and virtual USB ethernet connection to the service processor (a.k.a RKVMS) are all beneath a hub connected to port 2 on the USB controller.

The front USB connectors are connected through a hub to port 4 of the USB controller.

Likewise, on the T3-4 and T4-4 platforms, the rear USB connector is beneath a hub that is connected to port 3 of the USB controller and the front USB connector and the virtual mouse, keyboard, CD-ROM and virtual USB ethernet connection to the service processor are beneath a hub that is connected to port 2 of the USB controller.

To use a physical keyboard and mouse with this workaround, apply the fix (either patch 147004-03 or SRU3) and then perform the following recommended steps:

o On SPARC T3-1, T4-1, T3-2, and T4-2 systems

1. Connect the input devices to a front USB connector.
2. Add the following line to /kernel/drv/ehci.conf:

      ehci-port-forced-to-companion = 4

3. Reboot.

o On SPARC T3-4 and T4-4 systems

1. Connect the input devices to a rear USB connector.
2. Add the following line to /kernel/drv/ehci.conf:

      ehci-port-forced-to-companion = 3

3. Reboot.

To use a physical keyboard and mouse with this workaround, first apply the fix (either <SunPatch:147004-03> for Oracle Solaris 10 or SRU3 for Oracle Solaris 11) and then add the following line to /kernel/drv/ehci.conf and reboot:

      ehci-port-forced-to-companion = 2

All other devices connected to the hub that services the virtual keyboard and mouse will be forced to operate at the lower USB 1.0/1.1 speed. These include:

o The virtual USB ethernet connection to the SP
o The physical USB connectors:

- Rear conectors on the T3-1, T4-1, T3-2, and T4-2
- Front connectors on the T3-4 and T4-4

NOTE: If you use the virtual keyboard and mouse with this workaround, some devices connected to the hub, such as a Virtual CD-ROM and Ethernet over a USB connection to the service processor, may not come up properly following a reboot.

When these devices do not come up, messages similar to the following will be displayed on the console and written to system logs:

WARNING: /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,1/hub@1/hub@3 (hubd4):
Connecting device on port 2 failed

WARNING: /pci@400/pci@2/pci@0/pci@f/pci@0/usb@0,1/hub@1/hub@3 (hubd4):
Connecting device on port 3 failed

CAUTION: At this time, there is no fix or workaround for the failure of these devices to come up when the missing micro-frame workaround is configured to support a virtual keyboard and mouse.

For this reason, you should limit use of following USB ports when using virtual keyboard and mouse functionality:

- Rear USB connectors on the T3-1, T4-1, T3-2, and T4-2
- Front USB connectors on the T3-4 and T4-4

All other virtual devices (such as virtual keyboard and virtual mouse) will continue to function, but will be limited to operating at the lower speed.

Attachments

This solution has no attachment