7029837

Uncorrectable memory errors may result while the system is idle

Issue:

Uncorrectable memory errors are reported while the system is idle. They can appear to come from 1 DIMM, or multiple DIMM’s or multiple CPU’s at the same time.

Affected Operating Systems:

All Operating systems, this issue is at the BIOS level.

Workaround:

This problem is fixed in software release 1.1. Obtain the latest software release at: https://support.oracle.com

If you are unable to update to software release 1.1 at this time:

1. Clear any previous memory faults manually in ILOM.

For instructions see the "Oracle Integrated Lights Out Manager (ILOM) 3.0 Supplement for Sun Netra X6270 M2 Server Module" at:

http://www.oracle.com/pls/topic/lookup?ctx=E19472_01&id=homepage

1. Enter into BIOS Setup by selecting F2 during POST.
2. Select the "Advanced" tab.
3. Select the "CPU" menu.
4. Set the C-STATE tech feature to "Disabled".
5. Save the settings and exit the BIOS.

6928567

Unable to Launch ILOM Remote Console Using JRE 1.6.0 U14, U15, or U16

Issue:

If you try to launch the ILOM Remote Console through the web using some builds of Java Runtime Environment (JRE), the system returns the error Unable to Launch the Application.

Affected Operating Systems:

All operating systems running ILOM 3.0.9.xx, JRE 1.6.0, U14, U15, or U16.

Workaround:

Upgrade to JRE 1.6.0 U17 or later.

6923903

SP Restore Partially Successful and Reports an Error in the Log

Issue:

If the serial console is in use, properties related to the serial console cannot be restored and you will receive messages such as the following:

Config restore: Unable to restore property ’/SP/serial/host/commitpending’

Config restore: Unable to restore property ’/SP/serial/external’

Because such properties could not be restored, this is a partial failure and, therefore, results in the above message about the partial failure. This behavior is not a defect.

Affected Software:

Software Release 1.0.1

Workaround:

Log out of the serial console and try to run restore again.

6927196

Oracle Virtual Machine Manager 2.2 Install Fails on 6-Core CPU Configurations

Issue:

When installing Oracle VM Manager 2.2 on a Sun Netra X6270 M2 server module with 6-core CPUs, the install action might fail and exit with the message Database is not available.

Affected Hardware and Software:

• Oracle VM Manager 2.2
• Sun Netra X6270 M2 server module
• Software Release 1.0.1

Workaround:

To resolve this issue, see the patch and installation instructions at: http://oss.oracle.com/oraclevm/manager/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 online and enabled.

Affected Software:

VMware ESX 4.0 Update 1

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

6925850

The Solaris prtconf Command Does Not Report the Associated Physical Slot Number Along With the PCIe Device Slot Names

Issue:

When using the Solaris prtconf command to view system configuration information for some PCIe devices, the physical slot number is not reported along with the slot names.

For example, in the configuration information shown here, the first two slot names have associated physical slots, the other slot names do not:

% prtconf -pv | grep slot

slot-names: 00000001.65696370.00000034

physical-slot#: 00000004

slot-names: 00000001.65696370.00000031

physical-slot#: 00000001

slot-names: 00000001.746f6c53.00000035

slot-names: 00000001.746f6c53.00000032

slot-names: 00000001.746f6c53.00000036

slot-names: 00000001.746f6c53.00000033

Affected Operating System and Software:

• Oracle Solaris 10 10/09
• Software Release 1.0.1

Workaround:

There is no workaround.

6708175

Hot-Insert for Certain ExpressModules Is Not Supported by Oracle Solaris OS

Issue:

When using Oracle Solaris 10 10/09, the Sun Quad Gigabit Ethernet Module (X7284A-Z) ExpressModule cannot be hot-inserted:

Affected Operating System and Software:

• Oracle Solaris 10 10/09
• Software Release 1.0.1

Workaround:

Insert the ExpressModule. Reboot the blade server module so that the ExpressModules can be recognized.

6914173

pciehp Hot-Plug Default Driver Is Not Supported by SLES10 SP3

Issue:

SLES10 SP3 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 System and Software:

• SUSE Linux Enterprise Server 10 SP3 (SLES10 SP3)
• Software Release 1.0.1

Workaround:

You must load the pciehp driver with the following parameter:

pciehp_poll_mode=1

For example:

modprobe pciehp pciehp_poll_mode=1

6915768

During a Reboot of the System, You Might See a Kernel Panic

Issue:

During a warm reboot of the system, you might see an intermittent kernel panic __cpufreq_governor.

Affected Operating Systems and Software:

• Oracle Enterprise Linux (OEL) 5.4
• Red Hat Linux (RHEL) 5.4
• Software Release 1.0

Workaround:

A patch has been issued to fix this issue. You can download the patch at:

https://bugzilla.redhat.com/attachment.cgi?id=336296&action=diff

6914898

Hot-Plug Re-Insertion Fails With Code 35 in Windows Server 2008 SP2 and R2 64-bit

Issue:

With Windows Server 2008 SP2 and 2008 R2, certain ExpressModules are not currently supported for hot-insertion. The following ExpressModules cannot be hot-inserted:

• SG-XPCIEFCGBE-8Q-Z - Sun StorageTek Dual 8Gb FC Dual GbE HBA, QLogic
• X7284A-Z - Sun Quad GbE Express Module

Affected Operating Systems:

• Windows Server 2008 Service Pack 2, 64-bit
• Windows Server 2008 R2

Workaround:

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

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 processors 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
• Software Release 1.0.1

Workaround:

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