ECO NUMBER: VAXPHV02_070 ----------- PRODUCT: OpenVMS VAX Operating System -------- UPDATED PRODUCT: OpenVMS VAX Operating System 7.0 ---------------- APPRX BLCK SIZE: 1080 ---------------- UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 7.0 COVER LETTER 1 KIT NAME: VAXPHV02_070 2 KITS SUPERSEDED BY THIS KIT: VAXPHV01_070 3 KIT DESCRIPTION: 3.1 Version(s) of OpenVMS to which this kit may be applied: OpenVMS VAX V7.0 3.2 In order to receive the full fixes listed in this kit the following remedial kits also need to be installed: None 3.3 Files patched or replaced: o SYS$LOADABLE_IMAGES:ECDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:EFDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:EPDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:ESDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:ETDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:EXDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:EZDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:FCDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:FQDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:FXDRIVER.EXE (new image) o SYS$LOADABLE_IMAGES:NET$CSMACD.EXE (new image) o SYS$LOADABLE_IMAGES:NET$FDDI.EXE (new image) o SYS$LOADABLE_IMAGES:XEDRIVER.EXE (new image) -- COVER LETTER -- Page 2 24 December 1996 o SYS$LOADABLE_IMAGES:XQDRIVER.EXE (new image) 4 PROBLEMS ADDRESSED IN VAXPHV02_070 KIT o A fix to cure a minor memory leak exposed a more severe problem, double deallocation of pool, resulting generally in a system crash. This kit removes the memory leak fix. o Crash after DECnet Time Service is shut down. o There is a race condition in the DEMNA and DEBNI drivers where a packet can be received before the completion of a STOP USER command. Since DECnet time service apparently does a deassign of a channel instead of a stop followed by a deassign, the driver has to stop completing receives to the user at the instant the stop request is received rather than waiting for completion of the command to the device that stops it. There was a short time where a receive packet could come in for a user that the driver knew nothing about, resulting in a crash. 5 PROBLEMS ADDRESSED IN VAXPHV01_070 KIT o System may crash when DEMFA is unplugged from the Gigaswitch. o System bug check when deleting a LAT link from LATCP when the device is shutting down to perform a normal reset. The system crash occurs in FQDRIVER or FCDRIVER. o System crash in NET$FDDI when processing a set station directive as a result of a DECnet-OSI NCL command. o System crash during startup or shutdown at NET$FDDI+50DD when trying to access an FDDI network management data structure that does not exist. It is possible for a DECnet-OSI user to create an FDDI station with CSMACD Network Management data structures. o Allocating a local data structure and overwriting existing pointers causes 106 bytes of memory to be "lost" when deleting the last user of the port. o This machine check occurs on a Q-BUS system with a DEFQA FDDI controller installed. The bugcheck reason is reported as an ASYNCWRTER, Asynchronous write memory failure. o LANCP MOP can't be enabled at the same time as DECnet-MOP even specifying selective mode. -- COVER LETTER -- Page 3 24 December 1996 o After upgrading to V6.2, MOP downline loads appears to be very slow. Loading that normally took 5 minutes and now is taking 30 minutes. A LAN trace and shows that the remote device being loaded is responding to ALL the MEMLOAD packets sent to it. However, the load host is delaying 3-4 seconds and retransmitting MEMLOAD packets even though the satellite had requested the next MEMLOAD. 6 KIT INSTALLATION RATING: The following kit installation rating, based upon current CLD information, is provided to serve as a guide as to which customers should apply this remedial kit. (Reference attached Disclaimer of Warranty and Limitation of Liability Statement) INSTALLATION RATING: 3 : To be installed by customers experiencing the problems corrected. 7 INSTALLATION INSTRUCTIONS: Install this kit with the VMSINSTAL utility by logging into the SYSTEM account, and typing the following at the DCL prompt: @SYS$UPDATE:VMSINSTAL VAXPHV02_070 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. System should be rebooted after successful installation of the kit. If you have other nodes in your VMScluster, they should also be rebooted in order to make use of the new image(s). Copyright (c) Digital Equipment Corporation, 1997. 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 Digital Equipment Corporation. Possession, use, or dissemination of the software and media is authorized only pursuant to a valid written license from Digital Equipment 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 DIGITAL BE -- COVER LETTER -- Page 4 24 December 1996 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.