Patch Name: PHSS_30838 Patch Description: s700_800 11.11 rp3410/rp3440 PDC44.24,BMC02.34,MPE.02.29 FW Creation Date: 04/08/02 Post Date: 04/08/26 Hardware Platforms - OS Releases: s700: 11.11 s800: 11.11 Products: N/A Filesets: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP Automatic Reboot?: Yes Status: General Release Critical: Yes PHSS_30838: PANIC HANG - See Symptoms. PHSS_30676: PANIC - See Symptoms. Category Tags: defect_repair hardware_enablement enhancement general_release critical firmware panic halts_system Path Name: /hp-ux_patches/s700_800/11.X/PHSS_30838 Symptoms: PHSS_30838: The following features, fixes and enhancements appear in server firmware revision 44.24: Added full memory and IO support for new single core product rp3440#1. Enables upgrade from a 1-way rp3410 to a 1-way rp3440. Enables upgrade from a 1-way rp3410 to a full-way rp3440. Resolved an issue where the system would fail to dump following a TOC. ErrorHandler will now send chassis codes to indicate the type of error encountered. In the case of a DMT entry not being found the system will halt and send out a DMT_ENTRY_NOT_FOUND chassis code. Added two chassis codes to send out the entire part number of the memory extender. Resolved an issue which caused HPUX to incorrectly report installed physical memory. Low Priority Machine Checks are turned off until HPUX boot is complete to avoid improperly registering a Low Priority Machine Check. Corrected a parity error chassis code from returning incorrect data and triggering attention LED on every BCH boot during a memory ECC test. Resolved an issue which caused random memory rank deallocations due to a missing resistor on the memory extender. Corrected an issue that resulted in a stopped processor after running an MP memory test. Corrected an issue where AUTOSTART flag was incorrectly read from stable store and when set, prevented autoboot and autosearch. Resolved an issue when booting add-on PCI LAN cards that allowed the first LAN server to respond to boot the machine. In previous versions, a PDC_ALLOC request to allocate space would return SUCCESS even when there was insufficient storage to do so. Resolved an issue that resulted in a HPMC when attempting to boot on single core systems. Corrected an issue that resulted in no PIM for an L1 cache error. Resolved an issue that caused a memory hang when multiple memory errors are detected. Corrected an issue that cleared the PDT on hard reset resulting in changes to memory configuration to be lost between DC power cycles. Added logging of inbound correctable and uncorrectable errors. Initialized a variable that when uninitialized, caused a CC_MEM_EXTENDER_SPD_ERROR event indicating the memory extender SPD couldn't be read. Corrected an issue that filled the SEL log with PDCE_CALL_TAKE_TOO_LONG events which would require clearing the log before using autoboot. Resolved an issue where an ACC card (Z7340A) placed in a PCI slot could not be mapped due to insufficient memory failure. Corrected an issue where the Tachlite FibreChannel IODC driver (A6795A) failed to come online with the B-Series and M-Series switches at port F set at 2Gbps fixed speed, resulting in an FibreChannel boot failure at the BCH prompt: "IODC ENTRY_INIT failed. Error Status: -4". The following features, fixes and enhancements appear in BMC firmware revision 02.34: Disabled unsupported wake on LAN function. The following features, fixes and enhancements appear in Management Processor firmware revision E.02.29: Resolves a problem that resulted in a missing Web Console applet on systems updated during factory integration. Systems upgraded in the field should not be affected. MP did not show proper number of processors on rp3410, rp3440 and rp4440 systems in previous revisions of Management Processor firmware. VFP shows System state of "unknown" after MP upgrade (via LAN) in previous revisions. HE command with bad input causes garbage output in previous revisions. TELNET connections could hang for up to 30 minutes while waiting for the Management Processor ARP table to clear on firmware revisions prior to E.02.29. PHSS_30676: The following features, fixes and enhancements appear in server firmware revision 44.12: rp3410 systems may experience an HPMC during early boot. PDC revision 44.12 corrects the issue. Defect Description: PHSS_30838: - See Symptoms. PHSS_30676: - See Symptoms. Enhancement: Yes PHSS_30838: - See Symptoms. SR: 0000000000 Patch Files: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP: /usr/conf/rp3440srvrflash /usr/conf/rp3440saveFW /usr/conf/rp3440fw.wrap /usr/conf/rp3440bmcfw.wrap /usr/conf/rp3440gspfw.wrap /usr/conf/rp3440version.inf what(1) Output: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP: /usr/conf/rp3440srvrflash: Server Firmware Reflash Utility version 2.03 for PA- RISC Servers /usr/conf/rp3440saveFW: $Revision: 92453-07 linker linker crt0.o B.11.33 020 605 $ Data Hdr A 00.01 Save Firmware Image Utility Rev 1.1a _ HP-UX Version 11.11 /usr/conf/rp3440fw.wrap: Data Hdr A.00.01 ------------------------------------------------ MW_0313_4424 Fri Jun 4 09:09:42 PDT 2004 ------------------------------------------------ Mako CPU API Library Version 1.139 /usr/conf/rp3440bmcfw.wrap: Data Hdr A.00.01 /usr/conf/rp3440gspfw.wrap: Revision E.02.29 Mar 17 2004,16:25:21 /usr/conf/rp3440version.inf: Data Hdr A.00.01 cksum(1) Output: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP: 1898359452 132896 /usr/conf/rp3440srvrflash 4091073230 32768 /usr/conf/rp3440saveFW 2383931619 4195584 /usr/conf/rp3440fw.wrap 852658780 748800 /usr/conf/rp3440bmcfw.wrap 1206065900 3431063 /usr/conf/rp3440gspfw.wrap 2080046113 52 /usr/conf/rp3440version.inf Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: 9000/800/rp3410 9000/800/rp3440 9000/800/rp3440#1 Other Dependencies: None Supersedes: PHSS_30676 Equivalent Patches: None Patch Package Size: 2590 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_30838 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_30838.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_30838. 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_30838.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_30838.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_30838.depot of=/dev/rmt/0m bs=2k Special Installation Instructions: 1. This patch will only install and update the firmware on these systems: 9000/800/rp3410 9000/800/rp3440 9000/800/rp3440#1 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 the SUPPORT-TOOLS or Online Diagnostics software is installed, the existing system firmware will be saved during the installation of the patch, but the existing BMC and MP firmware will not be saved. In this case, if the patch is removed the original system firmware will be restored, but the BMC and MP firmware installed by the patch will remain loaded. If neither the SUPPORT-TOOLS nor Online Diagnostics software are installed, the existing system firmware will not be saved during the installation of the patch. In this case, if the patch is removed the original system firmware will not be restored and the firmware installed by the patch will remain loaded after the patch is removed. 3. The firmware update is accomplished by temporarily modifying the autoboot file on the primary boot disk. 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 and older than the one the system is running on. This will ensure that no un-necessary system reboot occurs. Use 'swremove' command to restore/go back to previous firmware revision. 6. The firmware update will be excluded from installation if the system is running in a VPAR session. To update the firmware, shut down all VPAR's and reboot the server into standalone mode using the primary path. 7. 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 setboot(1M) command to set the autoboot flag on prior to installing the patch.