ECO NUMBER: ALPDRIV22_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPDRIV22_062 2 KITS SUPERSEDED BY THIS KIT: ALPDRIV18_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 Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 4.2 Files patched or replaced: o [SYS$LDR]SYS$DRDRIVER.EXE (new image) 5 PROBLEMS ADDRESSED IN ALPDRIV22062 KIT o HDRFULL and BADFID errors on DR devices. Images Affected: - [SYS$LDR]SYS$DRDRIVER.EXE o A mismatch between the command count and the actual number of commands causes an INVEXCEPTN system crash. The crash footprint is as follows: Fatal Bugcheck -- COVER LETTER -- Page 2 14 July 2000 Crash Time: 28-MAY-1999 15:37:26.88 Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Node: TRDHQ1 (Clustered) CPU Type: AlphaServer 2100 4/275 VMS Version: V7.1 Current Process: A1 Sender_1 Current Image: DSA0:[ALLIN1.OA$EXE_AXP_SHARE]OA$MAIN.EXE Failing PC: FFFFFFFF.802537DC SYS$DRDRIVER_NPRO+057DC Failing PS: 30000000.00000804 Images Affected: - [SYS$LDR]SYS$DRDRIVER.EXE 6 PROBLEMS ADDRESSED IN ALPDRIV18_062 KIT o This set of changes introduces improvements to DRDRIVER that are needed to support StorageWorks Command Console, the global configuration/monitoring system available from Storage. 7 PROBLEMS ADDRESSED IN ALPDRIV14_062 KIT o The ALPDRIV01_071 remedial kit, which applied to V6.2* and V7.1 is being reissued as two single version kits. There are no new fixes in this kit. If you have installed the ALPDRIV01_071 remedial kit you do not need to install the ALPDRIV14_062 kit. 8 PROBLEMS ADDRESSED IN ALPDRIV01_071 KIT FOR OPENVMS ALPHA V6.2* o There are actually two instances of essentially the same problem. The first is in routine dr_compare(), the second in dr_diagnose(). Those routines both call dr_allocate_io(), which (on large-memory systems) allocates map registers based on the values of irp$l_boff and irp$l_bcnt. These registers are then used to map, not the user buffer, but a driver-private buffer (dr->buffer) that is to be the target of the eventual I/O request. If the page alignment of dr->buffer is such that the I/O touches an extra page there that it wouldn't have touched in the user buffer, dr_allocate_io() can end up allocating one too few map registers, and the resulting DMA operation fails to transfer the correct amount of data. -- COVER LETTER -- Page 3 14 July 2000 In both cases, the driver has been modified to set irp$l_boff temporarily to the correct value for the driver-private buffer before the call to dr_allocate_io(). irp$l_boff is then restored to its original value. 9 PROBLEMS ADDRESSED IN ALPDRIV04_062 KIT o DRDRIVER (the SWXCR RAID array driver) can hang. This hang occurs when a shadow copy is in progress between two logical RAID (DR) drives, and the SWXCR controller is under an extremely heavy I/O load. This problem is corrected in OpenVMS Alpha V7.0. 10 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_2 : To be installed by all customers using the following feature(s): StorageWorks Command Console 11 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 ALPDRIV22_062 [location of the saveset] The saveset location may be a tape drive, CD, or a disk directory that contains the kit saveset. 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. -- COVER LETTER -- Page 4 14 July 2000 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.