ECO NUMBER: VAXPHV03_062 PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS VAX OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: VAXPHV03_062 2 KITS SUPERSEDED BY THIS KIT: VAXPHV02_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this, or any required kit: None. 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 VAX V6.2 4.2 Files patched or replaced: o [SYS$LDR]ECDRIVER.EXE (new image) o [SYS$LDR]EFDRIVER.EXE (new image) o [SYS$LDR]EPDRIVER.EXE (new image) o [SYS$LDR]ESDRIVER.EXE (new image) o [SYS$LDR]ETDRIVER.EXE (new image) o [SYS$LDR]EXDRIVER.EXE (new image) o [SYS$LDR]EZDRIVER.EXE (new image) o [SYS$LDR]FCDRIVER.EXE (new image) o [SYS$LDR]FQDRIVER.EXE (new image) -- COVER LETTER -- Page 2 4 February 1999 o [SYS$LDR]FXDRIVER.EXE (new image) o [SYS$LDR]NET$CSMACD.EXE (new image) o [SYS$LDR]NET$FDDI.EXE (new image) o [SYS$LDR]XEDRIVER.EXE (new image) o [SYS$LDR]XQDRIVER.EXE (new image) 5 PROBLEMS ADDRESSED IN VAXPHV03_062 KIT o For a command: NCL> SHOW FDDI STATION FDDI-0 * ALL the SMTstationID field was displayed as '0000000000000000'H, but should have been '080008002B209E45'H. o A crash occurred in module FX$SCHED_CMDUNS_FORK while doing a DEVICELOCK. The crash occured under the following conditions: 1. FDDI (DEMFA) 2. MOPRC (60-02) 3. crash address FXDRIVER+022E4 4. current process was running TSM$MAIN o During testing of failover to a second FDDI controller, after an FDDI cable was removed, a SET HOST command hung for one minute, resulting in a bugcheck at TIMER.BUG. Note that the problem did not cause a fatal error and allowed the FDDI ring to resynchronize. o DECnet hung for 1 minute when the FDDI cable was removed from the bulkhead. o Attempting to start the MOPRC protocol on a DEMFA returned an SS$_DEVREQERR error status. o If a DEMFA FDDI controller fails, then transmit requests can possibly fail to complete within a timeout period. The failure that a user sees is that the FDDI path fails and then the cluster software does not switch to another path, usually resulting in a CLUEXIT error. o When the cable is disconnected from the DEMFA FDDI controller, timing problems can occur in the driver, which could result in a crash after an extended period of cable disconnections -- COVER LETTER -- Page 3 4 February 1999 (typically weeks). o The LAN Driver received a loopback packet with a broadcast destination address, which was an invalid use of the loopback protocol (90-00) format. However, the packet was not regarded as invalid, resulting in a crash at EZDRIVER+072E3. o Transmit timeouts errors must be set as fatal. A user had a problem with failover on the DEMFA on a VAX system. Although a transmit timeout had occurred, the transmit completed with an error status and continued. Since the failure happened in such a way that the link did not go down and come back up, a failover never happened. o A crash occurred during timeout processing and it can happen on a VAX 4000-90, VAX 4000-300, etc., that also has an SGEC Ethernet adapter. 6 PROBLEMS ADDRESSED IN VAXPHV02_062 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. 7 PROBLEMS ADDRESSED IN VAXPHV01_062 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. 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. -- COVER LETTER -- Page 4 4 February 1999 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 Applications don't receive packets larger than the buffer size specified by the first user to start up. For example: If the first user specifies a receive buffer size of 300 bytes, the DEMNA firmware discards all packets received that are larger. This problem is corrected in OpenVMS VAX V7.0. o A QIO with a null pointer to the P2 parameter causes an Invalid Exception (INVEXCEPTION), crash. This can occur on all Ethernet and FDDI LAN drivers. This problem is corrected in OpenVMS VAX V7.0. 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 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. 8 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. -- COVER LETTER -- Page 5 4 February 1999 9 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 VAXPHV03_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. The images in this kit will not take effect until the system is rebooted. If you have other nodes in your VMS 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, 1999 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.