Patch Name: PHSS_30632 Patch Description: s700_800 11.11 L1500 and L3000 44.12 PDC Firmware Patch Creation Date: 04/03/22 Post Date: 04/04/23 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_29941: PANIC HANG - See Symptoms PHSS_28608: OTHER - 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_30632 Symptoms: PHSS_30632: The following features, fixes and enhancements appear in server firmware revision 44.12: 1 - PDC revision 43.43 creates the following message in the dmesg file: /ux/core/kern/common/io/pat_psm.c: pat_event_clear - handle status - 10 loc 0xa548b8 event 0x40000000000 PDC revision 44.12 removes the message. 2 - 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_29941: The following features, fixes and enhancements appear in server firmware revision 43.43: 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_28608: The following features, fixes and enhancements appear in server firmware revision 43.22: 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.22 corrects an issue that causes characters to be dropped at BCH after updating GSP firmware to revision B.02.20. 5 - PDC revision 43.22 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.22 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.22 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.22 reports the correct address. 10 - Previous revision of PDC could not allocate PDH Scratch Buffer when executing IKEDIAG2. Revision 43.22 corrects this issue. 11 - Executing a TC after an abort occasionally caused an HPMC in previous revisions of firmware. PDC revision 43.22 corrects this issue. 12 - Deconfigured CPU's could prevent system from booting on earlier revisions of PDC firmware. PDC revision 43.22 corrects this issue. 13 - Previous revisions of PDC could experience unaligned data reference traps after mapping in Hyperfabric. PDC revision 43.22 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.22 corrects this issue. 15 - Tachlite Fibre channel cards did not properly auto speed negotiate with switch/device ports locked at 2gig speed. Revision 43.22 corrects this issue. 16 - 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 out 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, this wasn't a problem on previous processors. The PA8700 and subsequent cpus use different indexes for the Icache and the Dcache. This issue causes 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.22 corrects this issue. 17 - Previous revisions of firmware reported erroneous DIMM distribution errors when mixing 1GB DIMMs with different refresh rates. The memory distribution warning is displayed at BCH when refresh rates are mixed between extenders. Sample false error scenarios. System ( N4000 8 CPU 750MHz ) PDC : 41.36 Memory Type A: refresh rate : 15.6 usec Memory Type B: refresh rate : 7.8 usec Memory Configuration and the Results Case# Carrier 0 Carrier 1 Carrier 2 Results 1 AAAAAAAA BBBBBBBB AAAAAAAA ALERT LEVEL: 8 2 AAAAAAAA BBBBBBBB ALERT LEVEL: 8 3 BBBBBBBB AAAAAAAA ALERT LEVEL: 8 4 AAAAAAAA AAAAAAAA No Error message 5 AAAABBBB No Error message 6 AAAABBBB AAAABBBB No Error message 7 AAAABBBB AAAABBAA No Error message 8 AAAAAAAA BBAAAAAA No Error message 9 AAAAAAAA BBBBBBAA ALERT LEVEL: 8 10 AAAAAAAA BBBBAAAA ALERT LEVEL: 8 11 AAAA BBAA No Error message 12 AAAA BBBB ALERT LEVEL: 8 13 ABAA DIMM Mismatch: 18 - Previous revisions of firmware reported some PA8700 CPU's as PA8600 CPU's. Revision 43.22 corrects this issue. 19 - Added boot, swap and dump support for A9782A PCI-X 2GB FC / 1000Base-SX (Fibre) Combo Card. 20 - Added boot, swap and dump support for A9784A PCI-X 2GB FC / 1000Base-T (Copper) Combo Card. PHSS_27467: The following features, fixes and enhancements appear in server firmware revision 42.19: Added support for CPU product numbers A6152B and A6805B. PHSS_26532: The following features, fixes and enhancements appear in server firmware revision 42.06: 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.06 corrects thiese problems. PHSS_25687: The following features, fixes and enhancements appear in server firmware revision 41.46: - 1GB DIMMs have been produced with 2 different refresh rates, both types are usable in L-Class and N-Class servers however, the newer DIMMs that have a faster refresh rate could not be used in the same DIMM pair as the older DIMMs. Older PDC revisions also required DIMMs with different refresh rates to be distributed in the system like DIMMs of different sizes. PDC 41.46 allows the DIMMs to mixed in the same DIMM pair and removes distribution restrictions. - Earlier versions of PDC prevented online diagnostics for reading PIM data. PDC revision 41.46 corrects this problem. - previous versions of PDC were unable to dump using the A6795A 2Gb Fibre Channel HBA on all platforms, unable to to dump to disks on Point to Point Fabric with McData switches and unable to boot/dump with Brocade 3800 2GB Switches with A6795A cards installed. PDC revision 41.46 fixes these issues. - 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. - 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. - Changed IODC to allow DDS4 tape drives to operate in LVD mode on the A5149A SCSI Card. -Improved single memory error handling. PHSS_25104: The following features, fixes and enhancements appear in server firmware revision 41.36: 1. Added 'sn' command to BCH Information menu. This command displays the serial number stored in stable storage. 2. Added 'scroll' command to BCH Service menu. This command allows the display to scroll when using BCH utilities. 3. Enabled use of PA8700 revision 2.3 CPU's. 4. 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 41.36 properly handles TOC's on an MPE system. 5. 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. 6. The PDC revision number was displayed incorrectly, it has been changed to display correctly. 7. The PCI reset time did not meet the minimum required by the PCI specifications, it has been changed to meet the specification. 8. Changed IODC to allow DDS4 tape drives to operate in LVD mode on A5149A SCSI Card. 9. When a PCI I/O card is added or replaced Online, the PCI slot is left in a state from which is not designed to handle some types of errors. This may result in potential data integrity issues. These OLAR operations should not be performed on these systems until the PDC of the system is upgraded to revision 41.36. Defect Description: PHSS_30632: - See Symptoms. PHSS_29941: - See Symptoms. PHSS_28608: - See Symptoms items 1, 2, 3, 19 and 20. PHSS_27467: - See Symptoms. PHSS_26532: - See Symptoms. PHSS_25687: - See Symptoms. PHSS_25104: - See Symptoms. Enhancement: No (superseded patches contained enhancements) PHSS_29941: - See Symptoms. PHSS_28608: - 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/L3000srvrflash /usr/conf/L3000saveFW /usr/conf/L3000fw.wrap what(1) Output: OS-Core.KERN-RUN,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP: /usr/conf/L3000srvrflash: Server Firmware Reflash Utility version 1.19 for A,L ,N-class Servers /usr/conf/L3000saveFW: Data Hdr A 00.01 /usr/conf/L3000fw.wrap: Data Hdr A.00.01 PDC version: 354 from view: ARIA012 by: pedersen 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/L3000srvrflash 2404285325 32768 /usr/conf/L3000saveFW 121640588 2098432 /usr/conf/L3000fw.wrap Patch Conflicts: None Patch Dependencies: None Hardware Dependencies: 9000/800/L3000-5x 9000/800/L3000-6x 9000/800/L3000-7x 9000/800/L3000-8x 9000/800/L1500-5x 9000/800/L1500-6x 9000/800/L1500-7x 9000/800/L1500-8x Other Dependencies: None Supersedes: PHSS_25104 PHSS_25687 PHSS_26532 PHSS_27467 PHSS_28608 PHSS_29941 Equivalent Patches: PHSS_30631: s700: 11.00 s800: 11.00 Patch Package Size: 560 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_30632 5. Run swinstall to install the patch: swinstall -x autoreboot=true -x patch_match_target=true \ -s /tmp/PHSS_30632.depot By default swinstall will archive the original software in /var/adm/sw/save/PHSS_30632. 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_30632.text file is available in the product readme: swlist -l product -a readme -d @ /tmp/PHSS_30632.depot To put this patch on a magnetic tape and install from the tape drive, use the command: dd if=/tmp/PHSS_30632.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/L3000-5x 9000/800/L3000-6x 9000/800/L3000-7x 9000/800/L3000-8x 9000/800/L1500-5x 9000/800/L1500-6x 9000/800/L1500-7x 9000/800/L1500-8x 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 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. 7. 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.