**************************** ECO SUMMARY INFORMATION **************************** Release Date: 10-OCT-2003 Kit Name: DEC-AXPVMS-VMS731_SYSLOA-V0100--4.PCSI Kit Applies To: OpenVMS ALPHA V7.3-1 Approximate Kit Size: 1424 blocks Installation Rating: INSTALL_2 Required Feature: OpenVMs Clusters Reboot Required: Yes - rolling reboot Superseded Kits: None Mandatory Kit Dependencies: VMS731_UPDATE-V0100 VMS731_PCSI-V0100 Optional Kit Dependencies: None VMS731_SYSLOA-V0100.PCSI-DCX_AXPEXE Checksum: 2075174373 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VMS731_SYSLOA-V0100 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.3-1 1 KIT NAME: VMS731_SYSLOA-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_2: To be installed by all customers using the following feature(s): - OpenVMs Clusters 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 V7.3-1 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: - VMS731_PCSI-V0100 - VMS731_UPDATE-V0100 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 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$CLUSTER.EXE (new image) Image Identification Information image name: "SYS$CLUSTER" image file identification: "X-3" image file build identification: "X9TD-0060030009" link date/time: 19-SEP-2003 17:06:38.16 linker identification: "A11-50" Image Checksum: 830880022 o [SYS$LDR]SYS$CLUSTER_MON.EXE (new image) Image Identification Information image name: "SYS$CLUSTER_MON" image file identification: "X-3" image file build identification: "X9TD-0060030009" link date/time: 19-SEP-2003 17:06:39.67 linker identification: "A11-50" Image Checksum: 2698182613 o [SYS$LDR]SYS$CLUSTER.STB (new file) o [SYS$LDR]SYS$CLUSTER_MON.STB (new file) 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VMS731_SYSLOA-V0100 kit 6.1.1 Undetected deadlocks and cluster hangs 6.1.1.1 Problem Description: The system can experience random application or system hangs. Undetected deadlocks are also possible. $GETLKI will return a zero PID for the blocking information Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE Page 3 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.3 CLD(s) None. 6.1.1.4 QAR(s) None. 6.1.1.5 Problem Analysis: The PID check was incorrectly using the process index instead of the IPID, hence this check always failed. Because of this, a zero EPID and TSKPID was sent across to the node mastering this lock and a process-owned lock suddenly turned into a system-owned lock. Tis is not a problem most of the time. But, if this lock happens to block another process or a deadlock search trips over this, the process to send the blocking AST or give the ss$_deadlock to cannot be found. The result will be that a process holding a lock is blocking other processes, which can result in application and or system hangs. Undetected deadlocks are also possible and $GETLKI will return a zero PID for the blocking info. 6.1.1.6 Work-arounds: None. 6.1.2 INVEXCEPTN bugcheck in SYS$CLUSTER 6.1.2.1 Problem Description: Under unlikely circumstances, the system may accidentally queue an internal thread of execution twice, resulting in a system crash with hard to diagnose symptoms. The likeliest result is an immediate INVEXCEPTN crash in SYS$CLUSTER or the fork dispatch code, but other symptoms are possible. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE Page 4 - [SYS$LDR]SYS$CLUSTER_MON.STB 6.1.2.2 CLDs, and QARs reporting this problem: 6.1.2.3 CLD(s) None. 6.1.2.4 QAR(s) 75-83-1167 6.1.2.5 Problem Analysis: See Problem Description 6.1.2.6 Work-arounds: None. 6.1.3 MONITOR DISK/ITEM=QUEUE_LENGTH shows queue lengths on disks with no I/O 6.1.3.1 Problem Description: A MONITOR DISK/ITEM=QUEUE_LENGTH command shows queue lengths on disks that have no IO activity, shown by MONITOR DISK and system load. The UCB$L_QLEN field is non zero. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE - [SYS$LDR]SYS$CLUSTER_MON.STB 6.1.3.2 CLDs, and QARs reporting this problem: Page 5 6.1.3.3 CLD(s) 70-3-6291,CFS.94807,70-3-6468,CFS.96009 6.1.3.4 QAR(s) None. 6.1.3.5 Problem Analysis: UCB$L_QLEN was being decremented without preserving atomicity in these modules. The fix is to make sure atomicity preserved around decrement. 6.1.3.6 Work-arounds: None. 6.1.4 EV6 machines can experience spurious crashes due to an INEXCEPTN bugcheck in SYS$CLUSTER 6.1.4.1 Problem Description: Some cluster nodes may experience spurious crashes due to an INEXCEPTN bugcheck in SYS$CLUSTER. The crashes usually occur in routines CNX$RCV_MSG, CNX$PROCESS_RCV_MSG, or CNX_STD$SEND_MSG_V2. These crashes are the result of a timing issue and only affect EV6 systems. Images Affected: - [SYS$LDR]SYS$CLUSTER.EXE - [SYS$LDR]SYS$CLUSTER.STB - [SYS$LDR]SYS$CLUSTER_MON.EXE - [SYS$LDR]SYS$CLUSTER_MON.STB 6.1.4.2 CLDs, and QARs reporting this problem: Page 6 6.1.4.3 CLD(s) 70-3-7241, 70-3-7244, 70-3-7298, 70-3-7308, 70-3-7324, 6.1.4.4 QAR(s) None. 6.1.4.5 Problem Analysis: This problem has been isolated to a hardware specific timing issue. This fix will solve the problem by working around this crash symptom without affecting other symptoms. 6.1.4.6 Work-arounds: None. 7 INSTALLATION INSTRUCTIONS: 7.1 Installation Command Install this kit with the {Installation Utility} utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS731_SYSLOA /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt 7.2 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 definitions and commands: - $ DEFINE/SYS NO_ASK$BACKUP TRUE - $ DEFINE/SYS NO_ASK$REBOOT TRUE - Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. Page 7 /PROD=DEC/BASE=AXPVMS/VER=V1.0 - De-assign the logicals assigned For example, a sample command file to install the VMS731_SYSLOA-V0100 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS731_SYS/PROD=DEC/BASE=AXPVMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2003 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 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 COMPAQ 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.