Patch Name: PHSS_30726 Patch Description: s700_800 11.11 rp24xx 43.50 PDC Firmware Patch Creation Date: 04/04/07 Post Date: 04/04/20 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: No (superseded patches were critical) PHSS_29937: PANIC HANG -See Symptoms. PHSS_28612: ABORT PANIC HANG -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_30726 Symptoms: PHSS_30726: Corrected an issue that prevented firmware from updating properly and produced the following error message during the update process Firmware reflash utility: SPU HVersion = 0x5e2 Software error detected at line 313 PHSS_29937: The following features, fixes and enhancements appear in server firmware revision 43.50: 1 - Added an enhancement to preserve user configurable information across a firmware update, systems that loose configurable information could Panic or hang. 2 - Corrected an issue preventing revision A GSP's from being properly identified. 3 - A remote possibility exists in the IODC subset of PDC on all PA-RISC systems (affecting PCI Fibre Channel Adapter cards A5158A and A6795A) that can allow a return from a read operation without actually reading the requested block from the disk. This can result in kernel text, kernel static data, and ioconfig file to be read into memory incorrectly. This will result in either a system crash with a High Priority Machine Check (HPMC) or a panic (during boot-up or later). This was discovered in extreme lab testing and has now been resolved. PHSS_28612: The following features, fixes and enhancements appear in server firmware revision 43.24: 1 - Added boot, swap and dump support for A7173A PCI-X 2 Port Ultra320 SCSI Card. 2 - Added boot/dump support for A6826A 2 Port 2GB Fibre Channel Card. 3 - Added boot, swap and dump support for A7143A Raid U160 Card. 4 - PDC revision 43.24 corrects an issue that causes characters to be dropped at BCH after updating GSP firmware to revision C.02.14. 5 - PDC revision 43.24 correctly identifies a revision B GSP when executing the BCH command "CO DE". Previous revision identified revision B GSPs as revision A and set the console path incorrectly. 6 - Previous revisions of PDC HPMC'ed when entering an invalid primary path of 0/65/0. Revision 43.24 corrects this issue. 7 - Increased the Page Deallocation Table ( PDT) to 256 entries from 50. Systems using EMS should update to the diagnostics in HWE0306, not doing so could cause erratic behavior of the memory monitor. 8 - Revision of PDC prior to 43.24 would attempt to boot from the console port if the console path was set as the boot path. This revision prevents the behavior. 9 - HPMC chassis codes reported incorrect PDC base address. in previous revisions of PDC. PDC revision 43.24 reports the correct address. 10 - Executing a TC after an abort occasionally caused an HPMC in previous revisions of firmware. PDC revision 43.24 corrects this issue. 11 - In very intermittent cases a Rope 1 reset would cause an HPMC on previous revisions of PDC. PDC Revision 43.24 corrects this issue. 12 - Deconfigured CPU's could prevent system from booting on earlier revisions of PDC firmware. PDC revision 43.24 corrects this issue. 13 - Previous revisions of PDC could experience unaligned data reference traps after mapping in Hyperfabric. PDC revision 43.24 corrects this issue. 14 - Previous revisions of firmware experienced longer than expected boot and dump times on VA arrays connected to a Tachlite card. PDC revision 43.24 corrects this issue. 15 - Previous revisions of firmware did not process LPMCs properly. A register was overwritten causing the system to panic. PDC revision 43.24 corrects this issue. 16 - Tachlite Fibre channel cards did not properly auto speed negotiate with switch/device ports locked at 2gig speed. Revision 43.24 corrects this issue. 17 - A problem in the PDC Icache data parity error handler on PA8700 based systems causes multiple LPMCs. The current PDC attempts to repair a cache parity error, called scrubbing, by writing zeros to the failing cache line and marking the line invalid. This forces a new fetch of the cache line, clearing the parity error. The current PDC, calculates the index of the Icache data line using the Dcache index. Previous processors had identical indexes for both, so this was not a problem on previous processors. The PA8700 and subsequent processors use different indexes for the Icache and the Dcache. This issue generates multiple LPMCs while attempting to scrub the cache line when a parity error is experienced. Since the wrong cache line will be scrubbed, the parity error is not cleared thus causing a repeat LPMC when the parity error is experienced. The processor remains in the LPMC handler until internal system processes timeout waiting for the processor to return. PDC revision 43.24 corrects this issue. 18 - Added boot, swap and dump support for A9782A PCI-X 2GB FC / 1000Base-SX (Fibre) Combo Card 19 - Added boot, swap and dump support for A9784A PCI-X 2GB FC / 1000Base-T (Copper) Combo Card 20 - Added boot, swap and dump support for A5149A PCI Card. PHSS_27384: The following features, fixes and enhancements appear in server firmware revision 42.19: Starting with firmware revision 42.03 the software id was calculated incorrectly. Firmware revision 42.19 corrects the error and calculates the software id correctly. PHSS_26540: The following features, fixes and enhancements appear in server firmware revision 42.09: Intermittent Alert Level 4 events occurring during power on Selftest/PDC Initialization. The Alert Level 4 error would look similar to this: ----------------------------------------------------------- SYSTEM NAME: DATE: 11/29/2001 TIME: 16:22:52 ALERT LEVEL: 4 = Unexpected configuration change detected REASON FOR ALERT SOURCE: 8 = I/O SOURCE DETAIL: 3 = local bus adapter SOURCE ID: FF PROBLEM DETAIL: 3 = function failure LEDs: RUN ATTENTION FAULT REMOTE POWER FLASH OFF OFF OFF ON LED State: Running non-OS code. (i.e. Boot or Diagnostics) 0x2000004383FF2083 000000FF FF05FF83 - type 4 = Physical 0x5800084383FF2083 0000650A 1D101634 - type 11 = Timestamp ----------------------------------------------------------- Intermittent Alert Level 6 GSP errors similar to the one below occurring during poweron Selftest/PDC Initialization ----------------------------------------------------------- SYSTEM NAME: DATE: 01/29/2002 TIME: 09:47:14 ALERT LEVEL: 6 = Boot possible, pending failure - action SOURCE: 8 = I/O SOURCE DETAIL: 9 = serial SOURCE ID: 0 PROBLEM DETAIL: 3 = functional failure CALLER ACTIVITY: 1 = test STATUS: 0 CALLER SUBACTIVITY: 4C = implementation dependent REPORTING ENTITY TYPE: 0 = system firmware REPORTING ID:00 0x00000063890014C0 00000000 00000000 type 0 = Data Field 0x58000863890014C0 00006600 1D092F0E type 11 = Timestamp ----------------------------------------------------------- PDC Revision 42.09 corrects these problems. PHSS_26444: The following features, fixes and enhancements appear in server firmware revision 42.03. - Added support for 2GB FC boot. - Added support for PCI-PCI Bridge boot/swap/dump. - Added support for Ultra 160 SCSI boot/swap/dump. - Added FRU location to FRU id values. - Earlier versions of PDC prevented online diagnostics for reading pim data. PDC revision 42.03 corrects this problem. - HPMC chassis codes reported an incorrect PDC base address . When the chassis code is sent for HPMC MONARCH SELECTED it will now report the full 64 bit address. - Previous revisions of PDC prevented MPE systems from properly handling a Transfer Of Control (TOC) when LDEV1 was not on an internal disk. PDC revision 42.03 properly handles TOC's on an MPE system. - The PCI reset time did not meet the minimum required by the PCI specifications, it has been changed to meet the specification. - Earlier versions of PDC prevented online diagnostics for reading PIM data. PDC revision 42.03 corrects this problem. PHSS_25315: The following features, fixes and enhancements appear in server firmware revision 41.18. - Added support for Telco systems. PHSS_23515: The following features, fixes and enhancements appear in server firmware revision 41.17. - Added support for RAID boot on the A5658A card. - Corrected problem with MPE software clock losing 15 minutes per hour. - Added support for PCI combo card A5838A, including support for root/boot/swap. - Added 'scroll' command to the BCH Service menu. This command allows the screen to scroll when using BCH utilities. - Added 'sn' command to the BCH Service menu. This command displays the serial number stored in stable storage. PHSS_23156: This patch is a Firmware update for the HP9000 Model A400 & A500 systems. The following features, fixes and enhancements appear in server firmware revision 40.50: 1. Provide support for revision 3.1 processors 2. PDC Memory allocation failed second call. 3. Corrected EMS error stating "An insufficient number of fans are installed in the cabinet to cool the unit". 4. PDC call PDC_PAT_COMPLET subfun 6 (get cabinet info) fails repeatedly with -3 5. Entry _I/O on IODC Call, Status = +4294967291 6. Added support for RAID IODC 7. "in io" prints output for the same PCI-to-PCI bridge twice 8. Change model string from 9000/800/A500-55 to 9000/800/A500-5X. 9. Added Support for MPE Detailed Explanation: 1. Self explanatory 2. This problem appears when a search command is done at the BCH prompt and multiple fibre channel or a RAID cards are installed in the system. PDC memory allocation subroutines were changed to properly handle multiple requests. 3. Previous versions of PDC caused EMS to report the following error: "An insufficient number of fans are installed in the cabinet to cool the unit." This error was reported even when all 5 cabinet fans are functioning. PDC 40.50 corrects the error. 4. The PDC subroutine PDC_PAT_COMPLET subfun 6 did not poll the power monitor or other PDH hardware properly this caused EMS to report errors. PDC 40.50 firmware correctly poll all PDH hardware so EMS will report correct status. 5. At power on, pressing the Break key on the console or power cycling the console caused an unrecoverable IODC error "Entry _I/O on IODC Call, Status = +4294967291". The PDC error handling routines were changed to properly handle these occurrences. 6. Self explanatory 7. When executing the BCH command "in io" the PCI-to-PCI bridges were list before and after HBA's connected to the bridge. PDC was revised to list the PCI-to-PCI bridge before the HBA's connected to it. 8. When a processor is downgraded from 550Mhz to 440Mhz the model string will be modified to 9000/800/ A500-44. PDC revision 40.50 also changes the model string on 550Mhz machines from 9000/800/A500-55 to 9000/800/A500/5X. 9. Self explanatory. Defect Description: PHSS_30726: - See Symptoms. PHSS_29937: - See Symptoms. PHSS_28612: - See Symptoms. PHSS_27384: - See Symptoms. PHSS_26540: - See Symptoms. PHSS_26444: - See Symptoms. PHSS_25315: - See Symptoms. PHSS_23515: - See Symptoms. PHSS_23156: - See Symptoms. Enhancement: No (superseded patches contained enhancements) PHSS_29937: - See Symptoms. PHSS_28612: - Added Boot Swap and Dump for PCI Card see symptoms. See Symptoms for details. SR: 0000000000 Patch Files: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP: /usr/conf/A400srvrflash /usr/conf/A400saveFW /usr/conf/A400fw.wrap what(1) Output: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP: /usr/conf/A400srvrflash: Server Firmware Reflash Utility version 1.19 for A,L ,N-class Servers /usr/conf/A400saveFW: Data Hdr A 00.01 /usr/conf/A400fw.wrap: 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: 3670825482 61192 /usr/conf/A400srvrflash 2404285325 32768 /usr/conf/A400saveFW 834037184 2098432 /usr/conf/A400fw.wrap Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: 9000/800/A400-36 9000/800/A400-44 9000/800/A500-55 9000/800/A500-5X 9000/800/A500-44 9000/800/A400-6X 9000/800/A500-6X 9000/800/A500-7X Other Dependencies: None Supersedes: PHSS_28612 PHSS_27384 PHSS_26540 PHSS_26444 PHSS_25315 PHSS_23515 PHSS_23156 PHSS_29937 Equivalent Patches: PHSS_30725: s700: 11.00 s800: 11.00 Patch Package Size: 550 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_30726 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_30726.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_30726. 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_30726.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_30726.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_30726.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/A400-36 9000/800/A400-44 9000/800/A500-55 9000/800/A500-5X 9000/800/A500-44 9000/800/A400-6X 9000/800/A500-6X 9000/800/A500-7X 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 firmware will be saved during the installation of the patch. In this case, if the patch is removed, the original firmware will be restored. If neither the SUPPORT-TOOLS nor Online Diagnostics software is installed, the existing firmware will not be saved during the installation of the patch. In this case, if the patch is removed the original 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.