ECO NUMBER: VMS721_SYS-V1000 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-1 COVER LETTER 1 KIT NAME: VMS721_SYS-V1000. 2 KITS SUPERSEDED BY THIS KIT: VMS721_SYS-V0900. 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: - VMS721_PCSI-V0100. - VMS721_UPDATE-V0200. 3.2 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None. 4 KIT DESCRIPTION: 4.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS Alpha V7.2-1. 4.2 Files patched or replaced: o [SYSEXE]APB.EXE (new image) o [SYSEXE]DEBUG_APB.EXE (new image) o [SYSLIB]IOGEN$SHARE.EXE (new image) o [SYSEXE]SYSMAN.EXE (new image) o [SYSLIB]SDA$SHARE.EXE (new image) o [SYSEXE]SYSBOOT.EXE (new image) o [SYSEXE]SYSGEN.EXE (new image) -- COVER LETTER -- Page 2 12 June 2001 o [SYS$LDR]MESSAGE_ROUTINES.EXE (new image) o [SYS$LDR]EXCEPTION.EXE (new image) o [SYS$LDR]EXCEPTION_MON.EXE (new image) o [SYS$LDR]IMAGE_MANAGEMENT.EXE (new image) o [SYS$LDR]IO_ROUTINES.EXE (new image) o [SYS$LDR]IO_ROUTINES_MON.EXE (new image) o [SYS$LDR]LOCKING.EXE (new image) o [SYS$LDR]LOGICAL_NAMES.EXE (new image) o [SYS$LDR]MULTIPATH.EXE (new image) o [SYS$LDR]MULTIPATH_MON.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT.EXE (new image) o [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE (new image) o [SYS$LDR]SECURITY.EXE (new image) o [SYS$LDR]SECURITY_MON.EXE (new image) o [SYS$LDR]SYS$BASE_IMAGE.EXE (new image) o [SYS$LDR]SYS$CLUSTER.EXE (new image) o [SYS$LDR]SYS$VCC.EXE (new image) o [SYS$LDR]SYS$VCC_MON.EXE (new image) o [SYS$LDR]SYS$VM.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES.EXE (new image) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE (new image) o [SYS$LDR]MESSAGE_ROUTINES.STB (new file) o [SYS$LDR]EXCEPTION.STB (new file) o [SYS$LDR]EXCEPTION_MON.STB (new file) o [SYS$LDR]IMAGE_MANAGEMENT.STB (new file) o [SYS$LDR]IO_ROUTINES.STB (new file) o [SYS$LDR]IO_ROUTINES_MON.STB (new file) -- COVER LETTER -- Page 3 12 June 2001 o [SYS$LDR]LOCKING.STB (new file) o [SYS$LDR]LOGICAL_NAMES.STB (new file) o [SYS$LDR]MULTIPATH.STB (new file) o [SYS$LDR]MULTIPATH_MON.STB (new file) o [SYS$LDR]IODEF.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT.STB (new file) o [SYS$LDR]PROCESS_MANAGEMENT_MON.STB (new file) o [SYS$LDR]SECURITY.STB (new file) o [SYS$LDR]SECURITY_MON.STB (new file) o [SYSEXE]SYS$CONFIG.DAT (new file) o [SYS$LDR]SYS$VCC.STB (new file) o [SYS$LDR]SYS$VCC_MON.STB (new file) o [SYS$LDR]SYS$VM.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES.STB (new file) o [SYS$LDR]SYSTEM_PRIMITIVES_MIN.STB (new file) 5 PROBLEMS ADDRESSED IN VMS721_SYS-V1000 KIT o The use of HSM on a Multipath device results in a system crash at HSDRIVER+02AF8. This kit enables the use of Hierarchical Storage Manager (HSM) on Multipath devices. Images Affected: - [SYS$LDR]IODEF.STB - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB o A system crashes with a DOUBLEDEALO bugcheck at EXE$DEALLOCATE_C+00108 in $BRKTHRU when trying to deallocate P1 pool that has already been deallocated. See crash dump summary information below: -- COVER LETTER -- Page 4 12 June 2001 Crash Dump Summary ------------------ Bugcheck Type: DOUBLDEALO, Double deallocation of memory block Current Process: CANDOUGF_1 Current Image: $1$DUA0:[SYS1.SYSCOMMON.][SYSEXE]MAIL.EXE Failing PC: FFFFFFFF.80048A28 EXE$DEALLOCATE_C+00108 Failing PS: 20000000.00000200 Module: SYSTEM_PRIMITIVES_MIN (Link Date/Time: 13-SEP-2000 06:34:17.45) Offset: 00012A28 Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB - [SYS$LDR]SYS$CLUSTER.EXE o If host-based volume shadowing is running when I/O transfers to SCSI disks stop, and the disk is a member of a shadow set, then a SHADDETINCON crash occurs. Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB o Under a heavy I/O load, where the processes DIOCNT is at zero, certain circumstances exist that allow DIOCNT to go from 0 to a negative value. Once this has occurred, it may be possible for an application to hang a process or system with an un-managable RWAST condition. Or, it may be possible for an application to absorb all of non-paged pool with IRPs. This can cause a system to crash with an INSF_NONPAGED, 'Insufficient non- paged pool' bugcheck in SYS$SHDRIVER. See the crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: INSF_NONPAGED, Insufficient nonpaged pool Current Process: NMD_CQS4 Current Image: $2$DUA100:[MARS.V32.][EXE]CI_CQS.EXE;3 Failing PC: FFFFFFFF.92F8A204 SYS$SHDRIVER+70204 Failing PS: 30000000.00000804 -- COVER LETTER -- Page 5 12 June 2001 Module: SYS$SHDRIVER (Link Date/Time: 24-JAN-2000 9:28:00.85) Offset: 00070204 Images Affected: - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB o A system can crash during boot with a SHADDETINCON bugcheck at SYS$SHDRIVER+7580C in module SHD_THREADS, routine SHTD$ENQ_LOCK_BLOCK. See crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: SHADDETINCON, SHADOWING detects inconsistent state Current Process: NULL Current Image: Failing PC: FFFFFFFF.8047F80C SYS$SHDRIVER+7580C Failing PS: 04000000.00000804 Module: SYS$SHDRIVER (Link Date/Time: 24-OCT-2000 15:06:45.56) Offset: 0007580C Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB - [SYS$LDR]IODEF.STB o Pool corruption, caused by double deallocation of an IRP, can occur when the current path to a $1$GGAn: or $a$GKAn: device is a secondary path and a polling I/O arrives while there is an active IRP on that path. Images Affected: - [SYS$LDR]MULTIPATH.EXE -- COVER LETTER -- Page 6 12 June 2001 - [SYS$LDR]MULTIPATH.STB - [SYS$LDR]MULTIPATH_MON.EXE - [SYS$LDR]MULTIPATH_MON.STB - [SYS$LDR]IODEF.STB o When mounting FibreChannel shadowsets, a system can crash with an INVEXCEPTN, 'Exception while above ASTDEL' bugcheck at MULTIPATH_MON+3B2C, routine MPDEV$MAP_STATUS_SHDSET. See the crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.8038FB2C MPDEV$MAP_STATUS_SHDSET_C+0005C Failing PS: 10000000.00000804 Module: MULTIPATH_MON (Link Date/Time: 9-FEB-2001 23:41:29.09) Offset: 00003B2C Images Affected: - [SYS$LDR]MULTIPATH.EXE - [SYS$LDR]MULTIPATH.STB o The system can crash with an SSRVEXCEPT bugcheck at LOCKING+019CC on an LDQ_U R11,(R26) instruction while processing a resource domain. See crash dump summary below: Crashdump Summary Information: ------------------------------ Bugcheck Type: SSRVEXCEPT, Unexpected system service exception Current Process: BATCH_3084 Current Image: DSA509:[SSEXE.DP]SPCUSERMAINT.EXE;44 Failing PC: FFFFFFFF.801619CC LOCKING+019CC Failing PS: 38000000.00000203 Module: LOCKING Link Date/Time: 29-MAR-2000 00:58:34.67 Offset: 000019CC Images Affected: - [SYS$LDR]LOCKING.EXE -- COVER LETTER -- Page 7 12 June 2001 - [SYS$LDR]LOCKING.STB o Processes hang in Record Management Services (RMS) during $GET and no apparent locking conflict can be detected. There are cases where the status does not get updated after granting a byte range lock. Images Affected: - [SYS$LDR]LOCKING.EXE - [SYS$LDR]LOCKING.STB o With multithreaded processes, systems have been seen to hang. Specifically, an AST critical to the file system causes file system I/O operations to hang for all processes. It would be appropriate to suspect this problem is occurring on a system with otherwise unexplained system or application hangs, if the system has multiple CPUs and any multi-kernel-threaded applications. This includes essentially any Java applications. Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o An ACCVIO occurs in MESSAGE_ROUTINES near "ALTNUMTIM." There are several ways in which this problem may occur: - A process ACCVIOs near the symbol EXE$ALTNUMTIM. - ORA-482 crashes on Oracle 8.1.6 OPS. - An Oracle process exits with the status code 0C, which is an ACCVIO. Since Oracle processes run as detached processes, this status code would appear in the accounting log. Images Affected: - [SYS$LDR]MESSAGE_ROUTINES.EXE - [SYS$LDR]MESSAGE_ROUTINES.STB -- COVER LETTER -- Page 8 12 June 2001 o The GETTIMEOFDAY() CRTL function returns an error in ORACLE Parallel Server Version 8.1.6. This can occur in several ways: - The GETTIMEOFDAY() function returns status code 103DFE0. - The VMS user mode system services returns unexpected status codes, including C signal status code, SS$_BREAK, SS$_IMGDMP or SS$_DEBUG. - An ORA-7211 Oracle 8.1.6 OPS crash could occur. - A severe performance slowdown on Oracle 8.1.6 or 8.1.7 OPS could occur. - Oracle 8.1.6 or 8.1.7 OPS might hang. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o A process exits with an error status, but without a process dump. The image dump flag is set for the process. There are several ways this can be seen: 1. Processes don't dump when they exit while executing an exception handler. The process must have the image dump flag set. 2. Oracle8 OPS background processes do not dump when they hit an error. The processes must have the image dump flag set. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o The kill() sys$sigprc CRTL functions return the error SS$_SUSPENDED when the process is neither suspended nor waiting on a resource. The processes is simply waiting on a mutex or is in the transient RWSCS state. This leads to ORA-482 crashes on Oracle 8.1.6 or 8.1.7 OPS could also occur. -- COVER LETTER -- Page 9 12 June 2001 Images Affected: - [SYS$LDR]PROCESS_MANAGEMENT.EXE - [SYS$LDR]PROCESS_MANAGEMENT.STB - [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE - [SYS$LDR]PROCESS_MANAGEMENT_MON.STB o The user stack can become corrupt through repeated issuances of the DEBUG command. The following sequence of commands illustrates the problem: $LINK/DEBUG FOO (where FOO simply executes an infinite loop) $RUN FOO DBG> go DBG> CTRL/Y $DEBUG DBG> go DBG> CTRL/Y $DEBUG %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in DBGKREGISTERS\DBG$ GET_PD_FROM_FP %DEBUG-I-TRUNC64, address 0000000200000000 being truncated in DBGKREGISTERS\DBG$ GET_PD_FROM_FP DBG> g %DEBUG-I-BADSTACKPATCH1, Corrupt stack detected...attempting patch STQ R27,(SP) %DEBUG-W-NORESUME, unable to resume execution, stack or PC corrupted in %PROCESS_NUMBER 1 DBG> The user stack is now corrupt. Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o An Oracle Parallel Server can crash with an ORA-482 error. The PC is near a routine's prologue code and the FP has been set. R27 is stored on the stack after the FP is set and the process exits with an unhandled exception. -- COVER LETTER -- Page 10 12 June 2001 Images Affected: - [SYS$LDR]EXCEPTION.EXE - [SYS$LDR]EXCEPTION.STB - [SYS$LDR]EXCEPTION_MON.EXE - [SYS$LDR]EXCEPTION_MON.STB o A system can crash with An INCONSTATE bugcheck at SYS$VCC+0822C. Crashdump Summary Information: ------------------------------ Bugcheck Type: INCONSTATE, Inconsistent I/O data base Current Process: NULL Current Image: Failing PC: FFFFFFFF.801E822C SYS$VCC+0822C Failing PS: 08000000.00000804 Module: SYS$VCC (Link Date/Time: 18-MAY-2000 00:48:08.10) Offset: 0000822C This is not one of the conditions that the CVCB_CHKLK macro recognizes as temporary, so it bugchecks rather than retries the lock conversion. The restriction that fails in this case is the CVCB lock, which is already in PR mode. Images Affected: - [SYS$LDR]SYS$VCC.EXE - [SYS$LDR]SYS$VCC.STB - [SYS$LDR]SYS$VCC_MON.EXE - [SYS$LDR]SYS$VCC_MON.STB o Added the Adaptec Line of SCSI adapters. Images Affected: - [SYS.OBJ]IO_ROUTINES.EXE - [SYS.OBJ]IO_ROUTINES.STB - [SYS.OBJ]IO_ROUTINES_MON.EXE - [SYS.OBJ]IO_ROUTINES_MON.STB -- COVER LETTER -- Page 11 12 June 2001 o The system hangs with the AUDIT_SERVER process in RWMBX when Object_Server tries to write to its own mailbox. Images Affected: - [SYS$LDR]SECURITY.EXE - [SYS$LDR]SECURITY.STB - [SYS$LDR]SECURITY_MON.EXE - [SYS$LDR]SECURITY_MON.STB - [SYS$LDR]IO_ROUTINES.EXE - [SYS$LDR]IO_ROUTINES.STB - [SYS$LDR]IO_ROUTINES_MON.EXE - [SYS$LDR]IO_ROUTINES_MON.STB o Shadow sets with FibreChannel members fail to mount with MULTIPATH, resulting in MOUNTVERIFY error messages and member removals. Images Affected: - [SYS$LDR]MULTIPATH.EXE o The following fields have been added for the virtual unit and shadow set members in the output of an SDA SHO DEVICE DSA command: o Site Value o Timeout Value Each member will now display Read Cost, Site, SM Timeout. For example: OLD OUTPUT: ----------- $ analyze/SYS SDA> sho dev dsa64 DSA64 Generic_DK UCB: 817CD500 . . . I/O data structures ------------------- ----- Shadow Descriptor Block (SHAD) 817DA080 ----- -- COVER LETTER -- Page 12 12 June 2001 Virtual Unit status: 0001 normal Members 3 Act user IRPs 0 VU UCB 817CD500 Devices 3 SCB LBN 010F4627 Master FL 817DA3E4 Fcpy Targets 0 Generation Num 2C34A8FF Restart FL 817DA3EC Mcpy Targets 0 009FCC39 Last Read Index 0 Virtual Unit Id 00000000 Master Index 1 12610040 ----- SHAD Device summary for DSA64 ----- Device $1$DGA110 Index 0 Status 000000A0 src,valid UCB 816156C0 VCB 817DABC0 Unit Id. 10E1006E 00000001 Device $1$DGA210 Index 1 Status 000000A0 src,valid UCB 81615BC0 VCB 817DB540 Unit Id. 10E100D2 00000001 Device $64$DKA301 Index 2 Status 000000A0 src,valid UCB 81624540 VCB 8166E880 Unit Id. 1161012D 00000040 NEW OUTPUT ----------- $ analyze/SYS SDA> sho dev dsa64 DSA64 Generic_DK UCB: 81540000 . . . I/O data structures ------------------- --- Shadowing Descriptor Block (SHAD) 816EC440 --- Virtual Unit SCB Status: 0001 normal Total Devices 3 VU_UCB 81540000 Source Members 3 SCB LBN 010F4627 Act Copy Target 0 Generation 009FCC39 Act Merge Target 0 Number 2C34A8FF Last Read Index 1 VU Site Value 00000000 Master Mbr Index 1 VU Timeout Value 3600 Device $1$DGA110 Index 0 Status 000000A0 src,valid Read Cost 0000002A Site 00000000 SM Timeout 120 UCB 8153D440 VCB 8161F880 Device $1$DGA210 ... Master Member Index 1 Status 000000A0 src,valid Read Cost 0000002A Site 00000000 SM Timeout 120 UCB 81543800 VCB 8187CA40 Device $64$DKA301 Index 2 Status 000000A0 src,valid -- COVER LETTER -- Page 13 12 June 2001 Read Cost 0000002A Site 00000000 SM Timeout 120 UCB 81503700 VCB 8179D800 Images Affected: - [SYSLIB]SDA$SHARE.EXE 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: INSTALL_1 : To be installed by all customers. 7 INSTALLATION INSTRUCTIONS: 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 VMS721_SYS /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 This kit requires a system reboot. Compaq 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. (cİ 2001 Compaq Computer Corporation. COMPAQ, the Compaq logo, VAX, Alpha, VMS, and OpenVMS are registered in the U.S. Patent and Trademark Office. All other product names mentioned herein may be trademarks of their respective companies. -- COVER LETTER -- Page 14 12 June 2001 Confidential computer software. Valid license from Compaq 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. Compaq shall not 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 Compaq 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.