======================================================================= Hewlett-Packard OpenVMS ECO Release Notes ======================================================================= 1 KIT NAME: VMS84I_USB-V0100 2 KIT DESCRIPTION: 2.1 Installation Rating: INSTALL_3 : To be installed by customers experiencing the problems corrected. 2.2 Reboot Requirement: Reboot Required. HP 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. 2.3 Version(s) of OpenVMS to which this kit may be applied: OpenVMS for Integrity Servers V8.4 2.4 New functionality or new hardware support provided: No 3 KITS SUPERSEDED BY THIS KIT: - None 4 KIT DEPENDENCIES: 4.1 The following remedial kit(s), or later, must be installed BEFORE installation of this, or any required kit: - VMS84I_PCSI-V0400 - VMS84I_UPDATE-V0700 Page 2 4.2 In order to receive all the corrections listed in this kit, the following remedial kits, or later, should also be installed: - None 5 NEW FUNCTIONALITY AND/OR PROBLEMS ADDRESSED IN THE VMS84I_USB-V0100 KIT 5.1 New functionality addressed in this kit Not Applicable 5.2 Problems addressed in this kit 5.2.1 BL8x0c i2/rx2800 i2 system crash or hang on BAP exhaustion 5.2.1.1 Problem Description: UHCI(USB controller) driver not freeing up the memory allocated from BAP pool leads to system hang or crash. This issue is fixed. Images Affected: - [SYS$LDR]SYS$UHCIDRIVER.EXE - [SYS$LDR]SYS$UHCIDRIVER.STB - [SYS$LDR]SYS$USBDRIVER.EXE - [SYS$LDR]SYS$USBDRIVER.STB 5.2.1.2 Quix and PTR cases reporting this problem: 5.2.1.2.1 Quix Cases QXCM1001173685, QXCM1001186877 5.2.1.2.2 PTR(s) None Page 3 5.2.1.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.1.4 Work-arounds: None 5.2.2 AB552 keyboard not working on rx2800 i2 and BL8x0c i2 5.2.2.1 Problem Description: AB552 keyboard failed to configure on rx2800 i2 and BL8x0c i2 with VMS84I_UPDATE V6.0 and above. This issue is fixed. Images Affected: - [SYS$LDR]SYS$HUBDRIVER.EXE - [SYS$LDR]SYS$HUBDRIVER.STB 5.2.2.2 Quix and PTR cases reporting this problem: 5.2.2.2.1 Quix Cases QXCM1001210735 5.2.2.2.2 PTR(s) None 5.2.2.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.2.4 Work-arounds: None Page 4 5.2.3 Virtual keyboard/mouse fails on rx2800 i2/BL8x0c i2 server after firmware update 5.2.3.1 Problem Description: System iLO (MP) resets with firmware update. iLO3 firmware is not emulating the virtual devices as expected with MP reset, because of which virtual devices (keyboard/mouse) not working after firmware update. Root cause of this issue is fixed in iLO3 in firmware version K26.35 for BL8x0ci2 and S26.35 for rx2800 i2. OpenVMS USB drivers also modified based on changes in iLO firmware. This issue is fixed. Images Affected: - [SYS$LDR]SYS$HUBDRIVER.EXE - [SYS$LDR]SYS$HUBDRIVER.STB 5.2.3.2 Quix and PTR cases reporting this problem: 5.2.3.2.1 Quix Cases QXCM1001179282 5.2.3.2.2 PTR(s) None 5.2.3.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.3.4 Work-arounds: None 5.2.4 OpenVMS system crash with INVEXCEPTN in SYS$KBDDRIVER with firmware update Page 5 5.2.4.1 Problem Description: System iLO(MP) will be reset with firmware update. MP reset makes virtual devices to de-configure and re-configure. On MP reset, system may crash in SYS$KBDDRIVER with INVEXCEPTN as the device de-configuration completed without aborting/completing the I/O"s Images Affected: - [SYS$LDR]SYS$HUBDRIVER.EXE - [SYS$LDR]SYS$HUBDRIVER.STB - [SYS$LDR]SYS$HIDDRIVER.EXE - [SYS$LDR]SYS$HIDDRIVER.STB - [SYS$LDR]SYS$KBDDRIVER.EXE - [SYS$LDR]SYS$KBDDRIVER.STB 5.2.4.2 Quix and PTR cases reporting this problem: 5.2.4.2.1 Quix Cases QXCM1001203261, QXCM1001115552, QXCM1001203261 5.2.4.2.2 PTR(s) None 5.2.4.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 5.2.4.4 Work-arounds: None 5.2.5 USB Keyboard not working after system reboot Page 6 5.2.5.1 Problem Description: USB keyboard fails to configure if the keyboard is connected while booting the system. Images Affected: - [SYS$LDR]SYS$HUBDRIVER.EXE - [SYS$LDR]SYS$HUBDRIVER.STB - [SYS$LDR]SYS$USBDRIVER.EXE - [SYS$LDR]SYS$USBDRIVER.STB - [SYS$LDR]SYS$HIDDRIVER.EXE - [SYS$LDR]SYS$HIDDRIVER.STB - [SYS$LDR]SYS$KBDDRIVER.EXE - [SYS$LDR]SYS$KBDDRIVER.STB - [SYS$LDR]SYS$OHCIDRIVER.EXE - [SYS$LDR]SYS$OHCIDRIVER.STB - [SYS$LDR]SYS$UHCIDRIVER.EXE - [SYS$LDR]SYS$UHCIDRIVER.STB 5.2.5.2 Quix and PTR cases reporting this problem: 5.2.5.2.1 Quix Cases None 5.2.5.2.2 PTR(s) 75-126-149 5.2.5.3 Release Version of OpenVMS that will contain this change: Next release of OpenVMS Integrity after V8.4 Page 7 5.2.5.4 Work-arounds: None 6 FILES PATCHED OR REPLACED: o [SYS$LDR]SYS$HIDDRIVER.EXE (new image) Image Identification Information Image name: "SYS$HIDDRIVER" Image file identification: "X-5" Image build identification: "0100000089" linker identification: "Linker I02-37" Link Date/Time: 29-OCT-2012 17:14:28.55 Overall Image Checksum: 16BEF158 o [SYS$LDR]SYS$HUBDRIVER.EXE (new image) Image Identification Information Image name: "SYS$HUBDRIVER" Image file identification: "X-5" Image build identification: "0100000089" linker identification: "Linker I02-37" Link Date/Time: 29-OCT-2012 17:14:30.33 Overall Image Checksum: 86E3F8C1 o [SYS$LDR]SYS$KBDDRIVER.EXE (new image) Image Identification Information Image name: "SYS$KBDDRIVER" Image file identification: "X-5" Image build identification: "0100000089" linker identification: "Linker I02-37" Link Date/Time: 29-OCT-2012 17:14:33.40 Overall Image Checksum: 5F935882 o [SYS$LDR]SYS$OHCIDRIVER.EXE (new image) Image Identification Information Image name: "SYS$OHCIDRIVER" Image file identification: "X-5" Image build identification: "0100000089" linker identification: "Linker I02-37" Link Date/Time: 29-OCT-2012 17:14:36.05 Overall Image Checksum: 600DB6BD o [SYS$LDR]SYS$UHCIDRIVER.EXE (new image) Image Identification Information Image name: "SYS$UHCIDRIVER" Page 8 Image file identification: "X-5" Image build identification: "0100000089" linker identification: "Linker I02-37" Link Date/Time: 29-OCT-2012 17:14:38.21 Overall Image Checksum: 70AD4BB8 o [SYS$LDR]SYS$USBDRIVER.EXE (new image) Image Identification Information Image name: "SYS$USBDRIVER" Image file identification: "X-5" Image build identification: "0100000089" linker identification: "Linker I02-37" Link Date/Time: 29-OCT-2012 17:14:31.87 Overall Image Checksum: AAD4A2E2 o [SYS$LDR]SYS$HIDDRIVER.STB (new file) o [SYS$LDR]SYS$HUBDRIVER.STB (new file) o [SYS$LDR]SYS$KBDDRIVER.STB (new file) o [SYS$LDR]SYS$OHCIDRIVER.STB (new file) o [SYS$LDR]SYS$UHCIDRIVER.STB (new file) o [SYS$LDR]SYS$USBDRIVER.STB (new file) 7 INSTALLATION INSTRUCTIONS 7.1 Test/Debug Image Loss In the course of debugging problems reported to OpenVMS Engineering, customers may be given debug or point-fix images to install. Typically, these images do not have the same image generation flags contained in images released via the OpenVMS remedial patch process. Because of this, any debug or point-fix image that is in the SYS$COMMON area, will be replaced by any image of the same name installed by this kit. If this occurs, you will lose any functionality that is provided by the replaced image. If you wish to retain these debug or point-fix images, you can take the following steps: o Prior to installing this kit, move the test/debug image(s) to be saved to the SYS$SPECIFIC area. o During kit installation, you will be asked if you wish to delete the image(s) in SYS$SPECIFIC. You should answer NO for each image that you want to keep. o After installation completes, but before rebooting the system (if required), move the image(s) from SYS$SPECIFIC back to SYS$COMMON. Page 9 7.2 Compressed File This kit is provided as a Self Extracting ZIPEXE kit. To expand this file to the installable .PCSI file, run the file with the following command: $ RUN VMS84I_USB-V0100.ZIPEXE 7.3 Installation Command Install this kit with the POLYCENTER Software installation utility by logging into the SYSTEM account, and typing the following at the DCL prompt: PRODUCT INSTALL VMS84I_USB[/SOURCE=location of Kit] Note that this kit will install with the /SAVE_RECOVERY_DATA option turned on. Using this qualifier will allow easy removal of the kit from the system in the event of problems. If you wish to disable this option you must use the /NOSAVE_RECOVERY_DATA qualifier on the PRODUCT INSTALL command. The /SAVE_RECOVERY_DATA qualifier is optional but highly recommended. Using this qualifier will allow easy removal of the kit from the system in the event of problems. The kit location may be a tape drive, CD, or a disk directory that contains the kit. The /SOURCE qualifier is not needed if the PRODUCT INSTALL command is executed from the same directory as the kit location. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt. 7.4 Scripting of Answers to Installation Questions During installation, this kit will ask and require user response to several questions. If you wish to automate the installation of this kit and avoid having to provide responses to these questions, you must create a DCL command procedure that includes the following logical name definitions and commands: o To avoid the BACKUP question, define the following: $ DEFINE/SYS NO_ASK$BACKUP TRUE o To avoid the REBOOT question, define the following: $ DEFINE/SYS NO_ASK$REBOOT TRUE o To save replaced files as *.*_OLD define the following logical name as YES. If you do not wish to save replaced files, define the logical name as NO. Note that if you use the /SAVE_RECOVERY_DATA qualifier (recommended) on the PRODUCT INSTALL command all replaced files will be saved as part of Page 10 that operation. There is no need to also save files as *.*_OLD: $ DEFINE/JOB ARCHIVE_OLD NO o Add the following qualifiers to the PRODUCT INSTALL command and add that command to the DCL procedure. /PROD=HP/BASE=I64VMS/VER=V1.0 [/SOURCE=location of Kit] o De-assign the logical names assigned For example, a sample command file to install the VMS84I_USB-V0100 kit would be: $ DEFINE/SYS NO_ASK$BACKUP TRUE $ DEFINE/SYS NO_ASK$REBOOT TRUE $ DEFINE/JOB ARCHIVE_OLD NO $! $ PROD INSTALL VMS84I_USB/PRODUCER=HP/BASE=I64VMS/VER=V1.0 $! $ DEASSIGN/SYS NO_ASK$BACKUP $ DEASSIGN/SYS NO_ASK$REBOOT $! $ exit $! 7.5 Special Installation Instructions: Engineering recommends to update K26.35 firmware on BL8x0c i2 and S26.35 on rx2800 i2 firmware before installing this kit. 8 COPYRIGHT AND DISCLAIMER: (C) Copyright 2012 Hewlett-Packard Development Company, L.P. Confidential computer software. Valid license from HP and/or its subsidiaries required for possession, use, or copying. Consistent with FAR 12.211 and 12.212, Commercial Computer Software, Computer Software Documentation, and Technical Data for Commercial Items are licensed to the U.S. Government under vendor's standard commercial license. Neither HP nor any of its subsidiaries shall be liable for technical or editorial errors or omissions contained herein. The information in this document is provided "as is" without warranty of any kind and is subject to change without notice. The warranties for HP products are set forth in the express limited warranty statements accompanying such products. Nothing herein should be construed as constituting an additional warranty. Page 11 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 HP 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.