JavaScript is required to for searching.
Skip Navigation Links
Exit Print View
SPARC T4-1 Server

Product Notes

search filter icon
search icon

Document Information

Using This Documentation

1.  Late Breaking Information

Preinstalled Software

Supported Versions of Oracle Solaris OS, Firmware, and Software

OS Package and Patch Updates

Determining Oracle Solaris 11 OS Package Update Version

Determining Oracle Solaris 10 Patch Revision

Minimum Required Patchset for Oracle Solaris 10 8/11 OS

Minimum Required Patchsets and SPARC Bundle for Oracle Solaris 10 9/10 OS

Minimum Required Patchsets and SPARC Bundle for Oracle Solaris 10 10/09 OS

Support for new 16 Gbyte and 32 Gbyte DIMMs

Rules for I/O Slot Use by Certain Cards

2.  Known Product Issues

Hardware Issues

Maximizing Memory Bandwidth

Direct I/O Support

Use Links Labeled SPARC T3 to Download sas2ircu Firmware and Documentation for SPARC T4 Servers

Sun Type 6 Keyboards Are Not Supported By SPARC T4 Series Servers

Caution Needed When Removing a SATA Data Cable From a Backplane Connector

Caution Needed When Handling the Connector Board

Server Panics When Booting From a USB Thumbdrive Attached to the Front USB Ports (Bug ID 15667682)

PSH Might Not Clear a Retired Cache Line on a Replaced Motherboard (Bug ID 15705327, Bug ID 15713018)

PCIe Correctable Errors Might Be Reported (Bug ID 15720000, Bug ID 15722832)

SPARC T3 and T4 Platforms Might See Dropped or Doubled Character Input From USB Keyboards (Bug ID 15700526, Bug ID 15728507)

Supplementary Notes

L2 Cache UEs Are Sometimes Reported as Core Faults Without Any Cache Line Retirements (Bug ID 15731176)

Upon a Reboot After an Unrecoverable Hardware Error, CPUs Might Not Start (Bug ID 15733431)

reset /SYS Operations Can Cause the SAS Controller to Disappear (Bug ID 15737475)

SAS Command Might Fail to Complete When Certain SAS Devices Are Put Under Heavy Load (Bug ID 15802084)

Rebooting an SDIO-SAS HBA Guest Domain Might Generate ereport.io.pciex.pl.re (Bug ID 15718101)

Characters Are Occasionally Dropped at the Oracle OpenBoot Prompt (Bug ID15813690)

Oracle Solaris OS Issues

When a Start Address Is Not Aligned With the Largest Page Size, the OS Should Use the Next Available Page Size (Bug ID 15718159)

Cannot Boot Oracle Solaris 10 10/09 OS (U8) From the Internal DVD

Spurious Interrupt Message in System Console (Bug ID 15651697, Bug ID 15771956, Bug ID 15771958)

Spurious Error Message During Initial Oracle Solaris 10 OS Installation (Bug ID 15658412)

When diag-switch? is Set to true, Oracle Solaris OS Fails to Update EEPROM for Automatic Rebooting (Bug ID 15666767)

Memory Allocation Issues With Emulex 8Gb HBAs In a Magma IO Expansion Box (Bug ID 15666779)

Fault Management Sometimes Sends Resolved Cases to the SP (Bug ID 15667874, Bug ID 15741999)

Gigabit Ethernet (nxge) Driver Not Loading on Systems With Oracle Solaris 10 10/09 OS and a Solaris 10 9/10 Patchset or Solaris 10 8/11 Patchset (Bug ID 15677751)

The trapstat -T Command Causes Bad Watchdog Resets at TL2 (Bug ID 15720390)

Watchdog Timeouts Seen With Heavy Workloads and Maximum Memory Configurations (Bug ID 15737671, Bug ID 15744469, Bug ID 15771943)

ereport.fm.fmd.module Generated During a Reboot of an SDIO Domain (Bug ID 15738845, Bug ID 15742069)

Benign Error Message: mptsas request inquiry page 0x83 for target:a, lun:0 failed! (Bug ID 15809005)

Oracle VTS dtlbtest hangs when the CPU Threading Mode is Set to max-ipc (Bug ID 15743740, Bug ID 15744945)

Some pciex8086,105f Devices Fail to Attach (Bug ID 15774699)

L2 Cache Uncorrectable Errors Causing a Reboot Abort (Bug ID 15826320)

Firmware Issues

Performing First-Time Boot On Servers Equipped With the Sun Storage 6 Gb SAS PCIe 8-Port Internal RAID HBA

Cold Reset Adds One Day to System Time (CR 15764743, Bug ID 15765255, Bug ID 15765770)

Timestamp for an Oracle ILOM Fault/Critical Event Might Be Off by One Hour (Bug ID 15802097)

Missing Interrupt Causes USB Hub Hotplug Thread to Hang, Resulting In Process Hangs (Bug ID 15655752)

Units Used to Define the MIB Power Management Time Limit Are Reported in Seconds (Bug ID 15675720)

Message From cpustat Refers to Processor Documentation Incorrectly (Bug ID 15717099, Bug ID 15717100, Bug ID 15749141)

reboot disk Command Occasionally Fails When disk Argument Picks Up Extra Characters (Bug ID 15816272)

Explicit Processor Binding Might Block Strand Retirement (Bug ID 15733312)

Blue OK-to-Remove LED On Drive Does Not Light When The Drive Is Ready To Remove (Bug ID 15737491)

In Some Instances, a PCIe Card Might Disappear From the Device Tree Upon Reboot or During Power-On (Bug ID 15849720)

System Firmware 8.2.0 Contains a New Version of the scvar Database (Bug ID 16184046)

System Firmware 8.3.0.b Incompatible with the Sun Flash Accelerator F40 PCIe Card (Bug ID 16813726)

Firmware Issues

This section describes issues related to the system firmware.

Performing First-Time Boot On Servers Equipped With the Sun Storage 6 Gb SAS PCIe 8-Port Internal RAID HBA

On servers ordered with the Sun Storage 6 Gb SAS PCIe 8-Port Internal RAID HBA card preinstalled, you must specify the full device path when performing first-time boot.

  1. Set the auto-boot parameter to false:

    sc> set /HOST/bootmode script="setenv auto-boot? false"
  2. Use the full device path when performing first-time boot:

    ok boot /pci@400/pci@2/pci@0/pci@c/LSI,mrsas@0/disk@0,0

Cold Reset Adds One Day to System Time (CR 15764743, Bug ID 15765255, Bug ID 15765770)


Note - This issue was originally listed as CR 7127740.



Note - This issue is fixed in System Firmware version 8.1.4.e.


After a cold reset, the server might add one day to the Oracle Solaris OS date and time. This possible date change will only occur on the first cold reset after the first day of a leap year (for example. January 1, 2012). Once you set the correct date using the Oracle Solaris OS date(1) command, the corrected date and time will persist across future resets.


Note - This extra day error condition will return if the clock offset stored in the SP is cleared for any reason. For example, the clock offset will be lost if the battery is replaced, Oracle ILOM is reset, or the system firmware is flashed without first saving and then restoring the configuration.


A cold reset is when you halt the OS and restart the service processor (SP). For example, you can use one of the following Oracle Solaris OS commands to halt the OS:

Then, at the Oracle ILOM prompt, use the following commands to reset the host:

Refer to the service manual, the administration guide, and the Oracle Solaris OS documentation for more information.

Workaround: After the first cold reset of the system, verify that system date and time are correct. If the date has been impacted by this issue, use the Oracle Solaris OS date(1) command to set the correct date and time.

For example, to set the date and time to be February 26, 9:00am, 2012, type:

Refer to the date (1) man page and the Oracle Solaris OS documentation for more information.

Timestamp for an Oracle ILOM Fault/Critical Event Might Be Off by One Hour (Bug ID 15802097)


Note - This issue was originally listed as CR 6943957.



Note - This issue is fixed in System Firmware 8.3.0.


The timestamp reported in an email generated in an Oracle ILOM Fault/critical event might be one hour later than the timestamp recorded in the event log.

Recovery Action: Check the timestamp recorded in the event log. If it does not match the timestamp reported in the email, use the event log time.

Missing Interrupt Causes USB Hub Hotplug Thread to Hang, Resulting In Process Hangs (Bug ID 15655752)


Note - This issue was originally listed as CR 6968801.


When running Oracle VTS on T4 series platforms, it is possible (although rare) for a Oracle VTS test to hang. If this happens, it might cause other processes and commands to hang, including fmadm and prtconf. The hung processes cannot be killed.

Workaround: Reboot the system. If the problem repeats, contact your authorized service provider. Avoid running Oracle VTS in production environments.

Units Used to Define the MIB Power Management Time Limit Are Reported in Seconds (Bug ID 15675720)


Note - This issue was originally listed as CR 6993008.


The MIB should report the sunHwCtrlPowerMgmtBudgetTimelimit in milliseconds, but the value displayed is in seconds.

Workaround: Understand that the value reported for sunHwCtrlPowerMgmtBudgetTimelimit is in seconds.

Message From cpustat Refers to Processor Documentation Incorrectly (Bug ID 15717099, Bug ID 15717100, Bug ID 15749141)


Note - This issue was originally listed as CR 7046898.



Note - This issue is fixed in Oracle Solaris 11.


A message displayed by the cpustat command says:

SPARC T4 Supplement to Oracle SPARC Architecture 2011
User's Manual" for descriptions of these events.
Documentation for Sun processors can be found at:
http://www.sun.com/processors/manuals

This document and web site listed in this message are not available.

reboot disk Command Occasionally Fails When disk Argument Picks Up Extra Characters (Bug ID 15816272)


Note - This issue was originally listed as CR 7050975.



Note - This issue is fixed in Oracle Solaris 10 01/13.


When running the reboot disk command, extraneous characters are occasionally added to the disk argument before it reaches the OpenBoot PROM (OBP). This results in a failure to boot.

Recovery Action: Repeat the boot request.

Explicit Processor Binding Might Block Strand Retirement (Bug ID 15733312)


Note - This issue was originally listed as CR 7071974.


The explicit assignment of specific process(es) to CPU strands, either by binding or by use of the High-IPC feature, might cause a situation in which the fault manager's attempt to retire a strand is rejected because the strand is marked as busy.

Workaround: Remove the explicit binding of any process to the CPU strand diagnosed as faulty.

Blue OK-to-Remove LED On Drive Does Not Light When The Drive Is Ready To Remove (Bug ID 15737491)


Note - This issue was originally listed as CR 7082700.


When you attempt to unconfigure a drive for removal, the drive's OK-to-Remove LED might not light. This happens after you place a drive in a slot in place of a drive that had a different WWID.

Workaround: If you inserted a drive after booting the server, realize that the OK‐to-‐Remove LED does not perform this function until the server has been rebooted.

In Some Instances, a PCIe Card Might Disappear From the Device Tree Upon Reboot or During Power-On (Bug ID 15849720)

In some cases, a PCIe card might disappear from the device tree upon reboot or during power-on. The PCIe card reappears in the device tree when the system is power cycled or reset.

Workaround: Do one of the following:


Note - If the PCIe card does not reappear even after a power cycle or system reset, the PCIe card might be faulty


System Firmware 8.2.0 Contains a New Version of the scvar Database (Bug ID 16184046)

A new version of the scvar database was introduced in system firmware 8.2.0. Upgrading the system firmware from a version prior to 8.2.0 to system firmware version 8.2.0 or later reverts the scvar database to default settings after the installation completes. This also erases any date/time offsets that have not been saved in an LDOMs spconfig file, making it necessary to re-set the date/time on affected domains.

System Firmware 8.3.0.b Incompatible with the Sun Flash Accelerator F40 PCIe Card (Bug ID 16813726)

Servers equipped with System Firmware 8.3.0.b might exhibit severe performance degradation due to thermal limiting of the Sun Flash Accelerator F40 PCIe Card.

Workaround: If your server is equipped with the Sun Flash Accelerator F40 PCIe Card, do not not upgrade to System Firmware 8.3.0.b. If you have already upgraded a server equipped with a Sun Flash Accelerator F40 PCIe Card to System Firmware 8.3.0.b and are encountering thermal-related performance degradation, downgrade to System Firmware 8.2.2.c.