ECO NUMBER: ALPCPU0907_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPCPU0907_062 2 KITS SUPERSEDED BY THIS KIT: ALPCPU906_062 3 KIT DEPENDENCIES: 3.1 The following remedial kit(s) must be installed BEFORE installation of this kit: None. 3.2 In order to receive the all the corrections listed in this kit, the following remedial kits should also be installed: ALPLAN05_062 - For RACOR and DE500-BA adapter support 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$CPU_ROUTINES_0905.EXE (new image) o [SYS$LDR]SYS$CPU_ROUTINES_0902.EXE (new image) o [SYS$LDR]SYS$CPU_ROUTINES_1802.EXE (new image) o [SYS$LDR]SYS$CPU_ROUTINES_1805.EXE (new image) o [SYS$LDR]SYS$CPU_ROUTINES_0602.EXE (new image) 5 PROBLEMS ADDRESSED IN ALPCPU0907_062 KIT o Add support for the DE500-BA adapter and the Gigabit Ethernet adapter. -- COVER LETTER -- Page 2 26 March 1998 o The RACORE (Token Ring) adapter was never supported in V6.2. The supported adapter, Thomas Conrad (Token Ring adapter) is being phased out so this new adapter must be supported. 6 PROBLEMS ADDRESSED IN ALPCPU906_062 KIT o If an AlphaServer 2100 5/300, AlphaServer 2000 5/300, or AlphaServer 2100A 5/300 system has a problem with CPU0, and the console fails over to a different CPU, the user may see a mchk in PAL mode while trying to boot. (Halt code=7). o Change errorlog type codes used to log machine check frames. The errorlog type code will now match expected values for proper DECevent analysis. 7 PROBLEMS ADDRESSED IN ALPCPU905_062 KIT o Remedial kits ALPDRIV10_061 and ALPCPU904_062 both contain the V6.1R, SYS$CPU_ROUTINES_0902.EXE image. Eliminate this duplication. 8 PROBLEMS ADDRESSED IN ALPCPU904_062 KIT o There is a dependency between this kit and the AXPGUP01_062 remedial kit. When the ALPCPU904_062 remedial kit is installed on an OpenVMS Alpha V6.2 system the AXPGUP01_062 remedial kit must also be installed. If it is not, it is possible to experience bugchecks caused by machine checks while in kernal mode. 9 PROBLEMS ADDRESSED IN ALPCPU903_062 KIT o If a device's EISA configuration utility CFG file requests two or more IRQs, the device can crash an EISA_based system. This problem can occur on Digital AlphaServer 2100 5/250, AlphaServer 8400 5/275, AlphaStation 600 5/266, Digital AlphaServer 1000 4/200 and DEC 2000-300 platforms. -- COVER LETTER -- Page 3 26 March 1998 10 PROBLEMS ADDRESSED IN ALPCPU902_062 KIT o Intermittent system failures caused by a correctable memory error which is being handled incorrectly. Failure is an INVEXCEPTN crash. 11 PROBLEMS ADDRESSED IN ALPCPU902_062 KIT o When the system tries to queue a lock request against the associated resource, it encounters a corrupted R0 which causes a system crash. The corruption is the allocated pattern from the setting of POOL_CHECK (an ASCII "a" character, 61 Hex)." 12 PROBLEMS ADDRESSED IN ALPCPU901_062 KIT o Due to machine checks in PALmode while booting, AlphaServer 2100 systems with either a EV45/275 MHz CPU or an EV5 CPU installed may not boot. If you are seeing a machine check in PAL mode while booting, you must apply this patch. 13 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: INSTALL_2 : To be installed by all customers using the following feature(s): RACORE (Token Ring) adapter and/or DE500-BA adapter 14 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 ALPCPU0907_062 [location of the saveset] The saveset location may be a tape drive, or a disk directory that contains the kit saveset. -- COVER LETTER -- Page 4 26 March 1998 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) Digital Equipment Corporation, 1998 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 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.