ECO NUMBER: ALPLAD05_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPLAD05_062 2 KITS SUPERSEDED BY THIS KIT: ALPLAD04_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: o ALPCLUSIO01_062 o ALPY2K02_062 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 V6.2, V6.2-1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYSEXE]ESS$LADCP.EXE (new image) o [SYSEXE]ESS$LASTCP.EXE (new image) o [SYS$LDR]SYS$DADDRIVER.EXE (new image) o [SYS$LDR]SYS$LADDRIVER.EXE (new image) o [SYS$LDR]SYS$LASTDRIVER.EXE (new image) o [SYS$LDR]SYS$MADDRIVER.EXE (new image) o [SYS$STARTUP]ESS$LAST_STARTUP.COM (new file) -- COVER LETTER -- Page 2 13 September 2000 o [SYS$STARTUP]ESS$STARTUP.COM (new file) 5 PROBLEMS ADDRESSED IN ALPLAD05_062 KIT o MOUNT/MEDI=COMPACT and BACKUP/MEDI=COMPACT commands did not enable compaction of a TLZ06. Images Affected: - [SYS$LDR]SYS$MADDRIVER.EXE o The system crashed with INVEXCEPTN at LASTDRIVER+03511. See the crash analysis below: SDA> SH CRASH System crash information ------------------------ Time of system crash: 17-MAR-1998 14:50:52.68 Version of system: OpenVMS (TM) VAX Version V7.1 System Version Major ID/Minor ID: 1/0 VAXcluster node: RAVENS, a VAX 6000-540 Crash CPU ID/Primary CPU ID: 01/01 Bitmask of CPUs active/available: 0000001E/0000001E ------------------------ CPU bugcheck codes: CPU 01 -- INVEXCEPTN, Exception while above ASTDEL or on interrupt stack 3 others -- CPUEXIT, Shutdown requested by another CPU Process currently executing on this CPU: BATCH_838 Current image file: DSA1:[SYSA.SYSCOMMON.][SYSEXE]SYSGEN.EXE Current IPL: 8 (decimal) CPU database address: 889D4000 MPB address: 8505CB40 CPU 01 Processor stack ---------------------- Current operating stack (INTERRUPT): 889D5D5C 7FFECC50 889D5D60 7FFED7D4 889D5D64 7FFE2BDC CTL$AG_CLIDATA+00180 889D5D68 00000000 889D5D6C 853B554A 889D5D70 889D5D74 889D5D74 832FF27F EXE$EXCEPTION+00047 889D5D78 04080009 SP => 889D5D7C 00000004 889D5D80 853B554A 889D5D84 FFFFFFFD RBF$C_LOG 889D5D88 00000000 -- COVER LETTER -- Page 3 13 September 2000 889D5D8C 853B55B6 889D5D90 00000001 889D5D94 00000005 889D5D98 0000000C 889D5D9C 00000000 889D5DA0 00000024 889D5DA4 855B7E11 LASTDRIVER+03511 889D5DA8 04080004 889D5DAC 855B4A34 LASTDRIVER+00134 889D5DA0 889D4210 889D5DB4 00000008 889D5DB8 7FFED930 CTL$GQ_PRCTERM_LISTHEAD . . . SDA> E/I LASTDRIVER+03511-40;40 . . . LASTDRIVER+034FE: MOVAB -20(FP),R7 LASTDRIVER+03502: MOVL 18(R7),R6 We have a "PIB" (perform.i/o block) LASTDRIVER+03506: BEQL LASTDRIVER+03527 LASTDRIVER+03508: DECB 11(R6) The value here is "0" LASTDRIVER+0350B: BNEQ LASTDRIVER+0351E LASTDRIVER+0350D: MOVL 20(R6),R0 LASTDRIVER+03511: MOVL 24(R0),R0 this produces our VA = 24 Images Affected: - [SYS$LDR]ESS$LASTDRIVER.EXE o If a system has multiple controllers and not all of the controllers are connected to the wire, a solicit command, such as: $ MC ESS$LADCP LADCP> SHO SERVICES/TAPE will time out and crash in MADDRIVER. Images Affected: - [SYS$LDR]SYS$MADDRIVER.EXE o If a tape is initialized on a TZ87 and then put on a TZ86, an attempt to re-initialize the tape on the TZ86 will be very slow. The TZ86 takes too much time to determine how to handle that tape. -- COVER LETTER -- Page 4 13 September 2000 Images Affected: - [SYS$LDR]SYS$MADDRIVER.EXE o SYS$MADDRIVER crashed the system. See a portion of the dumpfile below: MADDRIVER_SYSDUMP.DMP;1 185365/185370 17-JUN-1999 13:11:33.64 (R,RWED,R,RE) Crash Time: 17-JUN-1999 13:52:43.74 Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Node: ASDEV (Clustered) CPU Type: AlphaServer 1000A 4/266 VMS Version: V7.1-2 Current Process: PDEMBITSKY Current Image: $1$DKC0:[SYS0.SYSCOMMON.][SYSEXE]VMOUNT.EXE Failing PC: FFFFFFFF.85B2DF60 SYS$MADDRIVER+13F60 Failing PS: 00000000.00000801 Module: SYS$MADDRIVER Offset: 00013F60 Boot Time: 15-JUN-1999 17:01:50.00 System Uptime: 1 20:50:53.74 Crash/Primary CPU: 00/00 System/CPU Type: 1B02 Saved Processes: 34 Pagesize: 8 KByte (8192 bytes) Physical Memory: 256 MByte (32768 PFNs, contiguous memory) Dumpfile Pagelets: 185267 blocks Dump Flags: olddump,writecomp,errlogcomp,dump_style Dump Type: raw,selective EXE$GL_FLAGS: poolpging,init,bugdump Paging Files: 2 Pagefiles and 1 Swapfile installed . . . Failing Instruction: SYS$MADDRIVER+13F60: LDL R0,#XFFFE(R0) R0 = 00000000.0000003E failing vc = 3C (-2 off 3e) Images Affected: - [SYS$LDR]SYS$MADDRIVER.EXE o The system crashes with a UNXSIGNAL bugcheck when trying to create a directory or write a file to a large InfoServer partition. -- COVER LETTER -- Page 5 13 September 2000 Images Affected: - [SYS$LDR]SYS$DADDRIVER.EXE o During system shutdown a system can crash with an INVEXCEPTN bugcheck at LASTDRIVER+35FA. Images Affected: - [SYS$LDR]SYS$LASTDRIVER.EXE o After de-allocating non-paged pool, the driver did not clear the pointer to the structure that it deallocated. As a result, an INVEXCEPTN crash occurred due to stale structure pointers. Images Affected: - [SYS$LDR]SYS$MADDRIVER.EXE 6 PROBLEMS ADDRESSED IN ALPLAD04_062 KIT o ESS$STARTUP.COM and ESS$LAST_STARTUP.COM are missing from the ALPLAD03_062 kit. They are in the ALPLAD03_070 kit, which is superseded by ALPLAD03_062 for OpenVMS Alpha V6.2*. o If a system has multiple controllers and they are not all connected to the wire, then the following (sample) solicit command can time out and then crash in MADDRIVER: $ MC ESS$LADCP LADCP> SHO SERVICES/TAPE Image(s) Affected - [SYS$LDR]SYS$MADDRIVER.EXE o MOUNT/MEDIA=COMPACT DEV(x) and BACKUP/MEDIA=COMPACT do not handle density setting correctly. Hence, density is not being enabled. Image(s) Affected - [SYS$LDR]SYS$MADDRIVER.EXE o In a multi-processor environment, the service solicitation queues may be accessed by several processors. Since these queues are not synchronized correctly, they can get corrupted. -- COVER LETTER -- Page 6 13 September 2000 Thus, the system crashes with an INVEXCEPTN at around LASTDRIVER+3513 in routine LAST$TICK. Note: LAST should not be started on non-connected Ethernet controllers. Otherwise, problems with the LADCP> SHOW SERVICE command can occur. Image(s) Affected: - [SYS$LDR]SYS$LASTDRIVER.EXE o If a tape is initialized on a TZ87 and then put on a TZ86 with an attempt to re-initialize the tape, the TZ86 takes an excessive amount of time to determine how to handle the tape. Hence, it times out. Image(s) Affected: - [SYS$LDR]SYS$MADDRIVER.EXE o The BLISS compiler output an error message that NEWVAL is not initialized in routine LADCP_SET. Image(s) Affected: - [SYSEXE]ESS$LADCP.EXE 7 PROBLEMS ADDRESSED IN ALPLAD03_062 KIT o 1. LASTDRIVER crashes when it receives a run message in the circuit stalled state. 2. Typing a CTRL/Y at a certain instance could cause an IO$_PACKACK function to a MAD device to be canceled. The result could eventually be that the system crashes in I/O post processing. 3. LADCP BIND/UNIT=x will cause a duplicate UCB unit number to be generated if the unit number specified is greater then the seed unit number. This problem can happen for both DADDRIVER and MADDRIVER. o The system crashes in LTDRIVER when SSB is deleted prematurely while an UNLOAD is in progress. -- COVER LETTER -- Page 7 13 September 2000 o The LASTDRIVER image crashes when it receives an Advertisement (ADV) or Solicit (SOL) message with a negative message length. o In the past, BIND/TAPE/NOPERMANENT "tape_service" created a MADx device UCB that could be deleted once the UCB reference count went to zero. Problems occurred when the UCB was deleted due to the use of the /NOPERMANENT qualifier, that is multivolume BACKUP. Note: A MAD device is a tape device that is attached to an InfoServer. 8 PROBLEMS ADDRESSED IN ALPLAD03_070 KIT FOR OPENVMS ALPHA V6.2, V6.2 o Infoserver boots very slowly. 9 PROBLEMS ADDRESSED IN ALPLAD02_070 KIT FOR OPENVMS ALPHA V6.2-1H1 o The ALPLAD01_070 remedial kit did not install on systems running OpenVMS Alpha V6.2-1H1, as it should have. 10 PROBLEMS ADDRESSED IN ALPLAD01_070 KIT FOR OPENVMS ALPHA V6.2, V6.2 o Not waiting for "unit ready" caused system crashes in MADDRIVER and LASTDRIVER. o MADDRIVER has not supported reverse read. This fix allows the user to issue READ with I/O modifier IO$M_REVERSE set. 11 PROBLEMS ADDRESSED IN ALPLAD02_062 KIT FOR OPENVMS V6.2 o The ALPLAD01_062 kit was missing the ESS$LAST_STARTUP.COM and ESS$STARTUP.COM files for OpenVMS Alpha V6.2 -- COVER LETTER -- Page 8 13 September 2000 12 PROBLEMS ADDRESSED IN ALPLAD01_062 KIT FOR OPENVMS ALPHA V6.2 o UCB$L_DEVCHAR2 characteristics bits are not defined correctly when the template UCB is created. This causes SECURITY to crash the system and causes LADCP> BIND SERVICE/TAPE to prefix device name, MADx, with the node name or allocation class. This is inconsistent with the DAD device naming convention. o Container file corruption for PATHWORKS. None of the LAD services can be written to without corrupting the data in the service. After a write operation some of the errors with the following format can be seen using CHKDSK on a disk service: E:\EGASMC.FRS Allocation error, size adjusted E:\EGAUND.FRS Has invalid allocation unit, file truncated E:\EGASMC.FRS Is cross linked on allocation unit 95 o There is no MADDRIVER (InfoServer virtual tape driver) support for OpenVMS ALPHA V6.2. This change is to provide MADDRIVER support for OpenVMS VMS V6.2. 13 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_3 : To be installed by customers experiencing the problems corrected. 14 INSTALLATION INSTRUCTIONS: Install this kit with the {Installation Utility} utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL ALPLAD05_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. -- COVER LETTER -- Page 9 13 September 2000 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. Copyright (c) Compaq Computer Corporation, 2000 All Rights Reserved. Unpublished rights reserved under the copyright laws of the United States. The software contained on this media is proprietary to and embodies the confidential technology of Compaq Computer Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Compaq Computer Corporation. 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.