2.5.1

3.0.16.17.a

2.0.3.10 (minimum) and

3.0.3.32*

07.07.01.03

2.5

3.0.16.17

2.0.3.10 (minimum) and

3.0.3.32*

07.07.01.03

2.4.3

3.0.9.19.g

2.0.3.10 (minimum) and

3.0.3.32*

07.07.01.01

2.4.2

3.0.9.19.f

2.0.3.10 (minimum) and

3.0.3.32*

07.06.02.33

2.4.1

3.0.9.19.d

2.0.3.10 (minimum) and

3.0.3.32*

07.06.02.30

2.4

3.0.9.19.b

2.0.3.10 (minimum) and 3.0.3.32*

07.06.02.30

2.3 (latest update for systems running ILOM 3.0)

3.0.9.19

2.0.3.10 (minimum) and 3.0.3.32*

07.06.02.23

2.1.1

3.0.6.21

2.0.3.10 (minimum) and 3.0.3.32*

07.06.02.15

2.1

3.0.6.10

2.0.3.10 (minimum supported) and 3.0.3.32*

07.06.02.15

2.0.1

3.0.3.35.a

2.0.3.10 (minimum supported) and 3.0.3.32*

07.05.01.01

2.0*

3.0.3.35

2.0.3.10 (minimum supported) and 3.0.3.32*

07.03.00.03

1.4 (latest update for systems running ILOM 2.0)

2.0.3.19

2.0.3.10*

07.04.40.02

1.2

2.0.3.14

2.0.3.10*

07.02.39.01

1.1

2.0.3.8 (r43734)

2.0.3.10*

07.02.39.00

1.0

2.0.3.8 (r42527)

2.0.3.10*

07.01.38.03

Intel CPU Microcode

SRV_C_81

Intel RC

1.05

Intel CPU Reference Code

1.02

Intel QuickPath Interconnect (QPI) Reference Code

1.05

Intel Memory Reference Code (MRC)

1.05

6806444

Sun ILOM Remote Console Might Hang on Windows Client When Redirecting a CD-ROM Image or Floppy Image

Issue:

When using a Windows client to redirect a CD-ROM image or floppy image from the Sun ILOM Remote Console, the Sun ILOM Remote Console might not respond.

Affected Operating Systems and Software:

• Windows Operating System installed on client system
• ILOM 2.0 or later and ILOM 3.0 or later
• Sun ILOM Remote Console
• JDK 1.6.0_07
• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Fix Available:

Fix is available on Supplemental Software Release 2.4.

15861266

Fault Reported for Non-Existent NEM

Issue:

In a powered-off Sun Blade 6000 Modular System, the amber Service Required LED for a network express module (NEM) reports an erroneous fault condition. When the Sun Blade 6000 Modular System that has a Sun Blade X6270 M2 or X6270 M3 server module (blade) installed is powered off, the amber Service Required LED might be illuminated for one of the NEMs (NEM0 or NEM1) even when there is no NEM installed in the chassis. In this case, ILOM reports a fault.fruid.corrupt message.

Affected Hardware and Software:

Sun Blade X6270 Server Module

Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Power on the chassis. After the chassis is powered on, the Service Required LED for the NEM is extinguished and the system recognizes that no NEM is present.

15648626 (formerly CR 6959652)

Dual 10-Gb Ethernet Fabric Expansion Model (FEM) X4871A-Z only works in FEM Slot 0 with the 10-Gb Ethernet Switched Network Express Module (NEM) X2073A

Issue:

If a reconfiguration or part replacement is required in a Sun Blade X6270 server module, the Dual 10-Gb Ethernet FEM X4871A-Z must be placed in FEM slot 0 with the 10-Gb Ethernet Switched NEM.

Affected Hardware and Software:

Sun Blade X6270 Server Module

Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Not applicable.

6937479

Use Default CMM and PSU FAN Settings

Issue:

The normal fan setting is default. OEM fan settings are developed for specific customers after testing their exact configuration and cooling requirement. If any other customer uses the OEM setting arbitrarily, this could cause a thermal event and void the warranty.

Affected Hardware and Software:

Sun Blade X6270 Server Module

Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Use the default fan setting. If a customer needs to use an OEM setting, they need to work with their Service/Account team to have these settings approved.

6890913

Active LED Does Not Illuminate When Solid State Disk (SSD) Is Idle

Issue:

Active LEDS do not illuminate when the blade powers on using the latest SSD and Controller firmware versions with onboard SATA controller, Adaptec RAID controller, and LSI RAID controller.

Affected Hardware and Software:

Sun Blade X6270 Server Module

Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Workaround is not yet available. This abnormal LED behavior does not impact the operation, performance, or functionality of the SSD.

6795890

USB Devices Not Shown in BIOS Boot Order When Using a CompactFlash Device

Issue:

In rare cases, when a CompactFlash device is connected using the CompactFlash connector, some USB devices might not be accessible in the BIOS boot-list.

Affected Hardware and Software:

• Sun Blade X6270 Server Module
• Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Reboot the system. If the problem persists after the reboot, initiate a service call.

7005619

Operating System Might Hang After Running Pc Check Diagnostics

Issue:

After running Pc Check, if you attempt to install or boot an operating system, the OS install or boot might hang.

Affected Software:

• Software releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Reboot the system after running Pc Check and before trying to install or boot an operating system.

6917623

“EHCI: BIOS handoff failed” Message Appears When Legacy USB is Enabled

Issue:

The following BIOS error appears in the log during boot: [ 118.727293] 0000:00:1d.7 EHCI: BIOS handoff failed (BIOS bug ?) 01010001...

Affected Operating Systems and Software:

• All supported operating systems
• Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Disable "Legacy USB" setting in BIOS and the error message will not appear. Or you can ignore the error message with no impact to the OS and applications.

6757722

LSI Utility Drive Enumeration Is Misleading

Issue:

Drive enumeration is misleading. Slot enumeration should be 0,1,2,3, or 1,2,3,4. LSI utility shows drives in slots 4 and 5, which are the top two drives (2 and 3).

Affected Operating Systems and Software:

• All supported operating systems
• Supplemental Software Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

There is no workaround. Check for the availability of a patch.

6779289

In-chip Connectivity Between the SP and the Host OS Is Not Supported When Using Sideband Network Port Sharing

Issue:

When configured for sideband (SB) network port sharing, in-chip connectivity between the service processor (SP) and the host OS is not supported by the on-board host Gigabit Ethernet controller.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3.1, 2.4

Workaround:

Use a different port or route to transmit traffic between the source and destination targets instead of using L2 bridging/switching.

6913602

ILOM Fails To Read DIMM FRU Information When Host is On

Issue:

When the host is on, FRU information for DIMMs is lost after Reset ILOM with factory option and ILOM reboot.

Affected Software:

• ILOM3.0.9.19.b r59793

Workaround:

Power off the Host before setting reset_to_defaults=factory, then reboot the SP.

6930223

Network Case Fails When Running SUNVTS7PS8

Issue:

When running SUNVTS7.0PS8, the network case will fail. The fix has not yet been backported to Solaris10.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Use the loopback connector for Virgo igb interfaces. The S10 patch 143355-03 is available on sunsolve.com.

6882835

6884652

Power Management Budget Is Not Supported on RHEL 4.7, 5.3, or 5.4

Issue:

Multiple issues occur if you try to use the Power Budget feature of Power Management on servers running Red Hat Enterprise Linux (RHEL) 4.7, 5.3, or 5.4. These issues can lead to configured power budgets being exceeded or lower than expected CPU performance.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.7, 5.3, 5.4
• ILOM 3.0.6
• Supplemental Release 2.1, 2.3, 2.4

Workaround:

Do not use the Power Budget feature when running Red Hat Enterprise Linux (RHEL) 4.7, 5.3, or 5.4.

6795975

Subsequent ILOM Session KVMS Interface Might Not Work

Issue:

When multiple ILOM Remote Console sessions are opened to the same service processor, the additional session's keyboard interface might not work. The first session's keyboard interface is not affected.

Affected Software:

• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

• Double-click in the ILOM Remote Console dialog to activate the mouse, then move the mouse.

Or

• In the ILOM Remote Console menu bar, select Devices --> Mouse, then move the mouse.

6800702

64-bit JRE Fails to Launch the Sun ILOM Remote Console

Issue:

An attempt to start Storage Redirection in ILOM might fail when using a 64-bit JRE. Since the 64-bit JRE is the default on a 64-bit system, you might also need to download a 32-bit JRE. When using a 64-bit JRE to start Storage Redirection, an "Unsupported platform" error appears.

Affected Software:

• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Install a 32-bit JRE on the 64-bit system. JREs can be downloaded at:

http://java.com/en/download/index.jsp

6840591

IPMI GUID Changes When Switching ILOM Management Between Sideband and Out-Of-Band

Issue:

When switching ILOM management between sideband and out-of-band, the IPMI GUID will change. This unexpected behavior might affect applications that use IPMI GUID for system management (for example, Sun xVM Ops Center) or for deployments that use SMBIOS UUID for server provisioning. Ensure that the ILOM configuration for sideband or out-of-band is complete prior to configuring third-party system management or server provisioning tools.

Affected Software:

• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

There is no workaround. Check for availability of a patch.

6779112

Misleading Status for Power Supplies Is Reported by VMware Health Status Screen

Issue:

The VMware Virtual Infrastructure client Health Status screen under the Power component reports the server power supplies in an Off-Line Disabled state and 0 watts, even though the power supplies are on-line and enabled.

Affected Operating Systems and Software:

• VMware ESX 3.5u4
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

To view the correct power status while in the VMware Virtual Infrastructure client Health Status screen, click on the Other component from the list of available options and view the blade n VPS (where n is the blade number).

6837645

Local Storage Drive Is Not Seen After Installing VMware ESXi 3.5 Update 4

Issue:

If the Sun Blade X6270 Server Module has a local storage drive attached to a Sun Blade RAID 0/1 RAID Expansion Module (X4607A-Z), the local storage drive is not seen by the system after installing VMware ESXi 3.5 Update 4.

Affected Operating Systems and Software:

• VMware ESXi 3.5u4
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

After completing the ESXi installation, follow these steps to add the local storage drive to the storage inventory:

1. Add the ESXi host to the data center of your choice using the Virtual Infrastructure Client.
2. Select the ESXi host added in Step 1, then click the Configuration tab.
3. In the hardware box (in the upper left of the display), select Storage.
4. In the upper right part of the display, click the Add Storage... link.
5. Ensure that the Disk/LUN Storage Type is selected, then click Next.
6. Highlight the vmhba entry that corresponds to the local storage drive and click Next.
7. Select the Use free space entry and click Next.
8. Create a Datastore Name (for example, local_storage), then click Next.
9. Adjust the Maximum file size, if needed, then click Next.
10. Verify the proposed disk layout, then click Finish.

The local VMFS datastore should now be available for use.

6930223

Network Case Fails When Running SUNVTS7PS8

Issue:

When running SUNVTS7.0PS8, the network case will fail. The fix has not yet been backported to Solaris10.

Affected Software:

• Supplemental Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Patch is not yet available.

6889350

Solaris FMA may fail to load and cause hang on system shutdown with particular memory configuration

Issue:

With mixed 4Gb and 8Gb dimms present in the same channel, Solaris FMA may fail to start correctly on system boot, and may cause the system to hang on shutdown.

Svcs will report that the fma daemon (fmd) is offline.

This issue has been seen with the following memory configuration:

8Gb dimms in D2,D5,D8 and 4Gb dimms in D1, D4, D7

Affected Operating Systems and Software:

• Solaris 10 10/08
• Solaris 10 5/09

Workaround:

For the above memory configuration, placing the dimms in the following order does not cause this issue

8Gb dimms in D1,D4,D7 and 4Gb dimms in D2, D5, D8

Arrange dimms to ensure that all dimms within a channel are the same capacity.

The Solaris 10 patch 1369140=-01 is available on http://sunsolve.sun.com.

6883310

On Systems Running the Solaris OS, Setting the Power Management Hardcap Power Limit Prior to Booting the System Does Not Control System Power

Issue:

If you set a power limit with timelimit=0 (none) prior to booting the system and the operating system (OS) is Solaris 10 05/09, the power limit is not adhered to by the system.

Affected Operating Systems and Software:

• Solaris 10 05/09
• Supplemental Software Release 2.1, 2.3, 2.4

Workaround:

After the OS is booted, do the following:

1. Disable the budget activation state.
2. Re-enable the budget activation state.

Note - Note - Note - This must be done each time after the OS is booted.

6731637

Boot Disk Size Limitation

Issue:

Solaris 10 05/09 will not install on a disk device that is greater than 1 TB in size.

Affected Hardware and Operating Systems:

• Sun Blade X6270
• Solaris 10 05/09

Workaround:

This issue will be resolved in the next release of Solaris. Install the OS on a boot device that is 1 TB or smaller.

6764573

KVMS Redirection Does Not Work When Intel VT-d Is Enabled in BIOS

Issue:

USB devices used for remote KVMS redirected keyboard and storage will not work with Intel VT-d enabled. An installation over redirected DVD might start, then hang after an IOMMU fault message is displayed on the console. The redirected USB keyboard will also hang. Other devices might be affected as well. When the failure occurs, IOMMU faults will display a message similar to:

WARNING: dmar0,0 generated a fault event when translating DMA read on address 0x0 for PCI(0, 26, 7), the reason is: The Read field in a page-table entry is Clear when DMA read

WARNING: /pci@0,0/pci1028,235@1a,7 (ehci0): Unrecoverable USB Hardware Error.

Affected Operating Systems and Software:

• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Perform one of the following procedures:

Disable VT-d in BIOS:
At system start-up, press F2 after POST to enter BIOS Setup.
Choose Advanced tab then disable the setting for VT-d.

Or

Disable intel-iommu in the Solaris GRUB menu:

Note - Note - Note - Help for editing the GRUB menu is available at the bottom of each screen.

1. During installation modify the GRUB menu by adding:
   -B intel-iommu=no
2. When the GRUB menu appears, type 'e' to edit then scroll to the appropriate boot entry.
3. Using the arrow keys, select the following line:
   kernel$ /platform/i86pc/kernel/$ISADIR/unix
   (continued on next page)

6764573 (continued)

Workaround (continued)

4. Press 'e' to edit the entry.

5. Append -Bintel-iommu=no to the line so that it looks like this:
kernel$ /platform/i86pc/kernel/$ISADIR/unix -Bintel-iommu=no

6. Press Enter then press 'b' to boot.
If you are adding this boot option to a list of existing options, note that the delimiter for boot options is a comma.
For example:
kernel$ /platform/i86pc/kernel/$ISADIR/unix -Bconsole=ttya,intel-iommu=no

7. After the installation completes, repeat the GRUB editing step outlined above prior to boot.

8. Boot, and edit /platform/i86pc/kernel/drv/rootnex.conf, adding the line:
intel-iommu=no

9. After installation, modify:
/platform/i86pc/kernel/drv/rootnex.conf: adding
intel-iommu=no

10.Rebuild the boot archive by typing:
bootadm update-archive

6767389

Hot-Insert for Certain ExpressModules Is Not Supported by Solaris

Issue:

When using Solaris 10 10/08, the following ExpressModules cannot be hot-inserted:

• Sun Fibre Channel - 4Gigabit/Sec PCIe Dual FC / Dual Gigabit Ethernet Host Adapter ExpressModule (EM) (SG-XPCIE2FCGBE-Q-Z)
• Fibre Channel - 4Gigabit/Sec PCI-X Dual FC Host Adapter (Emulex) (SG-XPCIE2FCGBE-E-Z)
• Sun Quad Gigabit Ethernet Module (X7284A-Z)

Affected Operating Systems and Software:

• Solaris 10 10/08
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Insert the affected modules and reboot in order for them to be recognized.

6783710

ExpressModule (X1028A-Z) Is Not Supported by Solaris

Issue:

The Solaris 10 10/08 and operating systems do not support the Sun x8 PCI Express Dual 10 Gigabit Ethernet ExpressModule (X1028A-Z and 1108A-Z).

Affected Operating Systems and Software:

• Solaris 10 10/08
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

For Solaris, support will be bundled into a future release. .

6836590

High-Speed USB 2.0 Devices Might Not Enumerate Properly

Issue:

In rare cases when booting the Solaris 10 10/08 Operating System, a USB initialization problem can occur that causes high-speed devices to go undetected by Solaris.

Affected Operating Systems and Software:

• Solaris 10 10/08
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Reboot Solaris. If USB enumeration issues persist across multiple consecutive reboots, then the problem is not due to this known issue.

7006903

Failure Message Appears After Booting SLES11 SP1 x64 and Oracle Linux 5.5 With Oracle Unbreakable Enterprise Kernel

Issue:

This issue exists on OSes with the 2.6.32 kernel or subsequent, such as SLES11SP1 64-bit and Oracle Linux 5.5 64-bit. When OS is loading iTCO_wdt watchdog driver, it reports the following error: "[ 63.009559] iTCO_wdt: failed to reset NO_REBOOT flag, reboot disabled by hardware". The watchdog timer feature in ICH10 is not supported on X6270 hardware, so the driver can’t initialize the device correctly.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 5.3
• SUSE Linux Enterprise Server 11 Service Pack 1
• Oracle Linux 5.5 with Oracle Unbreakable Enterprise Kernel
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Not available.

6817764

ILOM Power Budget Feature Does Not Work Unless RHEL 5.3 Errata CPUSPEED Package Is Used

Issue:

The speedstep-centrino cpufreq driver was built into the RHEL kernel, and the acpi-cpufreq driver was included as a module. The two cpufreq scaling drivers conflict due to Red Hat init scripts. This conflict causes the RHEL kernel to not honor CPU power capping directives from ILOM.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 5.3
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

The problem was corrected by Red Hat and a fix was released to the public. Users of Red Hat Enterprise Linux 5.3 should use the latest 5.3 errata cpuspeed package available for download. For more information, see the following document for download details:

http://rhn.redhat.com/errata/RHBA-2009-0424.html

6830785

SLES XEN Host (Dom 0) Using igb.ko Driver Will Drop XEN Guest
(Dom U) Packets When IPv4 TX Checksum Offload Is Enabled

Issue:

The XEN Host (Dom 0) will corrupt XEN Guest (Dom U) network traffic during transmission to and from the physical interface under the following conditions:

1. XEN Host (Dom 0) is SLES 10 SP2 operating system.
2. The inbox SLES 10 SP2 Intel igb.ko driver is being used on the XEN Host (Dom 0).
3. IPv4 TX checksum is enabled on the XEN Guests (Dom U).
4. XEN Guests (Dom U) are using optimized paravirtualized NIC drivers.

Affected Operating Systems and Software:

• SUSE Linux Enterprise Server 10 Service Pack 2 (SLES10 SP2)
• Supplemental Software Releases 1.0, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

A later version of the driver has been compiled for SLES 10 SP2 to resolve this issue. Upgrade to the latest driver version. This issue has been documented by Novell SLES support in the following Technical Information Document (TID), which is available at this location: http://www.novell.com/support/php/search.do?cmd=displayKC&docType=kc&externalId=7003448&sliceId=1&docTypeID=DT_TID_1_1&dialogID=39728435&stateId=0%200%2060594008

Please refer to the TID for information on the latest igb driver that fixes this issue.

6729577

PCIHP Hot-Plug Default Driver Is Not Supported by SLES10 SP2

Issue:

SLES10 SP2 has disabled interrupts on the PCI Express root ports. As a result, pciehp hot-plug does not function properly with default driver options. This can result in USB devices being inadvertently disabled when hot-plug actions are attempted.

Affected Operating Systems and Software:

• SUSE Linux Enterprise Server 10 SP2 (SLES10 SP2)
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

You must load the pciehp driver with the following parameter.

pciehp_poll_mode=1

For example:

modprobe pciehp pciehp_poll_mode=1

6763570

Preferred Method for Preventing RHEL 4.7 to Load Hot-Plug Driver

Issue:

On the Sun Blade X6270 Server Module, it is necessary for the administrator to choose a preferred method and to explicitly prevent Red Hat Enterprise Linux 4 from loading the hot-plug driver (acpiphp or pciehp).

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.7
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Blacklist the undesired module in /etc/modprobe.conf using the install command to direct the system to run /bin/true instead of inserting the incorrect hot-plug module if it is called by the kernel in response to a PCIe bus event.

For example:

1. Edit /etc/modprobe.conf

2. Add either of these lines:

install acpiphp /bin/true ;#blacklist acpiphp

or

install pciehp /bin/true ;#blacklist pciehp

For additional information, see Red Hat Release Note for the RHEL 4 product at:

http://www.redhat.com

6831175

Code for PCIe Hot-Plug Driver in RHEL 4.x Cannot Properly Handle Insertion of I/O Cards With Bridge Chips

Issue:

Because of outdated code, attempting to hot-insert the following I/O cards with bridge chips will likely result in a system hang:

• Sun StorageTek Dual 4 Gb FC Dual GbE HBA
  QLogic (SG-XPCIE2FCGBE-Q-Z)
• Sun StorageTek Dual 4 Gb FC Dual GbE HBA
  Emulex (SG-XPCIE2FCGBE-E-Z)
• Sun x4 PCIe Quad Gigabit Ethernet ExpressModule (X7284A-Z)

Affected Operating Systems and Software:

• RHEL 4.x
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.3, 2.4

Workaround:

Currently, there is no fix available. RHEL 4 is nearing the end of its support cycle, and it is possible that this issue might not be fixed. Users that need to hot- insert I/O cards with bridge chips should use the legacy acpiphp hot-plug driver under RHEL 4.x.

6766163

6766172

6771124

Legacy PCIe Hot-Plug Is Not Supported by SLES10 SP2

Issue:

SLES10 SP2 is not able to do legacy hot-plug on the Sun Blade X6270 Server Module. During boot up the kernel loads the PCIE_AER driver. This driver gains native (pciehp) control of PCIe hot-plug slots using the BIOS/ACPI _OSC method. After this occurs, the legacy (acpiphp) hot-plug driver should never be loaded.

Affected Operating Systems and Software:

• SUSE Linux Enterprise Server 10 Service Pack 2 (SLES10 SP2)
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

You must use the pciehp hot-plug driver with SLES10 SP2 on the Sun Blade X6270 Server Module.

The acpiphp hot-plug driver should not be used with SLES10 SP2 on the Sun Blade X6270 Server Module.

6771120

Benign Error Messages Are Seen When Using RHEL 5.3

Issue:

When using RHEL 5.3, benign error messages might be seen in the boot logs. These benign messages are related to the PCI device probe of the Aspeed video device.

Example of benign error messages:

• PCI: Ignore bogus resource 6 [0:0] of 0000:20:05.0

Or

• PCI: Ignore bogus resource 6 [0:0] of 0000:35:05.0

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 5.3
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

These error messages are benign and have no effect on the system stability or performance.

6800672

ixgbe (1.3.53) Driver Is Not Supported on RHEL 5.3

Issue:

The latest ixgbe (1.3.53) driver from Intel cannot compile on RHEL 5.3 for PCI Express Single (1106A-Z) or Dual (1180A-Z or 1107A-Z) 10-Gigabit Ethernet unless the setting for Large Receive Offload is disabled.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 5.3
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Compile with the earlier ixgbe driver (1.3.47).

6801897

RHEL 4.7 ipmi_si Driver Does Not Load With Default Parameters

Issue:

IPMI service fails to start. RHEL 4.7 ipmi_si driver does not load with default parameters.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.7
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

1. Edit /etc/modprobe.conf
2. Add the following line to change default ipmi_si driver parameters:

options ipmi_si type="kcs" ports=0xCA2 regspacings="4"

3. Save changes and exit.

4. Stop the service:

/etc/init.d/ipmi stop || service ipmi stop

5. Start the service:

/etc/init.d/ipmi start || service ipmi start

6803871

RHEL 5.3 Might Experience an Interrupt Storm Under Certain Conditions

Issue:

If the following HBA devices are simultaneously configured with the server, the Sun Blade X6270 Server Module running RHEL 5.3 can experience an interrupt storm when the kernel installs the Emulex driver.

• StorageTek PCI-E 4 Gb FC Host Bus Adapter PCI-Express EM (SG-PCIE2FC-QB4-Z)
• StorageTek PCI-E 4 Gb FC Host Bus Adapter with Emulex HBA SG-PCIE2FC-EB4-Z (SG-PCIE2FC-EB4-Z)

If this configuration exists, you could experience the following anomalies:

• USB device is disabled after 100K interrupts occur within 2 seconds.
• LUNs on the QLogic device will not register all of the LUNs.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 5.3
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

No patch is expected. Do not use SG-PCIE2FC-QB4-Z and SG-PCIE2FC-EB4-Z together with the Sun Blade X6270 Server Module when running RHEL 5.3.

6879304

Windows Server 2008 R2 Generates System Event Log Warning Messages When Power Is Being Limited by ILOM Power Management

Issue:

When power is being limited by the ILOM Power Management feature, the Windows Server 2008 R2 operating system will generate warning messages in the System Event Log informing the user that the processor(s) are being restricted. Example Event: The Speed of Processor xx in group x is being limited by system firmware. The processor has been in this reduced performance state for xxxx seconds since last report.

Affected Hardware, Operating Systems, and Software:

• All Sun servers with Power Management support
• Windows Server 2008 R2
• Supplemental Release 2.1, 2.3, 2.4

Workaround:

None needed. These are expected events and are not indicative of a problem.

6746934

After Hot-Plug Operation, Some PCI ExpressModules Might Display a Stop-Error Message or Might Not Appear in Device List

Issue:

A "0x00000124" Stop error message occurs when you use the hot-plugging feature to add or to remove a PCI Express device on a Windows Server 2008 based computer or on a Windows Vista-based computer.

Note - Note - Note - This issue can also be encountered during the software installation process.

Additionally, some PCI ExpressModules might not return to service properly after a hot-plug operation. The module might not appear in the device list or might appear with a yellow exclamation point next to the device description.

Affected Operating Systems and Software:

• Windows Server 2008 and Windows Vista
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Microsoft has an updated PCI bus driver for PCI Express that addresses a potential bug where the Max Payload Size might be configured incorrectly on the PCI Express root port if the root port is disabled and then re-enabled.

See the following knowledge base article, which includes a link to a hot-fix that can be downloaded when this problem is encountered:

http://support.microsoft.com/kb/952681

6756232

CompactFlash Card Might Not Be Detected by Windows Setup Utility

Issue:

The Windows Server 2003 Setup Utility copies the system boot files to the first disk found in the boot order. Windows detects the CompactFlash (CF) device as an ATA class device but, it is attached using the USB bus. The drives attached using USB are not supported by Microsoft for Windows Server as system boot devices.

Affected Operating Systems and Software:

• Windows Server 2008
• Windows Server 2008-R2
• Windows Server 2003
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround

The CF card must be lower in the Boot Device Priority List than the target disk. For more information, see the BIOS section in the Sun Blade X6270 Server Module Service Manual (820-6175).

6783026 6759267 6783538 6806081

Hot-Insertion or Removal of InfiniBand ExpressModule Is Only Allowed During Scheduled Downtime

Issue:

Attempting a hot-plug operation on an Sun Dual Port DDR IB Host Channel Adapter PCIe ExpressModule (X4216A-Z) will result in Uncorrectable Error on PCI Express bus.

Affected Operating Systems and Software:

• Windows Server 2008
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Do not attempt hot-insertion or removal of this device when running Windows Server 2008. If necessary, the InfiniBand ExpressModule should only be removed or added during scheduled downtime.

6783538

Blue Error Screen Might Appear When InfiniBand PCIe ExpressModule Is Disabled in Windows Device Manager

Issue:

If the option for the Sun Dual Port 4x QDR IB Host Channel Adapter PCIe ExpressModule (X4219A-Z) is disabled in Windows Device Manager, Windows Server 2008 stops and displays a Blue Screen with the following bug check 0x122 - General WHEA Error.

Affected Operating Systems and Software:

• Windows Server 2008
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

• Do not disable the option for the Sun Dual Port 4x QDR IB Host Channel Adapter PCIe ExpressModule in Windows Device Manager. If the module is disabled causing a Blue Screen to display, reboot the host system to recover. The Sun Dual Port 4x QDR IB Host Channel Adapter PCIe ExpressModule will be enabled upon reboot.
• Check for the availability of a patch for this defect.

6793369

Hot-Insert Is Not Supported by Windows 2008 for Some ExpressModules

Issue:

With Windows 2008 the following ExpressModules cannot be hot-inserted:

• Sun Fibre Channel - 4 Gigabit/Sec PCI-E Dual FC / Dual Gigabit Ethernet Host Adapter ExpressModule (EM) (SG-XPCIE2FCGBE-Q-Z)
• Fibre Channel - 4 Gigabit/Sec PCI-X Dual FC Host Adapter (Emulex) (SG-XPCIE2FCGBE-E-Z)
• Sun Quad Gigabit Ethernet Module (X7284A-Z)

Affected Operating Systems and Software:

• Windows Server 2008
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Insert the affected modules and reboot in order for them to be recognized.

6863766

Install Will Fail When Using a Diskette Made From the Tools and Drivers DVD or the Floppy Image (QLogic64.img) on the Tools and Drivers DVD to Install Windows Server 2003 64-bit to a Fiber Channel Array Over a QLogic Fiber Channel HBA

Issue:

If you use a diskette made from the Tools and Drivers DVD or the QLogic64.img floppy image available on the Tools and Drivers DVD to install Windows Server 2003 64-bit to a Fiber Channel Array over a QLogic Fiber Channel HBA, the installation will fail with a Blue Screen late in the setup process. The installation fails because the 64-bit QLogic Boot from SAN driver set available on the Tools and Drivers DVD has mismatched files. This results in a Bug Check 0x07B near the end of the installation process.

Affected Operating Systems and Software:

• Windows Server 2003 64-bit
• Supplemental Software Releases 1.0, 1.1, 1.2, 1.4, 2.0, 2.0.1, 2.1 2.3, 2.4

Workaround:

The corrected QLogic driver set, Boot from SAN for STOR Miniport 64-bit Driver (x64), for installing Windows 2003 64-bit to a QLogic connected fiber channel array (the drivers used when pressing F6 during install) is available for download at this web site:

http://driverdownloads.qlogic.com/QLogicDriverDownloads_UI/Sun_Details.aspx?productid=928&OSTYPE=Window&oemid=124

Check for the availability of a fix in updates to the Tools and Drivers DVD software.

6864864

SIA Will Cause Kudzu to Be Run for RHv4.7 x64 Installations With Emulex Cards

Issue:

When an installed system is booting for the first time SIA unintentionally causes Kudzu, a Red Hat hardware configuration utility, to be run for RHv4.7 x64 installations with Emulex cards.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.7 64-bit

Workaround:

Configure the Emulex cards through the Kudzu interface.

6862030

SIA Causes Default Keyboard Selection in SLES11 To Be UK-Style English

Issue:

SIA will cause the keyboard selection for SLES11 installation to default to UK-style English.

Affected Operating Systems and Software:

• SUSE Linux Enterprise Server SLES (SLES) 11
• Supplemental Software Release 2.1

Workaround:

The first screen that is displayed during the SLES 11 installation has a drop-down box for selecting the correct keyboard. Select the US-style keyboard.

6861956

SIA Is Unable to Install SLES Via Network File System (NFS)

Issue:

Problem installing SLES 10 SP2 or SLES 11 via a NFS-exported ISO image.

Affected Operating Systems and Software:

• SUSE Linux Enterprise Server SLES (SLES) 10 Service Pack 2 and SLES 11

Workaround:

Use direct attach ISO image, redirected ISO image, or expanded image via NFS, ftp, or http.

6851222

SIA Does Not Include Drivers for the Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module

Issue:

When SIA is used to install an operating system to the Sun Blade X6270 Server Module in a chassis which contains a Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module, drivers for this device are not installed.

Note - Note - Note - If you are installing Windows Server 2003, the "Found New Hardware Wizard" might run at the first login.

Affected Operating Systems and Software:

• Windows Server 2003 and 2008
• Red Hat Enterprise Linux (RHEL) 4.7, 5.1, 5.2, 5.3
• SUSE Linux Enterprise Server SLES (SLES) 10 SP2
• Supplemental Software Releases 1.0, 1.1, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Manually install the driver, which can be found by downloading the Sun Blade 6000 Virtualized Multi-Fabric 10GbE Network Express Module Tools and Drivers CD from http://www.sun.com/servers/blades/downloads.jsp

6798618

6800204

6806734

6813789

Blue Error Screen Might Appear When Option for Automatic SIA Updates Is Not Selected

Issue:

If you are using SIA to install Windows Server 2008 to the Sun Blade X6270 Server Module and you opted out of the automatic SIA update, then your installation might fail and a Blue Screen might appear with a bug check.

Affected Operating Systems and Software:

• Windows Server 2008
• Supplemental Software Releases 1.0, 1.1, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Perform one of the following workarounds for this issue:

• Restart the SIA installation and accept the option for automatic SIA updates.

Or

• Disable ACHI mode in the BIOS Setup Utility and restart installation. Follow these steps:
• In the Advanced menu of the BIOS Setup Utility, select On-board SATA Configuration and press Enter.
• Select the option for Configure SATA#1 and press Enter.
  A tab appears listing the available options.
• In the tab, select the option for IDE and press Enter.
• To save the changes and exit the BIOS Setup Utility, press F10.
• Install Windows 2008 directly from the installation media.

6805366

SIA Might Not Install AHCI Device Driver for Windows 2003

Issue:

If you are installing to an LSI device or Sun StorageTek Raid Host Bus Adapter, SIA might not automatically install the AHCI device driver for Windows 2003 installations. SIA will copy the AHCI device driver to disk (install target) but you might need to install the AHCI driver using Windows Device Manager.

Affected Operating Systems and Software:

• Windows Server 2003
• Supplemental Software Releases 1.0, 1.1, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

Any of the following is an acceptable workaround for this issue:

• Use Windows Device Manager to install the AHCI device driver that was copied to disk (install target). For instructions for using Device Manager to update or install device drivers, refer to the Windows Device Manager documentation.
• Restart the SIA installation and accept the option for automatic SIA updates.
• Download the latest SIA CD from:

http://www.sun.com/servers/blades/downloads.jsp

and restart the installation.

6835303

SIA Installation Does Not Work Correctly When Installing an ISO Image of the Red Hat Operating System Using NFS

Issue:

If you elect to install the Red Hat operating system from an ISO image that is exported using a network file system (NFS) server, profiles for the Red Hat installation will not be propagated to the installation. This will result in the following behavior:

• Anaconda will prompt the user for the installation type (desktop, client, server, or minimal).
• Individual packages will not be pre-selected based on the installation type, and the user will have to select these manually.

Affected Operating Systems and Software:

• Red Hat Enterprise Linux (RHEL) 4.x and 5.x
• Supplemental Software Releases 1.0, 1.4, 2.0, 2.0.1, 2.1, 2.3, 2.4

Workaround:

When using SIA to install the Red Hat operating system, do not use an ISO image exported using NFS.