Firmware Issues

This section describes issues related to the system firmware.

Intermittent WARNING: ios#, peu# Link Width x8 Link Speed GEN1 Messages (CR 6958263)

When your server powers on to the OpenBoot PROM (OBP), you might see warning messages like the following in the system console:

WARNING: ios0, peu0 Link Width x8 Link Speed GEN1.

Workaround:

You can safely ignore these messages.

sas2flash Utility Fails When Six or More Sun Storage 6 Gb SAS RAID PCIe HBAs, External, Are Installed (CR 6983246)

The LSI Corporation sas2flash utility fails when there are six or more Sun Storage 6 Gb SAS RAID PCIe HBAs, External, installed in the system. For example, when attempting to list the HBAs using the sas2flash -listall command, you might see the following error message:

6   SAS2008(??)         ERROR: Failed to Upload Image!
-----------  ---------- ERROR: Failed to Upload Image!

Workaround:

Install five or less Sun Storage 6 Gb SAS RAID PCIe HBAs, External, in the system.

Adding a PCIe End-Point Device to a Guest Domain Might Result in a Hypervisor Abort and Shutdown (CR 6999227)

Your Oracle VM Server for SPARC 2.0 system might encounter one of the following problems if you reboot the root domain after adding a PCIe end-point device to a guest domain:

• Experience a hypervisor abort and shut down

• Fail to return to the OpenBoot PROM

• Fail to return to the Oracle Solaris OS

These problems only occur if you did not start the guest domain after adding the PCIe device. By not starting the guest domain, previously configured virtual interfaces might not have been properly cleaned up.

Workaround:

If these problems occur, restart the system. To avoid these problems, start a guest domain after adding an I/O resource to it. If you do not want the domain to be active at this time, stop the guest domain after it has been started.

Cold Reset Adds One Day to System Time (CR 7127740)

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

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:

# shutdown -g0 -i0 -y

# uadmin 1 6

# init 5

# poweroff

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

-> stop /SYS
. . .
-> start /SYS

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 the 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:

# date 022609002012

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

Performing stop /SYS with HOST_COOLDOWN Policy Enabled Generates a Critical Voltage Fault

By default, the HOST_COOLDOWN policy is disabled in the SP policy list, as shown by the following ILOM command:

-> ls /SP/policy
/SP/policy
Targets:
Properties:
HOST_AUTO_POWER_ON = disabled
HOST_COOLDOWN = disabled
HOST_LAST_POWER_STATE = disabled
HOST_POWER_ON_DELAY = disabled
PARALLEL_BOOT = enabled
 
Commands:
cd
set
show
 
 

If you change this value to enabled, you will encounter a fault.chassis.voltage.fail fault when you power off your system. This fault prevents you from powering your system on again until it is cleared.

This fault is in the event list in the ILOM command-line interface. For example:

-> show /SP/logs/event/list
24756  Wed Nov 24 11:23:36 2010  Fault     Fault     critical
Fault detected at time = Wed Nov 24 11:23:36 2010. The suspect component:
/SYS/MB has fault.chassis.voltage.fail with probability=100. Refer to http://www.sun.com/msg/SPT-8000-DH for details.
24755  Wed Nov 24 11:23:36 2010  System    Log       minor
Host: Solaris powering down
24754  Wed Nov 24 11:23:24 2010  System    Log       minor
Host: Host stopped
 
 
 

Workaround:

1. Disable the HOST_COOLDOWN policy:

   -> set /SP/policy HOST_COOLDOWN=disabled
   Set 'HOST_COOLDOWN' to 'disabled'

2. Clear the fault:

   -> set /SYS/MB clear_fault_action=true
   Are you sure you want to clear /SYS/MB (y/n)? ySet 'clear_fault_action' to 'true'

3. Restart the system:

   -> start /SYS