Patch Name: PHSS_29649 Patch Description: s700_800 11.X rx5670 System Firmware Rev 03.23 Patch Creation Date: 04/02/27 Post Date: 04/03/23 Hardware Platforms - OS Releases: s700: 11.22 11.23 s800: 11.22 11.23 Products: N/A Filesets: OS-Core.KERN-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA/PA,v=HP OS-Core.KERN-RUN,fr=B.11.23,fa=HP-UX_B.11.23_IA/PA,v=HP Automatic Reboot?: Yes Status: General Release Critical: Yes PHSS_29649: PANIC HANG - SAL now returns the exact FSB frequency instead of a rounded one to fix problem with the system losing wall time every day. - Fixed issue where system could lock up if a user put slower CPU's in the system than were installed before. Category Tags: defect_repair hardware_enablement general_release critical firmware panic halts_system Path Name: /hp-ux_patches/s700_800/11.X/PHSS_29649 Symptoms: PHSS_29649: The following features appear in system firmware revision 03.23: New features: - None The following features appear in system firmware revision 03.21: New features: - McKinley PAL_B updated to version 7.59 - Upgraded the USB OHCI EFI Driver to version 29 - Upgraded the USB Mass Storage Driver to version 11 - Added a new event during Late memory self test to indicate single bit errors The following features appear in system firmware revision 03.11: New features: - PAL_B updated to version 5.37 - Memory Scrubbing implemented in SFW - FPSWA updated to 1.18 - EFI International Keyboard Support. - Version 0.29 OHCI USB Driver (This is required for International Keyboard Support) - Version 1.02.00 U160 SCSI driver - Margin Features Switch via NVM Token - Added new TUI which consists of following: * New System Configuration menu added to the Boot Manager menu. This menu allows the user to view information available from the "info" command, to set the date and time, and to reset the configuration to default values. * Moved Security/Password menu to the System Configuration menu. * Cold Reset option in Boot Maintenance menu now prompts user for confirmation. - Enhanced USB EFI driver features: * Support for the USB floppy drive * Support for multiple USB keyboards * Support for some USB storage devices (e.g. CD-ROM, DVD-ROM, flash memory, hard disk); note, some devices do not work * Support for some USB mice - EFI now creates a "Internal Bootable DVD" boot option for the internal CD/DVD drive whenever none of the Boot Manager variables exist. This condition typically only occurs when EFI NVM is invalid - The dh command now displays the device and vendor strings for any handle with an attached UI protocol. Currently only the EFI shell and the internal CD/DVD drive handles have the UI protocol attached - The dh command can now search for handles which have the UI protocol attached using: "dh -p ui" - From Intel's 01.10 [14.61] EFI drop: * Added generalized page break mechanism with the "-b" option for select commands. At each screen full of text, user is prompted to continue or quit display * Following commands modified to use new mechanism: alias, attrib, dmpstore, ls, memmap, map, set, type * Following commands no longer default to using page break and do not support the "-b" option (F1627) dblk, dmem * dmpstore no longer defaults to using page break. Use "dmpstore -b" to view data with page breaks - The dmpstore command now supports the syntax "dmpstore [-b] [variable]", where variable is the name of a specific variable for which to display data The following features appear in system firmware revision 02.21: New features: - None The following features appear in system firmware revision 02.11: New features: - None ----------------------------------------------------------- The following fixes appear in System firmware revision 03.23: Fixed issues: - SAL now returns the exact FSB frequency instead of a rounded one to fix problem with the system losing wall time every day. - Fixed issue where system could lock up if a user put slower CPU's in the system than were installed before. - Firmware now assumes all PCI-X cards are 66MHz capable - Serialized late selftest. - System could fail to recover if a CPU was deconfigured by firmware during the boot process. - Increased wait time from 10ms to 25ms for PCI slot power on. The following fixes appear in System firmware revision 03.21: Fixed issues: - Corrected compatibility issues with EFI EBC drivers - Corrected issues RDFM/WRFM ACPI issue with HPUX. This could cause issues with HPUX 11.23 and later - I/O changed to report system as non-hotpluggable to the OS to ensure compatibility with the RDFM/WRFM ACPI. - EFI "Baud" command was locked-out on the MP UART in previous version of firmware. The "Baud" command is now supported with MP firmware revisions E.02.23 and later. - Function ID for PCI UART in previous revision could be reported incorrectly in the HCDP table. - The EFI console splitter did not initialize its attributes value in previous versions of firmware. The original attribute for the console splitter standard output in previous revisions was 0, which is black foreground on black background. During boot the EFI console could become temporarily unreadable displaying black text on a black background in previous revisions of firmware. - SAL Speculation Fault Handler did not update IIPA correctly in previous revisions of firmware. - In previous revisions of firmware after PCI MCA errors occasionally the OS_MCA handler is unable to access PCI configuration space. The firmware handoff state to OS_MCA did not always re-enable PCI configuration space transactions. This caused HP-UX to be unable to reinitialize the console resulting in the system being hung. - Previous revisions firmware produced misleading error messages when an incorrect admin or user password is entered ("Error verifying password. Status= Unsupported" and "Unable to verify privilege. SAL or BMC failure."). Revision 03.21 produces an "access denied" error. - Corrected errors in the EFI Help text. - Previous revisions of the EFI boot manager did not allow text highlighting with HP-UX's xterm. EFI now uses the reversed text attribute to allow text highlighting to work on HP-UX's xterm. - Previous revisions of EFI sent an "ESC[3h" to the serial or lan console device during initialization or when a 'reconnect -r' command was issued. The "ESC[3h" causes VT100 terminal emulators to act according to the VT100 specification and change display mode to "display control mode". This mode displays control characters instead of acting upon them. The result is a screen filled with control codes and garbled text. Revision 03.21 corrects this issue. - Previous revisions of firmware did not implement the Platform Features Descriptor entry and the Translation Register Descriptor entry of the SAL system table. Revision 03.21 implements these entries in the SAL system table. The following fixes appear in System firmware revision 03.11: Fixed issues: - CPE error severity is now reported correctly. - FW now enforces 128MB error free memory when initing memory only. - DiskIO fix in EFI for proper alignment of Disk/Memory accesses. - SAL MCA Monarch LID fix . - SAL MCA GR11 handoff state fix. - ErrorHandler Module Specific Function Pointer fixed for virtual mode. - The "pdt clear" EFI command now only clears PDT once, not again on reboot. - Fix to enable ACC network card. - Timing/Frequency fix to fully support processors over 1 GHz. - Old CPE/CMC logs are now invalidated before attempting to log again. - Correct PalProc Addr is used during CPU Deconfig. - Memory Poisoning using unoptimized routine. - New EFI 1.1 memory requirements for RUN_TIME_MEMORY attribute. - New EFI 1.1 memory requirements for EfiAcpiReclaimMemory. - SAL System Table shows OEM_ID as Intel instead of HP. - MCA when installing Windows. - FW will now demote hard SBE's and unverified MBE's in the PDT below 128MB. This is to be in spec with the SPPA Platform EAS published April 2002. - Firmware sets incorrect PCI bus error log validation bits. - Error log severity may be incorrect for I/O errors. - Disable Mercury Strict_DCR to accommodate HP ATM cards . - Need EFI INFO CPU to display Cache Sizes. - ASSERT filenames reversed within event data. - EFI INFO SYS should display FSB frequency. - EFI INFO SYS should display date and time. - Need to remove clearing of BMC passwords. - EFI USB Driver must support USB and LS120 floppy. - Only one keyboard enabled with multiple keyboards installed. - EFI_SYSTEM_STATE_RUNNING_OK event misdefined with unused data type. - INFO SYS should display all fields settable via SYSSET. - Usb Keyboard Driver has significant memory leaks. - Memory Poisoning using unoptimized routine. Adds to boot time. - Efi Stack and backing store sizes are not per the EFI spec 2.3.3. - Delete the word 'order' from "Product Order Number" strings. - Stopboot timeout message has extra ')' when less than 10 seconds. - Long output in the Advanced System Information menu is now paged. - Update ConsoleSelection code for the Vibern USB driver. - There is a possible memory corruption caused by SFW. - INFO CPU should not display absent CPUs. - IPF will not boot with a 300i and media installed . - FTP causes a TRAP. - Boot manager does not detect removable media change. - DVD Boot option incorrect when no DVD drive present. - The device and vendor strings for internal DVD drive could be improved. The following fixes appear in System firmware revision 02.21: Fixed issues: - Intel has notified HP and other computer manufacturers of an issue with the Itanium 2 processor. Multiprocessor (MP) systems running IA-32 applications that use the "cmpxchg8b" instruction could experience hangs, halts, or data integrity issues on your system while running Windows or Linux; HP-UX is not susceptible. HP multiprocessor systems that may be affected are: the HP Server rx2600, HP Server rx5670, and the HP Workstation zx6000. The issue does not occur on the first generation Itanium processor-based systems or on recently announced Itanium 2-based single processor systems such as the HP Workstation zx2000. It also does not occur on any other Intel processors or PA-RISC or Alpha systems. This issue is not unique to HP and is a published Intel erratum on the Itanium 2 processor (Erratum 53). The problem has not been reported by any Itanium 2 processor customers. However, because Intel is strongly committed to delivering high quality products, it has developed a new PAL (Processor Abstraction Layer, a part of system firmware) that addresses the issue. HP has incorporated this new PAL into updated firmware for its Itanium 2 -based products. The following fixes appear in System firmware revision 02.11: Fixed issues: - In previous versions of firmware the unloading the EBC driver caused the system to MCA. Firmware revision 2.11 corrects this issue. - Previous revisions of firmware issued warning messages when the most current revision of MP firmware was not installed on the MP card and the revision checking scheme did not allow for newer revisions than the one hard coded in revblock when the firmware image was built. Firmware revision 2.11 corrects this issue. - Previous revisions of firmware were unable to boot from a DVD without having to remap. The following action sequence produced failures - plug the machine in, and boot it to the IPF Setup & Config DVD. - A menu called the EFI Boot manger will appear, with the following options: 1. efi shell [build in] 2. Microsoft Windows .NET Boot 3. DVD 4. Boot option maintenance menu 5. Security/Password menu - pick option 3 for DVD - The same menu will appear: 1. efi shell [build in] 2. Microsoft Windows .NET Boot 3. DVD 4. Boot option maintenance menu 5. Security/Password menu The selecting option 3 will continue to display this menu on previous revisions of firmware. - Previous revisions of EFI the "info fw" command and the "ver" command returned different values for the SAL B revision. Firmware revision 2.11 corrects this issue. - Setting the EFI console to VGA only on servers using Linux caused the system to hang with previous versions of firmware. Firmware revision 2.11 corrects this issue. - The earlier versions of rx5670 firmware did not duplicate or backup the system serial number and original product number. These variables are used for system identification. This prevented them from being restored when parts were replaced. These variables are used by management applications to identify the system and application licensing. Firmware revision 2.11 corrects this issue. - The earlier versions of rx5670 firmware did not consistently display SCSI disks being detected when executing the reconnect command. Firmware revision 2.11 corrects this issue. - When Fibre Channel cards were installed in rx5670 servers with earlier firmware and topology was changed it caused a later "reconnect -r" command to hang. Firmware revision 2.11 corrects this issue. - In Windows operating system, the manageability software starts the watchdog timer to implement a feature called ASR (Automatic Server Recovery). When the operating system enters a hung or unresponsive state the watchdog timer refresh will fail and will let the timer expire in 10 minutes. The expiration will cause a hard reset, therefore getting the server out of the hung/unresponsive state. In extreme cases when the refresh process of watchdog timer failed unexpectedly the watchdog timer kept on ticking even during the system restart that followed. Since the configured timer action is a hard reset, the system restarted again at some point while the Operating System boots up. Firmware revision 2.11 stops the watchdog timer when a reset is detected preventing the unexpected reboot. - Previous revisions of rx5670 firmware did not display PAL A and PAL B revision numbers with the "info FW" command. - In earlier versions of firmware if power to the system and the battery failed at the same time the date and time would be set to an invalid value. This prevented the user from resetting the date and time to a correct Date and Time. This issue is corrected by firmware revision 2.11. Defect Description: PHSS_29649: - See Symptoms. Enhancement: No SR: 0000000000 Patch Files: OS-Core.KERN-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA/PA,v=HP: OS-Core.KERN-RUN,fr=B.11.23,fa=HP-UX_B.11.23_IA/PA,v=HP: /usr/conf/OSIFU/fwupdate.efi /usr/conf/OSIFU/updatebootsequence what(1) Output: OS-Core.KERN-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA/PA,v=HP: /usr/conf/OSIFU/fwupdate.efi: verscode: 03.23.rx5670_ia64.view datecode: 4347 built with: makerom -C -O -V=3.23 -L=EVERMAD_RELEASE _3_23_ROS on Tue Nov 25 12:32:00 PST 2003 ROM : Official Build SFW 3.23 for rx5670 localtime.c 7.57 asctime.c 7.7 /usr/conf/OSIFU/updatebootsequence: None cksum(1) Output: OS-Core.KERN-RUN,fr=B.11.22,fa=HP-UX_B.11.22_IA/PA,v=HP: 1873829041 10139136 /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: 3410 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_29649 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_29649.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_29649. 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_29649.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_29649.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_29649.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: 1. 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 touching 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. 2. 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. 3. The firmware update is accomplished by temporarily altering the boot sequence. To identify the disk, 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 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. 4. It is recommended that the firmware update is performed outside of an OS update or Update-UX session. If a firmware update is performed, it will be excluded from installation to ensure that OS update or Update UX is successful. 5. The firmare update will be excluded from installation if the firmware revision in the patch is the same or older than the one the system is running on. This will ensure that no un-necessary system reboot occurs. 6. 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. 7. The firmware update will be excluded from installation if the system has a BMC administrator password set. If this password is set, it must be cleared by connecting to the Management Processor and running the BP command from the Command Menu prior to installing the patch. 8. Do not attempt to update firmware on the Management Processor via the network while updating system firmware.