**************************** ECO SUMMARY INFORMATION **************************** Release Date: 11-MAY-2007 Kit Name: DEC-AXPVMS-VMS83A_FIBRE_SCSI-V0100--4.PCSI$COMPRESSED Kit Applies To: OpenVMS ALPHA V8.3 Approximate Kit Size: 1779 blocks Installation Rating: INSTALL_2 Required Features: Fibrechannel, SCSI Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS83A_UPDATE-V0200 or later Optional Kit Dependencies: None Checksums: VMS83A_FIBRE_SCSI-V0100.ZIPEXE Checksum: 1673974029 DEC-AXPVMS-VMS83A_FIBRE_SCSI-V0100--4.PCSI$COMPRESSED Checksum: 309141024 VMS83A_FIBRE_SCSI-V0100.ZIPEXE MD5 Checksum: 7D3C0C5DAF2215DBBCCBE22BE97745B5 DEC-AXPVMS-VMS83A_FIBRE_SCSI-V0100--4.PCSI$COMPRESSED MD5 Checksum: CE44E8B9E62C7075B7A4655AA01EFEA1 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= 1 KIT NAME: VMS83A_FIBRE_SCSI-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2 : To be installed by all customers using the following feature(s): - Fibrechannel, SCSI 2.2 Reboot Requirement: Reboot Required. HP strongly recommends that a reboot is performed immediately after kit installation to avoid system instability. If you have other nodes in your OpenVMS cluster, they must also be rebooted in order to make use of the new image(s). If it is not possible or convenient to reboot the entire cluster at this time, a rolling re-boot may be performed. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS ALPHA V8.3 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS83A_UPDATE-V0200 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS83A_FIBRE_SCSI-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 System Crash With INVEXCEPTN, Exception while above ASTDEL Bugcheck 5.2.1.1 Problem Description: A SCSI adapter hardware error can result in an iNVEXCEPTN, exception while above ASTDEL bugcheck in SYS$PKWDRIVER.EXE. Crashdump Summary Information ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.803A5FC4 SYS$PKWDRIVER+0DFC4 Failing PS: 00000000.00001504 Module: SYS$PKWDRIVER (Link Date/Time: 11-APR-2006 13:11:15.84) Offset: 0000DFC4 The crash occurs because the PKWDRIVER driver does not have the ability to handle this type of error. This change allows the driver to handle this type of error and prevent a system crash. The SYS$PKWDRIVER.EXE change does not correct the underlying cause of the error. Users may still experience the error but the system will not crash. Instead, users will see errors occurring in groups - a device_attention and then a device_error from each disk on that bus that is being accessed. The device_attention error causes a SCSI bus reset which will then cause the disks to report that they've seen a bus reset. This problem affects DS10, DS20 and ES40 family of systems running OpenVMS Alpha V8.2 it specifically supports the KZPBA-xx SCSI card. Engineering is Page 3 continuing to investigate the root cause of the error. Images Affected: - [SYS$LDR]SYS$PKWDRIVER.EXE 5.2.1.2 CLDs, and QARs reporting this problem: 5.2.1.2.1 CLD(s) QXCM1000333503 5.2.1.2.2 QAR(s) None. 5.2.1.3 Problem Analysis: The crash occurred when the adapter interrupted the driver during a SCSI bus phase change, without a valid IO structure pointer. The driver crashed trying to access the IO structure. 5.2.1.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.1.5 Work-arounds: None. 5.2.2 Excessive Mount Verify Events 5.2.2.1 Problem Description: DS20 and ES40 platforms see many mount verify events for disks connected to KZPCA and KZPCM SCSI controllers. For this error to occur the following conditions must apply: o The Entry_Type field must be "VMS Asynchronous Device Attention" o The PKW_Error_type field must be 4 Images Affected: Page 4 - [SYS$LDR]SYS$PKWDRIVER.EXE 5.2.2.2 CLDs, and QARs reporting this problem: 5.2.2.2.1 CLD(s) QXCM1000296362,1000303532,1000319591,1000322382 5.2.2.2.2 QAR(s) None. 5.2.2.3 Problem Analysis: See problem description. 5.2.2.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.2.5 Work-arounds: None. 5.2.3 SSRVEXCEPT System Crash 5.2.3.1 Problem Description: Issuing the following HSZTERM command may crash the system with SSRVEXCEPT bugcheck: SET HOST/SCSI $1$GGAXXX SHOW STORAGE FULL Images Affected: - [SYS$LDR]SYS$GKDRIVER.EXE - [SYS$LDR]SYS$DKDRIVER.EXE - [SYS$LDR]SYS$MKDRIVER.EXE Page 5 5.2.3.2 CLDs, and QARs reporting this problem: 5.2.3.2.1 CLD(s) QXCM1000308088,WFM1209719167-121 5.2.3.2.2 QAR(s) None. 5.2.3.3 Problem Analysis: This crash is due to a synchronization issue when multiple processes access the diagnose buffer while executing in the FDT context. 5.2.3.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.3.5 Work-arounds: None. 5.2.4 Disk Size Increase Past One Terabyte Limit 5.2.4.1 Problem Description: Customers that use HSV type controllers can increase disk size past the one terabyte limit. This will cause INIT and MOUNT commands to fail and the volume to become unusable. Also certain XQP functions like SET VOLUME/SIZE will fail to use this excess size. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE 5.2.4.2 CLDs, and QARs reporting this problem: 5.2.4.2.1 CLD(s) None. Page 6 5.2.4.2.2 QAR(s) 75-112-77 5.2.4.3 Problem Analysis: See problem description. 5.2.4.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.4.5 Work-arounds: None. 5.2.5 Pool Fragmentation 5.2.5.1 Problem Description: Pool fragmentation can be a factor in a number of different crashes. Although not correcting a specific failure, this problem correction eliminates many of the causes of pool fragmentation in the fibre channel drivers, the heaviest consumers of pool in the SCSI facility. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 5.2.5.2 CLDs, and QARs reporting this problem: 5.2.5.2.1 CLD(s) None. 5.2.5.2.2 QAR(s) 75-13-1707 Page 7 5.2.5.3 Problem Analysis: See problem description. 5.2.5.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.5.5 Work-arounds: None. 5.2.6 Boot Process Hangs 5.2.6.1 Problem Description: The boot process can hang for four minutes and the fibre channel devices not be configured. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 5.2.6.2 CLDs, and QARs reporting this problem: 5.2.6.2.1 CLD(s) None. 5.2.6.2.2 QAR(s) None. 5.2.6.3 Problem Analysis: For ELS requests, the default Emulex timeout of 240 seconds was used. Thus, during boot, if the initial FLOGI failed, the driver would hang the boot process for four minutes and the fibre channel devices would not be configured. This change significantly shortens ELS command timeout values. In the event of an FLOGI failure, this change has the effect of shortening the boot time as well as allowing time for retries (which, if successful, will allow for the configuration of the FC devices). Page 8 5.2.6.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.6.5 Work-arounds: None. 5.2.7 Hung Fibre Channel, SCSI or SAS Disk 5.2.7.1 Problem Description: A fibre channel, SCSI or SAS disk can hang. If a process with outstanding IO to the hung volume tries to exit, the process will hang in RWAST state waiting for the hung IO to complete. Images Affected: - [SYS$LDR]SYS$PKMDRIVER.EXE - [SYS$LDR]SYS$PKRDRIVER.EXE 5.2.7.2 CLDs, and QARs reporting this problem: 5.2.7.2.1 CLD(s) None. 5.2.7.2.2 QAR(s) 75-109-1719,75-109-1767 5.2.7.3 Problem Analysis: The hang is due to a synchronization issue. 5.2.7.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 Page 9 5.2.7.5 Work-arounds: None. 5.2.8 System crash with CPUSPINWAIT Bugcheck. 5.2.8.1 Problem Description: 1. The system can crash with a CPUSPINWAIT bugcheck. 2. Various types of crashes can be caused by kilobytes of pool being overwritten. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 5.2.8.2 CLDs, and QARs reporting this problem: 5.2.8.2.1 CLD(s) None. 5.2.8.2.2 QAR(s) 75-13-1707 5.2.8.3 Problem Analysis: If the target (STDT) disconnects while holding several port-specific resources, the resources can be permanently lost. The crashes and overwritten pool occur when the driver tries to allocate new resources to replace those that were lost. 5.2.8.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 Page 10 5.2.8.5 Work-arounds: None. 5.2.9 System Crash with INCONSTATE Bugcheck or ACCVIO 5.2.9.1 Problem Description: The system can crash with an INCONSTATE bugcheck or ACCVIO when allocation of an FCCD off of a statically-sized list fails. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE 5.2.9.2 CLDs, and QARs reporting this problem: 5.2.9.2.1 CLD(s) None. 5.2.9.2.2 QAR(s) None. 5.2.9.3 Problem Analysis: See problem description. 5.2.9.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Alpha after V8.3 5.2.9.5 Work-arounds: None. 5.2.10 Boot Process Hangs and Fibre Channel Devices Are Not Configured Page 11 5.2.10.1 Problem Description: The boot process can hang for four minutes and the Fibre Channel devices not be configured. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 5.2.10.2 CLDs, and QARs reporting this problem: 5.2.10.2.1 CLD(s) None. 5.2.10.2.2 QAR(s) None. 5.2.10.3 Problem Analysis: For ELS requests, the default Emulex timeout of 240 seconds was used. Thus, during boot, if the initial FLOGI failed, the driver would hang the boot process for four minutes and the Fibre Channel devices would not be configured. This change significantly shortens ELS command timeout values. In the event of an FLOGI failure, this change has the effect of shortening the boot time as well as allowing time for retries (which, if successful, will allow for the configuration of the FC devices). 5.2.10.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 5.2.10.5 Work-arounds: None. 5.2.11 Memory Leak Page 12 5.2.11.1 Problem Description: In PGA and FGE drivers, the header field used to store the size of pool allocations was a word in size. When allocation sizes exceeded the value that could be stored in a word, the subsequent deallocation would leak memory. Images Affected: - [SYS$LDR]SYS$FGEDRIVER.EXE - [SYS$LDR]SYS$PGADRIVER.EXE 5.2.11.2 CLDs, and QARs reporting this problem: 5.2.11.2.1 CLD(s) None. 5.2.11.2.2 QAR(s) None. 5.2.11.3 Problem Analysis: See problem description. 5.2.11.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 5.2.11.5 Work-arounds: None. 5.2.12 Multipath Scalar Disk Hung in Mount Verification 5.2.12.1 Problem Description: If cluster quorum is lost within a few seconds of powering down a fibre channel switch, a multipath scalar disk volume may hang in mount verification. Necessary conditions for the problem to occur are: o A fibre channel switch is powered down o The powered down fibre channel switch is connected to a fibre channel host bus adapter (HBA) that is used for the primary path to some disk device Page 13 o The node loses cluster quorum within 6 seconds of the power down of the fibre channel switch (the loss of quorum could be caused by temporary loss of access to a quorum disk via the failed switch, or because of some other completely unrelated fault) o The node is an SMP system and the HBA connected to the powered down switch has a preferred CPU other than the primary CPU. If all these conditions apply, the affected disk devices remain hung in mount verification and will not automatically switch to any available alternate path via some other HBA. Moreover, even if the fibre channel switch is powered back up, the affected devices will remain hung in mount verification. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE 5.2.12.2 CLDs, and QARs reporting this problem: 5.2.12.2.1 CLD(s) 70-3-8657,QXCM1000316902 5.2.12.2.2 QAR(s) None. 5.2.12.3 Problem Analysis: See problem description. 5.2.12.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 5.2.12.5 Work-arounds: None. Page 14 5.2.13 5.2.13.1 Problem Description: A process can hang in RWAST state with a channel assigned to a SYS$DKDRIVER disk (DK* or $1$DGA*). One UCB of the device will have a KPB stuck on its UCB$Q_DK_DRAIN_LIST, but there will be no UCB$L_CLASS_BUSY bits set with the possible exception of bit #0. UCB$Q_DK_IRP_LIST will be empty, as will UCB$Q_DK_FP_IRP_LIST. Other I/Os will be able to pass this tuck I/O as long as they do not have to perform a drain first. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE 5.2.13.2 CLDs, and QARs reporting this problem: 5.2.13.2.1 CLD(s) None. 5.2.13.2.2 QAR(s) None. 5.2.13.3 Problem Analysis: A tagged request with its own autosense buffer was allowed to complete after an untagged request or one without its own autosense buffer had been issued and put on the drain queue. The completing request saw the UCB$M_CB_DIAGNOSE bit in UCB$L_CLASS_BUSY set, assumed that it was set by it, and so cleared it. Later, when it ran through COMPLETE_IO, the drain queue was not checked because there were no UCB$L_CLASS_BUSY bits set. 5.2.13.4 Release Version of OpenVMS that will contain this change: Next release of OpenVMS for Integrity Servers after V8.3 5.2.13.5 Work-arounds: None. Page 15 6 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$DKDRIVER.EXE (new image) Image Identification Information image name: "SYS$DKDRIVER" image file identification: "X-9" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:00.42 linker identification: "A13-03" Overall Image Checksum: 1811738148 o [SYS$LDR]SYS$FGEDRIVER.EXE (new image) Image Identification Information image name: "SYS$FGEDRIVER" image file identification: "X-70A4A42" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:26.04 linker identification: "A13-03" Overall Image Checksum: 4089500969 o [SYS$LDR]SYS$GKDRIVER.EXE (new image) Image Identification Information image name: "SYS$GKDRIVER" image file identification: "X-63" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:04.15 linker identification: "A13-03" Overall Image Checksum: 2683676332 o [SYS$LDR]SYS$MKDRIVER.EXE (new image) Image Identification Information image name: "SYS$MKDRIVER" image file identification: "X-14" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:02.95 linker identification: "A13-03" Overall Image Checksum: 3429654892 o [SYS$LDR]SYS$PGADRIVER.EXE (new image) Image Identification Information image name: "SYS$PGADRIVER" image file identification: "X-93" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:21.44 linker identification: "A13-03" Overall Image Checksum: 2565674082 Page 16 o [SYS$LDR]SYS$PKMDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKMDRIVER" image file identification: "X-88A3" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:19.93 linker identification: "A13-03" Overall Image Checksum: 2404876130 o [SYS$LDR]SYS$PKRDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKRDRIVER" image file identification: "X-36" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:16.99 linker identification: "A13-03" Overall Image Checksum: 2349869768 o [SYS$LDR]SYS$PKWDRIVER.EXE (new image) Image Identification Information image name: "SYS$PKWDRIVER" image file identification: "X-43" image file build identification: "XBCA-0080070020" link date/time: 27-MAR-2007 21:26:17.92 linker identification: "A13-03" Overall Image Checksum: 2731255545 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. Page 17 o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. 7.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS83A_FIBRE_SCSI-V0100.ZIPEXE 7.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS83A_FIBRE_SCSI[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE Page 18 o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=DEC/BASE=AXPVMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS83A_FIBRE_SCSI-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS83A_FIBRE_SCSI/PRODUCER=DEC/BASE=AXPVMS/VER=V1.0" $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2007 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express Page 19 limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. DISCLAIMER OF WARRANTY AND LIMITATION OF LIABILITY THIS PATCH IS PROVIDED AS IS, WITHOUT WARRANTY OF ANY KIND. ALL EXPRESS OR IMPLIED CONDITIONS, REPRESENTATIONS AND WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR PARTICULAR PURPOSE, OR NON-INFRINGEMENT, ARE HEREBY EXCLUDED TO THE EXTENT PERMITTED BY APPLICABLE LAW. IN NO EVENT WILL HP BE LIABLE FOR ANY LOST REVENUE OR PROFIT, OR FOR SPECIAL, INDIRECT, CONSEQUENTIAL, INCIDENTAL OR PUNITIVE DAMAGES, HOWEVER CAUSED AND REGARDLESS OF THE THEORY OF LIABILITY, WITH RESPECT TO ANY PATCH MADE AVAILABLE HERE OR TO THE USE OF SUCH PATCH.