ECO NUMBER: VMS722_DRIVER-V0300 PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM V7.2-2 COVER LETTER 1 KIT NAME: VMS722_DRIVER-V0300 2 KITS SUPERSEDED BY THIS KIT: VMS722_DRIVER-V0200 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: VMS722_UPDATE-V0100 3.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, 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-2 4.2 Files patched or replaced: o [SYS$LDR]SYS$DUDRIVER.EXE (new image) o [SYS$LDR]SYS$PBDRIVER.EXE (new image) o [SYS$LDR]SYS$PEDRIVER.EXE (new image) o [SYS$LDR]SYS$TUDRIVER.EXE (new image) 5 PROBLEMS ADDRESSED IN VMS722_DRIVER-V0300 KIT o After applying the VMS722_DRIVER-V0200 ECO kit, the system may crash with an INVEXCEPTN Bugcheck SHWCLSTR+71234. Crashdump summary information: ------------------------------ -- COVER LETTER -- Page 2 14 October 2002 Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: SHC_COLLECT Current Image: DSA1:[SYS4.SYSCOMMON.] [SYSEXE]SHWCLSTR.EXE Failing PC: 00000000.00061234 SHWCLSTR+71234 Failing PS: 0C000000.00001F03 Module: SHWCLSTR Offset: 00071234 Images Affected: - [SYS$LDR]SYS$PBDRIVER.EXE - [SYS$LDR]SYS$PEDRIVER.EXE 6 PROBLEMS ADDRESSED IN VMS722_DRIVER-V0200 KIT o If DUTU$POLL_FOR_UNITS encounters an error, it does not return an ILLCDTST error. Rather, it returns to the caller's caller, which hangs the thread and stalls I/O. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE o An ACCVIO occurs when using the PREFER.MAR routine with a /FORCE qualifier. For example: $ PREFER $1$DUA15: /HOST=HSC000 /FORCE %SYSTEM-F-ACCVIO, access violation, reason mask=00, virtual address=0000000C, PC =0000000C, PSL=0000000F If the command is executed without the /FORCE qualifier, no ACCVIO occurs: $ PREFER $1$DUA15: /HOST=HSC000 Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE -- COVER LETTER -- Page 3 14 October 2002 o When performing multi-volume Backup (and various other Backup operations involving label processing) with generic SCSI tapes, compaction status gets turned off. Images Affected: - [SYS$LDR]SYS$TUDRIVER.EXE o Add support to allow the use of the SDLT 320 tapedrive with compaction. Images Affected: - [SYS$LDR]SYS$TUDRIVER.EXE o VAXPORT crash in PEdriver routine PEM$PCI_GET_DFQ when one or more other nodes crashes, is shutdown or rebooted. Crashdump Summary Information: ------------------------------ Bugcheck Type: VAXPORT, Fatal error detected by VAX port driver Current Process: NULL Current Image: Failing PC: FFFFFFFF.F247850C SYS$PEDRIVER+1050C Failing PS: 18000000.00000804 Module: SYS$PEDRIVER (Link Date/Time: 5-AUG-2001 01:06:01.63) Offset: 0001050C Images Affected: - [SYS$LDR]SYS$PEDRIVER.EXE o The system may hang after a tapeunit did a failover to a second controller. Another symptom may be a CPUSPINWAIT crash on a SMP system. The hang occurs at routine DUTU$MOVE_IODB when we attempt to follow a chain of UCB's via the field UCB$L_CDDB_LINK while the field points to the UCB itself. Normally the last field in the chain of UCB's should be zero. Crashdump Summary Information: ------------------------------ Bugcheck Type: CPUSPINWAIT, CPU spinwait timer expired Current Process: BATCH_1006249 Current Image: DSA1010:[RUN]GEM.EXE Failing PC: FFFFFFFF.80088384 SMP$TIMEOUT_C+00064 Failing PS: 18000000.00000803 Module: SYSTEM_SYNCHRONIZATION_MIN (Link Date/Time:22-MAR-2001 01:01:40.01) Offset: 00000384 -- COVER LETTER -- Page 4 14 October 2002 Images Affected: - [SYS$LDR]SYS$TUDRIVER.EXE - [SYS$LDR]SYS$DUDRIVER.EXE o SHOW CLUSTER and SDA SHOW CONNECTIONS can correctly report up to 8 SMCI ports. The reason for this is that, PBDRIVER uses a multiport scheme to handle its connections. In other words, UCB unit numbers are coupled with the galaxy instance number, making unit numbers greater than the standard ZERO as in traditional SCS port drivers. SCS reports the port name in the PB field PB$T_LPORT_NAME (format PBx0) which is only 4 bytes in length. In all cases, the unit number is set to zero. This is incorrect for SMCI ports. Images Affected: - [SYS$LDR]SYS$PBDRIVER.EXE o In routine DU$INSERT_RESTARTQ, certain CDRPS (MVIRP, shadowing) were being posted with DEVOFFLINE instead of being queued to the restart queue. Many of these CDRPs had mapping registers active, and posting them unmapped them while still active. This caused a variety of symptoms, such as IOMACHINECHECKS, unrecognized SCA messages and INCONSTATE errors. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE 7 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. -- COVER LETTER -- Page 5 14 October 2002 8 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 VMS722_DRIVER /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. 8.1 Special Installation Instructions: 8.1.1 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. /PROD=DEC/BASE=AXPVMS/VER=V3.0 - De-assign the logicals assigned For example, a sample command file to install the VMS722_DRIVER-V0300 kit would be: $ $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $! $ PROD INSTALL VMS722_DRIVER/PROD=DEC/BASE=AXPVMS/VER=V3.0 $! -- COVER LETTER -- Page 6 14 October 2002 $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit Copyright (c) Compaq Computer Company, 2002 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. 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. Confidential computer software. Valid license from COMPAQ are 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.