 |
≫ |
|
|
|
パッチ名: PHSS_36327
パッチ摘要: 11.31 rx5670 システム、BMCおよびiLO MPファームウェアパッチ
作成日: 07/03/30
公開日: 07/05/14
ハードウェアプラットフォームおよびOSリリース:
11.31
現象:
PHSS_36327:
- 拡張ラボテスト時に、IntelデュアルコアItanium IIプロセッサ(Montecito)
より前のItaniumプロセッサで、あるソフトウェアコードシーケンスの実行
中に異常な現象が起きました。Montecitoベースシステムのファームウェア
ではこの現象は起きません。PALファームウェアの実行時に起きた小サブセ
ットのCMC(Correctable Machine Check)イベントがSALファームウェアに渡
された可能性があります。ところが、SALファームウェアは、CMCイベントの
処理時に浮動小数点レジスタの以前の内容を保存していなかったため、レジ
スタ内容の破損により誤動作した可能性があります。この現象はラボ環境以
外では報告されていません。
当社は、今後とも、高品質の製品をお客様に提供するための努力を続けて参り
ます。その一環として、このファームウェアリリースでは、性能と信頼性を向
上させるためのいくつかの改善を行いました。
問題点の説明:
PHSS_36327:
- 上記の"現象"セクションを参照。
-----------------------------------------------------------------------------
Patch Name: PHSS_36327
Patch Description: 11.31 rx5670 System, BMC & iLO MP Firmware Patch
Creation Date: 07/03/30
Post Date: 07/05/14
Hardware Platforms - OS Releases:
11.31
Products: N/A
Filesets:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHSS_36327: CORRUPTION
- SAL firmware fails to preserve pre-existing
floating point registers in its handling of the
CMC event, potentially resulting in unexpected
operation due to a corrupted register state.
Category Tags:
defect_repair general_release critical firmware corruption
Path Name: /hp-ux_patches/11.X/PHSS_36327
Symptoms:
PHSS_36327:
- During extensive lab testing, HP discovered abnormal
behavior that may appear under certain software code
sequences on Itanium processors prior to the Intel
Dual Core Itanium II processor (Montecito). Firmware
for Montecito-based systems does not have this
exposure. The issue may occur with a small subset of
Correctable Machine Check (CMC) events when PAL
firmware is executed and eventually hands off to SAL
firmware. SAL firmware fails to preserve pre-existing
floating point registers in its handling of the CMC
event, potentially resulting in unexpected operation
due to a corrupted register state. This behavior has
not been reported outside the lab environment.
Hewlett-Packard continually strives to provide customers
with the highest quality of products. To meet this goal,
several minor performance and reliability improvements
have been identified that Hewlett-Packard has included in
this firmware release.
Defect Description:
PHSS_36327:
- See Symptoms.
Enhancement:
No
SR:
0000000000
Patch Files:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP:
/usr/conf/OSIFU/fwupdate.efi
/usr/conf/OSIFU/updatebootsequence
what(1) Output:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP:
/usr/conf/OSIFU/fwupdate.efi:
asctime.c 7.7
localtime.c 7.57
FWEUPDATE.EFI 0.80
Revision E.03.30 Oct 27 2006,13:43:15
/usr/conf/OSIFU/updatebootsequence:
None
cksum(1) Output:
OS-Core.KERN-RUN,fr=B.11.31,fa=HP-UX_B.11.31_IA/PA,v=HP:
1825691540 9900032 /usr/conf/OSIFU/fwupdate.efi
261107441 50136 /usr/conf/OSIFU/updatebootsequence
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
rx5670
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 4880 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_36327
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_36327.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_36327. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_36327.text file is
available in the product readme:
swlist -l product -a readme -d @ /tmp/PHSS_36327.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_36327.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
1. Prior to Installation:
Clear the system event logs.
1. Establish a telnet session with the iLO Management
Processor.
2. Logon to the iLO Management Processor using the
Admin password.
3. Type SL to enter the Show Logs menu.
4. At the "Enter menu item or [Ctrl-B] to Quit:" prompt,
type "c".
5. At the "Are you sure you want to clear all logs?
(Y/[N]):" prompt, type "y".
The following should be displayed:
-> Logs have been cleared.
2. Prior to updating the iLO MP firmware an MP reset needs
to occur via the "XD -R" command in order to free up enough
contiguous memory.
- Reset the iLO MP.
- Establish a telnet session with the iLO Management
Processor.
- Logon to the iLO Management Processor using the Admin
password.
- Type "XD -R" to restart the MP.
- Type "Y" to confirm.
3. This patch will only install and update the firmware on
rx5670 systems.
If you wish to install the patch on a different system even
though it does not apply, you can force the installation of
the patch by using the touch(1) command to create the file
'/tmp/force_patch_install' before installing the patch.
This may be useful when creating a 'golden' archive image
for Ignite-UX that may be used on several different
hardware platforms.
If the patch is installed on a system other than those
listed above, it will not modify the system firmware so no
harm will occur.
4. If this patch is uninstalled it will not uninstall/
downgrade the firmware installed by the patch and the
firmware installed by the patch will remain loaded after
the patch is removed. To install or downgrade to
an earlier firmware version see step #8 below.
5. The firmware update is accomplished by temporarily
altering the boot sequence. To identify the disk, the patch
assumes that the primary boot disk is the first disk listed
in the /stand/bootconf file.
To ensure the firmware update is successful, please use the
setboot(1M) and ioscan(1M) commands to verify that the
primary boot disk is set and is the first disk listed in the
/stand/bootconf file. If it is not, modify the bootconf
file appropriately. Please reference the man page for
bootconf(4) for information on this file.
6. If a firmware update is attempted from within an OS
install, update-UX, or Dynamic Root Disk session. it will
be excluded from installation to ensure that OS install,
update-UX, or DRD is fully functional. Attempting a
firmware update when installing or updating patch
bundles (e.g. from an Ignite-UX server using a 'golden'
archive image) will be successful.
7. The firmware update will be excluded from installation
if the firmware versions in the patch is the same or older
than the one the system is running on. This will ensure
that no unnecessary system reboot occurs. To downgrade
to an earlier firmware version see step #8 below.
8. Any newer firmware versions on the system can be
downgraded with firmware in this patch by forcing the
installation of the patch by using the touch(1) command
to create the file '/tmp/force_patch_install' before
installing the patch. If there are any newer firmware
patches installed on the system that supersede this
firmware patch, the newer firmware patches must be removed
with the SD command swremove in order to install this
downgrade firmware patch.
9. The firmware update will be excluded from installation
if the autoboot flag is not set. This is to ensure that the
end-to-end firmware update process goes smoothly without
user intervention once the patch installation is started.
Please use to setboot(1M) command to set the autoboot flag
on prior to installing the patch.
10. The firmware update will be excluded from installation
if the system has an Administrator password set.
If this password is set, it must be cleared by connecting
to the MP and running the BP command from the Command Menu
prior to installing the patch.
11. Do not attempt to update firmware on the MP via the
network while installing this patch.
12. Systems upgrading to HP-UX 11i v2 must first upgrade
system firmware to version 03.21 or later.
13. The MP firmware update will fail if the "Allow MP
Firmware upgrade via PCI" option is Disabled in the MP
Security Options menu. To update the firmware using this
package, enable this option in the MP Security Options
menu.
14. The BMC driver version 5.0 or Health driver version
7.0 or greater must be installed on the system to detect
the current firmware revisions. If the driver is not
installed, the existing firmware revisions are not
compared with the new firmware in the package.
15. CAUTION: Depending upon the currently installed MP
firmware, interim upgrades to previous revisions of
MP firmware may be required in order to upgrade to iLO
MP firmware revision E.03.30.
This system firmware update will be aborted if the
current MP firmware revision present on the system is
less than E.02.29. The firmware update and patch will
be excluded from installation if this requirement is
not met. In order to upgrade system firmware
using this package, first upgrade the MP firmware to
E.02.29. Please follow the upgrade requirements below:
1 - If the currently installed MP firmware is older
than E.02.10 then updating to MP firmware revision
E.02.26 requires updating to MP E.02.10 first.
2 - Upgrades to MP firmware revision E.02.29 will
require updating to MP firmware revision E.02.26
first.
3 - MP firmware must be at or upgraded to revision
E.02.29 prior to upgrading to iLO MP revision
E.03.30.
16. DETERMINING CURRENT VERSION:
The current version of firmware installed on the
system can be determined by executing the
swinstall(1M) command with the -p (preview)
command-line option:
swinstall -x autoreboot=true \
-x patch_match_target=true \
-p -s /tmp/PHSS_36327.depot
This will also verify various firmware installation
criteria. Or alternatively, the MP CM SYSREV command
can be used as shown below:
1 - Establish a telnet session with the iLO Management
Processor.
2 - Logon to the iLO Management Processor using the
Admin password.
3 - Type CM to enter the Command Menu.
4 - Type SYSREV to display system revision information.
The following should be displayed if the current
firmware is installed:
Current firmware revisions
MP FW : E.03.30
BMC FW : 01.30
EFI FW : 03.20
System FW : 03.33
5 - If the System firmware revision is less than 03.33,
if the BMC firmware revision is less than 01.30, or
if the iLO MP firmware revision is less than
E.03.30 then firmware should be updated.
|
