**************************** ECO SUMMARY INFORMATION **************************** Kit Name: VAXDRIV02_073.A Kit Applies To: OpenVMS VAX V7.2 Approximate Kit Size: 504 blocks Installation Rating: INSTALL_1 Reboot Required: Yes - rolling reboot Superseded Kits: VAXDRIV03_072 Mandatory Kit Dependencies: None Optional Kit Dependencies: None VAXDRIV02_073.A-DCX_VAXEXE Checksum: 533682766 ======================================================================= Hewlett-Packard OpenVMS ECO Cover Letter ======================================================================= ECO NUMBER: VAXDRIV03_072 PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM V7.2 1 KIT NAME: VAXDRIV03_072 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_1 : To be installed by all customers. This 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) 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 VAX V7.2 2.4 New functionality or new hardware support provided: No. 3 KITS SUPERSEDED BY THIS KIT: VAXDRIV02_072 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VAXUPDATE01_072 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]DUDRIVER.EXE (new image) Image Identification Information image name: "DUDRIVER" image file identification: "X-115" link date/time: 11-JUL-2003 15:20:05.49 linker identification: "V11-38" Overall Image Checksum: EEC7A45B o [SYS$LDR]PEDRIVER.EXE (new image) Image Identification Information image name: "PEDRIVER" image file identification: "VMS-10" link date/time: 11-JUL-2003 15:20:17.10 linker identification: "V11-38" Overall Image Checksum: F07C8230 o [SYS$LDR]PKBDRIVER.EXE (new image) Image Identification Information image name: "PKBDRIVER" image file identification: "X-45" link date/time: 11-JUL-2003 15:20:35.61 linker identification: "V11-38" Overall Image Checksum: 9D7C0F3F o [SYS$LDR]PKCDRIVER.EXE (new image) Image Identification Information image name: "PKCDRIVER" image file identification: "X-45" link date/time: 11-JUL-2003 15:20:33.44 linker identification: "V11-38" Overall Image Checksum: 78749405 o [SYS$LDR]PKRDRIVER.EXE (new image) Image Identification Information image name: "PKRDRIVER" Page 3 image file identification: "X-45" link date/time: 11-JUL-2003 15:20:34.59 linker identification: "V11-38" Overall Image Checksum: E0E5DEC8 o [SYS$LDR]TUDRIVER.EXE (new image) Image Identification Information image name: "TUDRIVER" image file identification: "X-81" link date/time: 11-JUL-2003 15:20:08.75 linker identification: "V11-38" Overall Image Checksum: A1815C43 6 PROBLEMS ADDRESSED IN THIS KIT 6.1 New problems addressed in the VAXDRIV03_072 kit 6.1.1 DGA device identified as snapshot device 6.1.1.1 Problem Description: The output of SHOW DEV/FULL for a DGA device identifies the device as a snapshot device. With this fix the device is properly identified as an HSG80 device. Images Affected: - [SYS$LDR]DUDRIVER.EXE 6.1.1.2 CLDs, and QARs reporting this problem: 6.1.1.3 CLD(s) None. 6.1.1.4 QAR(s) 75-45-359 6.1.1.5 Problem Analysis: A new entry to the MEDIA_ID to Device Type Conversion Table was needed. Implementing this change makes the table entry compatible with the one which currently exists for Alpha Page 4 6.1.1.6 Work-arounds: None. 6.1.2 Maningless error message when mounting or initializing a tapeunit 6.1.2.1 Problem Description: When mounting or initializing a tapeunit with a density that the unit can not handle, a misleading error message is generated. For example: $ mount/for/den=800 $1$MUA7: test %MOUNT-F-BUGCHECK, internal consistency failure This error does not indicate to the user issuing the command what the problem is. Images Affected: - [SYS$LDR]TUDRIVER.EXE 6.1.2.2 CLDs, and QARs reporting this problem: 6.1.2.3 CLD(s) None. 6.1.2.4 QAR(s) 75-45-1967 6.1.2.5 Problem Analysis: This is a sort of 'catch all' error message returned by TUDRIVER when a setmode command is rejected by the controller receiving the command. Rather than use SS$_IVDENS, the SS$_DRVERR error status will be used. SS$_IVDENS should not be returned as there may be more causes for the error. 6.1.2.6 Work-arounds: None. Page 5 6.1.3 Cluster nodes crash after another node is shutdown or crashes. 6.1.3.1 Problem Description: In a cluster, when one or more nodes is shut down or crashes, the remaining nodes crash with a VAXPORT crash in PEdriver routine PEM$PCI_GET_DFQ. Images Affected: - [SYS$LDR]PEDRIVER.EXE 6.1.3.2 CLDs, and QARs reporting this problem: 6.1.3.3 CLD(s) 70-3-5572, CFS.89636 6.1.3.4 QAR(s) None. 6.1.3.5 Problem Analysis: The PEM$PCI_GET_DFQ routine assumes that lower layers have verified that the port's DFREEQ contains at least one buffer when it is called. The one code path handling PEdriver BYE messages failed to check the datagram freeq empty flag before calling up to process the packet. 6.1.3.6 Work-arounds: None. 6.1.4 I/O's to a device hang after an error condition occurs. 6.1.4.1 Problem Description: I/O's to a device hang after an error condition occurs. A forced crash must be issued. Images Affected: - [SYS$LDR]PKBDRIVER.EXE - [SYS$LDR]PKCDRIVER.EXE - [SYS$LDR]PKRDRIVER.EXE Page 6 6.1.4.2 CLDs, and QARs reporting this problem: 6.1.4.3 CLD(s) CFS.85039 6.1.4.4 QAR(s) None. 6.1.4.5 Problem Analysis: When an error condition occurs, the QUEUE_FROZEN bit is set. If any SCDRPs timeout before the error condition is resolved, those SCDRPs are given more time to complete. When the SCDRPs are timed out, the DSCN bit is cleared and the TMODSCN bit is set in the SCDRP's CNX_STS. When the SCDRPs are given more time, as a result of the QUEUE_FROZEN bit being set, the TMODSCN bit is cleared and the DSCN bit is set in the SCDT$L_STS. Because the TMODSCN bit is still set for these SCDRPs in the SCDRP's CNX_STS, the time out code ignores these SCDRPs forever. Because the QUEUE_FROZEN bit is set in the SCDT, no further I/O's are queued to this connection and the system hangs until a forced crash is issued. 6.1.4.6 Work-arounds: None. 6.1.5 System hang or crash after tapeunit failover 6.1.5.1 Problem Description: The system may hang after a tapeunit fails over to a second controller. Another symptom may be a CPUSPINWAIT crash on an SMP system. The hang occurs at routine DUTU$MOVE_IODB when the code attempts 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 Failing PC: FFFFFFFF.8007A384 SMP$TIMEOUT_C+00064 Failing PS: 28000000.00000804 Module: SYSTEM_SYNCHRONIZATION (Link Date/Time: 28-MAY-1999 23:39: Offset: 00000384 Page 7 Stack Pointers: KSP = FFFFFFFF.F5D33E28 ESP = FFFFFFFF.F5D35000 SSP = FFFFFFFF.F5D31000 USP = FFFFFFFF.F5D31000 Failing Instruction: SMP$TIMEOUT_C+00064: BUGCHK Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE 6.1.5.2 CLDs, and QARs reporting this problem: 6.1.5.3 CLD(s) CFS.71855, CFS.77429, CFS.86456, CFS.89658, CFS.90050 6.1.5.4 QAR(s) None. 6.1.5.5 Problem Analysis: UTU$LINK_UCB2CDDB can, under certain circumstances, be called to link a UCB into the CDDB's chain when that UCB is already in the chain. The way it is currently handled causes the chain to be corrupted, i.e. when finished, UCB$L_CDDB_LINK will point to the UCB itself causing problems later on. 6.1.5.6 Work-arounds: None. 6.1.6 System can crash, during boot, with an INVEXCEPTN bugcheck at $RELEASEL+00011 from pkcdriver+04858. 6.1.6.1 Problem Description: If the system parameter MULTIPROCESSING is set to 2, the system can crash, during boot, with an INVEXCEPTN bugcheck at $RELEASEL+00011 from pkcdriver+04858. Images Affected: Page 8 - [SYS$LDR]PKBDRIVER.EXE - [SYS$LDR]PKCDRIVER.EXE - [SYS$LDR]PKRDRIVER.EXE 6.1.6.2 CLDs, and QARs reporting this problem: 6.1.6.3 CLD(s) CFS.94500 6.1.6.4 QAR(s) None. 6.1.6.5 Problem Analysis: A field was changed from scdrp to scdt without adapting the register used as an index. Thus a bit was set in the wrong data structure. 6.1.6.6 Work-arounds: None. 6.1.7 Access to certain drives can hang, SHADDETINCON bugcheck. 6.1.7.1 Problem Description: o Upon a connection failure, access to certain drives can hang, with an IRP to DUDRIVER never being returned to an application. This hang can spread from a single process to systemwide as other processes back up behind lock requests. Investigation shows the process' IRP is not found in the usual places in DUDRIVER (CDDB active queue, restart queue, UCB pending queue etc.). In other words it is "lost". o If Shadowing is involved on a hung drive, the system will crash with a SHADDETINCON bugcheck. Investigation shows an I/O (IRP) has been pending for MVTIMEOUT seconds (1 hour) and the shadowing IRP is "lost", as described above. Page 9 Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE 6.1.7.2 CLDs, and QARs reporting this problem: 6.1.7.3 CLD(s) CFS.92106, CFS.95877 6.1.7.4 QAR(s) None. 6.1.7.5 Problem Analysis: See Problem Description. 6.1.7.6 Work-arounds: None. 6.1.8 System can crash with an INVEXCEPN bugcheck at DUDRIVER+3F07 6.1.8.1 Problem Description: The system can crash with an INVEXCEPN bugcheck at DUDRIVER+3F07, MOVL 14(R4),R4 with R4=0. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE 6.1.8.2 CLDs, and QARs reporting this problem: 6.1.8.3 CLD(s) CFS.98583 Page 10 6.1.8.4 QAR(s) None. 6.1.8.5 Problem Analysis: See problem Description. 6.1.8.6 Work-arounds: None. 7 PROBLEMS ADDRESSED IN VAXDRIV02_072 KIT o INIT/DENSITY=XXX does not switch the density of the TSZ07 tape drive. This can happen if the following conditions occur: 1. A TSZ07 tape drive is locally connected to a SCSI adapter and driven by MKDRIVER. 2. The tape drive is TMSCP served to the clients. 3. The tape has been previously initialized to a density of 6250. If the INIT command issued specifies a density of 1600, the command will not fail, but the requested density is not honored. The tape remains at a density of 6250. Images Affected: - [SYS$LDR]TUDRIVER.EXE o A MOUNT command to a TZ8X drive can hang or fail with a "Volume not software enabled" error. This error occurs when the tape loaded is a COMPACT III tape that has previously been initialized at TK87 compacted density. Images Affected: - [SYS$LDR]TUDRIVER.EXE o The errorlog contains a bogus status when an I/O times out. It should log an SS$_TIMEOUT error for a DU/TU timeout. Images Affected: Page 11 - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o In certain cases DUDRIVER attempts to use the wrong alloclass of a disk, particularly satellite nodes when booting. This causes problems when attempting to access an MSCP served disk with the same allocation class as the client but a different allocation class from the server. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o A tape error can cause an INVEXCEPTN system crash. Crash Dump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.800AC2C0 MNTVER_STD$GET_CKSUM_BUF_C+001D0 Failing PS: 10000000.00000804 Module: IO_ROUTINES Offset: 000202C0 Images Affected: - [SYS$LDR]TUDRIVER.EXE o Occasionally, undetected data corruption can occur during a cluster failover event, port crash, or mount verification. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o A tape device hangs following a MOUNT-F-SERIOUSEXCP, 'Serious exception detected by TMSCP Controller' error. Images Affected: - [SYS$LDR]TUDRIVER.EXE Page 12 o A system can crash with an INVEXCEPTN in SYS$DUDRIVER bugcheck. See the partial crash dump summary below: Crash Dump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.80344454 SYS$DUDRIVER_NPRO+10454 Failing PS: 18000000.00000804 Module: SYS$DUDRIVER Offset: 00010454 Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o A system can crash with an INVEXCEPTN: DUDRIVER DUTU$CREATE_CDDB DDB$ DOUBLE DEALLOCATION bugcheck. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o When initializing a TZ tape unit, the INITIALIZE command could fail with a %INIT-F-DRVERR error, which causes an entry to be made in the errorlog. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER.EXE o If a tape, served by an V7.2-1 Alpha system, is mounted on a VAX V7.2 system with the /MEDIA_FORMAT=COMPACTION option, compaction may not be enabled. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER o Backup to a bad tape may result in a hung I/O request. Page 13 Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER o Compaction does not function properly on VAX clients of Alpha-served Fibre tapes. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER o Disk I/O appears to hang or get dropped. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER o A SHADDETINCON bugcheck occurs when a shadowing I/O hangs. Images Affected: - [SYS$LDR]DUDRIVER.EXE - [SYS$LDR]TUDRIVER 8 INSTALLATION INSTRUCTIONS: 8.1 Installation Command Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXDRIV03_072 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. 9 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. Page 14 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.