ECO NUMBER: ALPSCSI08_062 PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 UPDATE PRODUCT: OpenVMS Alpha OPERATING SYSTEM 6.2 COVER LETTER 1 KIT NAME: ALPSCSI08_062 2 KITS SUPERSEDED BY THIS KIT: ALPSCSI07_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 [SYSHLP.UNSUPPORTED]MKSET.EXE (new image) o [SYSHLP.UNSUPPORTED]SCSI_INFO.EXE (new image) o [SYS$LDR]SYS$DKDRIVER.EXE (new image) o [SYS$LDR]SYS$GKDRIVER.EXE (new image) o [SYS$LDR]SYS$mKDRIVER.EXE (new image) o [SYS$LDR]SYS$PKCDRIVER.EXE (new image) o [SYS$LDR]SYS$PKEDRIVER.EXE (new image) o [SYS$LDR]SYS$PKJDRIVER.EXE (new image) o [SYS$LDR]SYS$PKQDRIVER.EXE (new image) -- COVER LETTER -- Page 2 3 March 2000 o [SYS$LDR]SYS$PKSDRIVER.EXE (new image) o [SYS$LDR]SYS$PKTDRIVER.EXE o [SYS$LDR]SYS$PKZDRIVER.EXE (new image) o [SYSHLP.UNSUPPORTED]MKSET.TXT o [SYSHLP.UNSUPPORTED]MKSET_CLD.CLD 5 PROBLEMS ADDRESSED IN ALPSCSI08_062 KIT o If a shadowset is also a Pagefile disk, and a mount verification occurs for one of the set members, the failure IO Status is not copied to the IOST1 field. Whatever block was passed in the IRP$L_MEDIA field is left as an incorrect IO status. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o If a disk that is mounted as write protected is dismounted and un-write protected, when the disk is mounted again, it is still write protected. Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE o Appendix B of the OpenVMS V7.2 I/O User's Reference Manual states that the following values are ignored when S2DGB$V_TAGGED_REQ is 1: 1. S2DGV$L_32PHSTMO 2. S2DGV$L_64PHSTMO 3. S2DGV$L_32DSCTMO 4. S2DGV$L_64DSCTMO 5. S2DGB$V_DISCPRIV Although not documented, the PAD counts, S2DGV$L_32PADCNT and S2DGV$L_64PADCNT were included in this group. The implementation inadvertently conditionalized on the port's ability to handled command queuing instead of S2DGB$V_TAGGED_REQ. -- COVER LETTER -- Page 3 3 March 2000 The code has now been changed to conditionalize on S2DGB$V_TAGGED_REQ. The PAD counts are still included in the group. The documentation also stated that ports which do not support tagged command queuing always behave as if S2DGB$V_TAGGED_REQ is 0. This applies to the behavior of the ports and has no effect on whether the above set of parameters gets ignored. The reason these values are ignored when tagged command queuing is in use is that they can effect other commands to the connection until the IO$_DIAGNOSE command completes. (The timeout values are used as defaults for all commands to the connection for the duration of the command.) Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE - [SYS$LDR]SYS$GKDRIVER.EXE - [SYS$LDR]SYS$MKDRIVER.EXE o A generic scsi device may cause command timeout errors in the error log file Images Affected: - [SYS$LDR]SYS$DKDRIVER.EXE - [SYS$LDR]SYS$GKDRIVER.EXE - [SYS$LDR]SYS$MKDRIVER.EXE - [SYS$LDR]SYS$PKEDRIVER.EXE o Customers cannot use some SCSI devices with VMS due to a GKDRIVER limit of 65535 bytes transfer rate Images Affected: - [SYS$LDR]SYS$GKDRIVER.EXE o The skipfile function works on the MKdriver until a fatal tape error occurs. Skipfile is then permanently disabled until the next reboot. This problem slows down backups of appended save sets to sn unacceptable length of time. Images Affected: - [SYS$LDR]SYS$MKDRIVER.EXE -- COVER LETTER -- Page 4 3 March 2000 o The PKEDRIVER is unable to get mapping resources for I/O and the process hangs. Images Affected: - [SYS$LDR]SYS$PKEDRIVER - [SYS$LDR]SYS$PKTDRIVER o SCSI-1 devices fail with MEDOFL using PKEDRIVER. Images Affected: - [SYS$LDR]SYS$PKEDRIVER.EXE - [SYS$LDR]SYS$PKTDRIVER.EXE o A bugchek occurs when a data underrun condition is detected. Images Affected: - [SYS$LDR]SYS$PKQDRIVER.EXE o An INVEXCEPTN crash can occur during re-initialize of the KZPSA adapter. Images Affected: - [SYS$LDR]SYS$PKSDRIVER.EXE o An ACCVIO may occur during PKZDRIVER response processing. Images Affected: - [SYS$LDR]SYS$PKZDRIVER.EXE o A bad disk in a shadow set may hang the system. Images Affected: - [SYS$LDR]SYS$PKCDRIVER.EXE - [SYS$LDR]SYS$PKEDRIVER.EXE - [SYS$LDR]SYS$PKQDRIVER.EXE - [SYS$LDR]SYS$PKSDRIVER.EXE - [SYS$LDR]SYS$PKTDRIVER.EXE -- COVER LETTER -- Page 5 3 March 2000 - [SYS$LDR]SYS$PKWDRIVER.EXE - [SYS$LDR]SYS$PKZDRIVER.EXE 6 PROBLEMS ADDRESSED IN ALPSCSI07_062 KIT o A system crash can occur with an INCONSTATE error due to an attempt to execute two untagged WRITE commands. This problem can only occur on SMP (multiple CPU) machines and devices that do not support command Tagged Queuing. o A system crash can occur with an INVEXCEPTN exception due to bad SCSI device firmware. o Mount verification is unnecessary for a command that reports an event which did not fail. o When an HSZ/HSG controller device(s) reports mirror copy status events, the ERRCNT of the device is incremented, giving the false impression that the device(s) has a problem. o A cluster state transition hangs the cluster. o A system crash with an INVEXCEPTN exception occurs while an Asynchronous System Trap DELivery (ASTDEL) is at SYS$PKEDRIVER+0D338. o Two PKQdriver-related crashes can occur: 1. The Turbolaser crash was as follows: %BUGCHECK-I-INTOSWITCHDEV, into SwitchDevices %BUGCHECK-I-INTOINITBCB, into InitBootControlBlock %BUGCHECK-I-INTOFINDFILE, into Find_DumpFile %BUGCHECK-I-INTOVALDUMP, into Is_Valid_DumpFile %BUGCHECK-I-INTODUMPSHAD, into Is_DumpDev_Shadowed %BUGCHECK-I-EXITDUMPSHAD, exiting Is_DumpDev_Shadowed (success - not shadowed) %BUGCHECK-I-EXITVALDUMP, Exiting Is_Valid_DumpFile (at end) %BUGCHECK-I-EXITFINDFILE, exiting Find_DumpFile (success) %BUGCHECK-I-EXITINITBCB, exiting InitBootControlBlock (success) ** Bugcheck code = 0000099D: IOMACHINECHK, I/O induced machine check ** Crash CPU: 00 Primary CPU: 00 Active CPUs: 0000000B ** Current Process = NULL ** Current PSB ID = 00000001 ** Image Name = %BUGCHECK-I-EXITSWITCHDEV, exiting SwitchDevices %BUGCHECK-I-INTOMEMDUMP, into MemoryDump for memory dump %BUGCHECK-I-INITHEAD, initializing header %BUGCHECK-I-WRITHEAD, writing header %BUGCHECK-I-WRITERL, writing error logs -- COVER LETTER -- Page 6 3 March 2000 %BUGCHECK-I-REWRHEAD, rewriting header **** Starting selective memory dump (including shared memory) at 1-SEP-1998 09:54... ** Writing to device #01 in the DUMP_DEV environment variable %BUGCHECK-I-SELDUMP, calling SelectiveMemoryDump ................................................................. ................................................................. ....................................................... %BUGCHECK-I-FINDUMP, calling FinishDump ...Complete **** 2. INCONSTATE crash out of SYS$PKQDRIVER with an inconsistent I/O database o An INVEXCEPTN crash can occur when simultaneously booting a cluster with KZPSA SCSI adapters. o A system crash can occur with an INCONSTATE error due to an attempt to execute a target mode command when the Qlogic firmware does not have target mode support. o Since SCSI-3 devices will not configure on OpenVMS, a DRVERR error is returned, and the device is marked offline. o Quorum is lost and the system hangs in a single-node cluster when user I/O is active to the quorum disk and Mount Verification occurs. o Duplicate Units (UCBs) appear from some SCSI disks in three-node SCSI clusters. o The problem occurs when when an application (eg. HSZTERM, SMU) does an IO$_DIAGNOSE command, then that command is canceled while it is still active. (An IO$_DIAGNOSE function is used to send SCSI commands directly to a SCSI device). SMU does this command to change tapes via a loader, among other things. The problem seen with SMU is that it is shut down while a command (IO$_DIAGNOSE) is active, causing the I/O to be canceled. However, post processing via REQCOM is done twice. The problem was reproduced by issuing a SCSI command called Inquiry to a tape drive and then issuing a STOP PROC/ID= of that process. The system would then crash. o A Machine Check non-existent PCI Address system crash can occur. -- COVER LETTER -- Page 7 3 March 2000 7 NEW FUNCTIONALITY INCLUDED IN THE ALPSCSI06_062 KIT 7.1 Ultra SCSI Support for OpenVMS Version 6.2-1H3 OpenVMS Alpha Version 7.1-1H1 introduced support for certain Ultra SCSI devices in Ultra SCSI mode in single-host configurations. This kit extends Ultra SCSI support back to systems running OpenVMS Version 6.2-1H3 in single-host configurations only, using the KZPBA-CA, a single-ended adapter, or the KZPBA-CB adapter, a differential adapter. Note the restrictions described in Table 1. Table 1 OpenVMS_Restrictions Restrictions Comments __________________________ _______________________ If your system is an If the adapter is not already AlphaServer 4100 series installed, install this kit model and the KZPBA first according to the standard adapter is already installation procedure and then installed, a different install the adapter. installation procedure is recommended, which is provided in these release notes. Firmware for the KZPBA-CA This firmware is automatically or the KZPBA-CB must be updated from the system console Version 5.53 or higher. every time the system reboots. Console firmware must be All console SCSI driver fixes updated with the Alpha are included on this CD. This Systems Firmware Update CD CD also includes the latest Version 5.1 or higher. version of the KZPBA firmware (Version 5.53 or higher). DECevent Version 2.6 or Earlier versions of DECevent later is required for will display all of the analyzing events logged by logged data, but it will be the KZPBA port driver. in hexadecimal format only. For more information about Ultra SCSI devices supported by OpenVMS, including configuration guidelines, see the documents described in Table 2. Table 2 Documentation for Configuring OpenVMS Alpha Ultra SCSI Configurations --------------------------------------------------------------------- Topic Document Order Number ------------------- ---------------- ------------- SCSI devices that StorageWorks EK-ULTRA-CG -- COVER LETTER -- Page 8 3 March 2000 support Ultra SCSI UltraSCSI operations and how Configuration to configure them Guidelines KZPBA-CA UltraSCSI KZPBA-CA and SN- AV-QPBDC-TE storage adapter KZPBA-CA UltraSCSI Storage Adapter Module Release Notes KZPBA-CB UltraSCSI KZPBA-CB UltraSCSI AA-R5XWA-TE storage adapter Storage Adapter Module Release Notes KZPBA-CB UltraSCSI EK-KZPC-UG.C01 Storage Adapter Module User's Guide Information about StorageWorks Ultra SCSI products is available and periodically updated on the World Wide Web at the following URL: http://www.storage.digital.com OpenVMS software product descriptions are also available and periodically updated on the World Wide Web at the following URL: http://www.openvms.digital.com You will find the software product descriptions under Publications, a choice on the home page. 7.1.1 Installation Procedure for AlphaServer 4100 Series Models If your system is an AlphaServer 4100 series model, running OpenVMS Version 6.2-1H3 the following procedures detail different installation procedures for different configurations. 7.1.1.1 KZPBA adapter is not installed If the KZPBA adapter is not installed, install this kit first, according to the standard installation directions. Then install the KZPBA adapter. 7.1.1.2 KZPBA adapter already installed and at least one SCSI bus on the system does not use a KZPBA adapter If a KZPBA adapter is already installed on your system, Digital recommends the alternate installation procedure in this section. This is because, in rare cases, an AlphaServer 4100 system, with a KZPBA adapter already installed, has machine checked when a user attempted to install OpenVMS Version 6.2-1H3, before attempting to install this kit. -- COVER LETTER -- Page 9 3 March 2000 If all the buses on your system use KZPBA adapters, see the directions in the next section. 1. Select an install disk drive and target disk drive which are not on a bus interfaced through a KZPBA adapter. This example uses DKA500 for the install CD and DKB100 for the target disk. The installation is to SYS0. 2. Boot the install disk, using a conversational boot: >>> BOOT DKA500 -FL 0,1 3. At the SYSBOOT prompt, turn off AUTOCONFIGURE and type the CONTINUE command, as follows: SYSBOOT> SET NOAUTOCONFIGURE 1 SYSBOOT> CONTINUE 4. At the INSTALL menu, select the option to execute DCL command procedures. 5. Exclude those busses which have KZPBA adapters: $$$ MCR SYSMAN IO AUTO /EXCLUDE=(PKC*,PKD*,...) 6. Return to the INSTALL menu by typing: $$$ LOGOUT 7. Install OpenVMS Version 6.2-1H3 to the target disk. 8. Upon returning to the INSTALL menu, select the option to execute DCL command procedures again. 9. Delete SYS$PKQDRIVER.EXE from SYS$LOADABLE_IMAGES, with the following command: $$ DELETE DKB100:[sys0.syscommon.sys$ldr]sys$pkqdriver.exe;* 10. Return to the INSTALL menu by typing: $$$ LOGOUT 11. Shut down the system and complete the install by booting the target disk, which will then AUTOGEN and reboot. 12. Install this kit following the directions later in these release notes and reboot. -- COVER LETTER -- Page 10 3 March 2000 7.1.1.3 KZPBA adapter already installed and all buses use KZPBA adapters If all the buses on your system use KZPBA adapters, select one of the following options to install OpenVMS Version 6.2-1H3 and this kit: 1. Install another bus on your system with a different SCSI adapter (not a KZPBA adapter), then follow the procedure above. 2. Use another system to build the system disk with OpenVMS Version 6.2-1H3 and to install this kit. Then move this new system disk to its home system. 3. Boot into a cluster that is running OpenVMS Version 6.2-1H3 with this kit already installed. 8 PROBLEMS ADDRESSED IN ALPSCSI05_062 KIT o If the HSZ configuration utility HSZTERM has an an outstanding I/O to the HSZ, and Mount Verification occurs, then the system may crash. This usually happens under high I/O loads. o If Mount Verification occurs while a DK Device is reporting a write locked condition, the system will crash with an INVEXCEPTN Bugcheck. o When the new Quantum Atlas 2 disk drives are mounted in a cluster running Alpha OpenVMS V6.2-1H3, the system can enter an indefinite loop at mount verification, with each host issuing MODE SELECT commands. o Unnecessary Mount Verification for HSZ Unit Attention Conditions o The OpenVMS I/O User's Reference Manual added a new Magnetic Tape I/O Function IO$_FLUSH in Document Revision 1.5 for Alpha and revision 6.0 for VAX. This function was not fully implemented. o A TZ30 or TKZ50 will come up offline when a system boots on current versions of SYS$MKDRIVER. o The class driver queue could become frozen. HSZ devices may go into mount verify and eventually mount verify timeout after an HSZ70 failover. o o If a target returns a Queue Full status, an unnecessary Mount Verification occurs. -- COVER LETTER -- Page 11 3 March 2000 o In SYS$PKSDRIVER, if a command is reinserted on the device queue after a Queue Full condition occurs, the I/O will never complete. o RZ28B devices are not recognized by AUTOCONFIGURE. o A INCONSTATE crash can occur due to a Qlogic controller error. o Mount Verify not invoked for some recoverable errors. 9 PROBLEMS ADDRESSED IN ALPSCSI04_062 KIT o Unable to get or set volume using CDROM_AUDIO.C, a sample program in SYS$EXAMPLES which shows how to use the audio functions supported by DKDRIVER (SCSI disk class driver). Program logs CHECK CONDITIONs and fatal drive errors. o Mount fails on some devices. o Some non-Digital disks cannot be accessed using DKDRIVER due to "invalid mode sense" errors. o Tagged Command Queuing cannot be disabled at the drive level. o Fujitsu M2512A drive does not work on Alpha OpenVMS. o Copy/write_check fails to return error writing known bad block. o DKDRIVER does not properly support non-512 block devices. o Errors are logged when mounting some disks. o Unformatted floppies fail during format attempts. o Certain characteristics, such as mode sense 10 and tcq, cannot be permanently disabled. o Some third party SCSI-2 disks fail during data check operations. o Potential problem configuring SCSI devices. o Mount verification performed repeatedly with no error log entries to explain why. o Potential incorrect access to the mode page value for the WCE bit in the Caching mode page. o Potential miscalculation of DMA timeout value. -- COVER LETTER -- Page 12 3 March 2000 o Maximum usable disk size is only 8.6gb. Disk drives with a capacity of greater than 8.6gb are not fully utilized. o During a datacheck on SYS$PKEDRIVER, the ports may crash. This occurs because an attempt is made to read the autosense buffer after it has been deallocated. o Recoverable errors on disks were being treated as fatal except for "data recovered" errors of some types. o Some recoverable errors were being treated as success, which could lead to data corruption. o Deferred errors leave the I/O incomplete, no errors are reported. This can lead to undetected errors in disk I/O. o Geometry changes during packack, causes serving on clusters to fail. o Two names appear, and two paths, for SCSI disks when one side of a shared bus configures before another and the MSCP path to the disk is seen first. This causes problems in that f$device finds both. It can prevent host based RAID from working, can prevent quorum disks from functioning correctly, and often causes the local path not to be used when it is available and otherwise would be used. o SPI$CMD_BUFFER_ALLOC and SPI$BUFFER_MAP calls to port drivers can return error codes instead of allocating or mapping buffers. The port drivers crash, but the class driver is the root of the problem. Class code has not checked for these, and continued on using the pointers in SCDRP and other structures as though they were valid in such cases. At least one crash has definitely been traced to this, and several other mysterious crashes may have been related. The result can be pool corruption, or in some cases possibly disk corruption. o POOLCHECK can crash mounting disks. o Burns platform (Alphabook 1xxx/4xxx) system disk (IBM DPRS) is corrupted by INIT commands or by analy/disk/repair or continued use. o Badblock revectoring was delivering the wrong block numbers (negative, in fact) to the disk to be revectored. This would be rejected, but meant that bad blocks were not being revectored correctly. o The force_error routine that is used to force errors on certain blocks (so all shadowset members have the same error block numbers) were clobbering the boot block instead of the block selected. o IO$_AUDIO function may crash the system. -- COVER LETTER -- Page 13 3 March 2000 o Running HSZTERM while heavy I/O occurs results in an INVEXCEPTN bugcheck in port driver. o Third party archivers and Desktop Backup, which create Non-ANSI tapes, can see SS$_TAPEPOSLOST and SS$_DATAOVERUN errors when positioning tape. A new utility, SYS$ETC:MKSET.EXE, can parse DCL commands and generate these requests. It requires PHY_IO privilege since IO$_SETCHAR is a physical I/O function; thus it cannot be used by nonprivileged people. The utility can be used by enabling the MKSET command: $ SET COMMAND MKSET The syntax of the command is: $ MKSET/'qualifier' MKcuuu: There are three qualifiers to the MKSET command: NEVER - Never use the new SKIPFILE functionality. ALWAYS - Always use the new SKIPFILE functionality. PER_IO - Allow utilities such as BACKUP and DUMP to enable and disable the SKIPFILE functionality. Likewise, user programs can enable the SKIPFILE functionality with the IO$M_ALLOW_FAST modifier for the IO$_SKIPFILE function. For more information on this utility see: SYS$ETC:MKSET.TXT o Fatal drive error during attempt to INIT the Exabyte 8200 tape drive. o Request Sense data is truncated at 19 bytes. o If a Queue Full status is returned by a target, a MEDOFL status is returned by the Class Driver. This causes Mount Verification and an unnecessary SYSTEM-W-NOTQUEUED errorlog entry. o Unaligned reads (partial block) to a disk causes corruption of the EXE$GL_ERASEPB (Erase Pattern Buffer). Since this is used as a convenient source of zeros by various pieces of code it can lead to data corruption. o If Mount Verification occurs while a DK Device is reporting a write locked condition, the system will crash with an INCONSTATE Bugcheck. -- COVER LETTER -- Page 14 3 March 2000 o Disks goes into Mount Verify, and never comes out. o Error log entries have bad format. o Controller errors in systems with greater than 4gb of memory. o Controller errors when doing 1 and 2 byte transfer. o Crash after bus reset or adapter errors. o RZ74 will not mount if disk is not spinning. o Devices that require longer DMA and disconnect timeouts cannot be used until a fixed driver is supplied. o Mechanism for disabling SDTR, available in ALPSCSI02_070, was not documented. o Shadow copies and merges involving SCSI attached disks may crash system. 10 PROBLEMS ADDRESSED IN ALPSCSI02_070 KIT FOR OPENVMS ALPHA V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 o System can crash while forcing an error on a SCSI disk during a shadow copy. This problem is corrected in OpenVMS Alpha V7.0 o Extended Sense Data from the HSZ40 is truncated to about 20 bytes. This provides too little information to determine a failing raid member(s). o Premature command timeouts and SCSI bus resets. Occasionally the SCSI bus resets will crash the system. This problem occurs on SMP machines with the KZMSA adapter installed on DEC 7000 and AlphaServer 8000 machines or the Adaptec AHA-1740/1742 adapter installed on AlphaServer 2100 machines o The system can crash due to the driver having multiple bad block threads running at the same time. o Memory may be exhausted with BUFIO data structures. o In a two node SCSI cluster, shutting down one node can cause the surviving node to hang, especially if the system disk is the only disk on the bus. o SDTR (Synchronous Data Transfer) negotiations occur on every command issued through the IO$_DIAGNOSE QIO function. This can result in degradation of system performance. o Some SCSI 1 devices will become inoperative if they get SDTR negotiation messages. -- COVER LETTER -- Page 15 3 March 2000 o Preventing SDTR negotiations can crash system. o System crashes intermittently with an due to bugchecks (INCONSTATE) in PKEDRIVER when bus state is unknown. o Some SCSI 1 devices generate phase errors with the SCSI 2 driver. o Customers see the following DEVICE ERROR in the error log on Alpha 8400, and 8200 systems with SCSI disks connected to an KFTIA (ITIOP) IO module: ENTRY TYPE - Device Error OpenVMS SCSI Error type - Send SCSI Command Failed Port status - Unknown Port Status (hex value is 32C) o PKSDRIVER crash with a ACCVIO BUG_CHECK when a second SCSI cluster node boots. o Insufficient number of queue elements on the Adapter Driver Free Queue (ADFQ). These elements are used during SCSI bus reset processing. During heavy SCSI bus cluster traffic, the current number of free queue elements may run out. o INCONSTATE crash due to double deallocation of map registers. o DIAGNOSE reports unusual error log information for KZPSA errors. o KZPSA takes 6 seconds to initialize. This time could be reduced. 11 PROBLEMS ADDRESSED IN ALPSCSI01_070 KIT FOR OPENVMS ALPHA V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3 o The problem occurs on a check condition. When the request sense command is issued, both the condition code returned from SYS$QIO and the condition code returned in IOSB (after synchronization by SYS$SYNCH) indicate success. Also, the correct sense data block is transferred to the address specified in S2DGB$L_32DATADDR. Unfortunately the byte count in the IOSB is zero instead of the actual transfer length. o Serious performance degradation experienced with devices that use GKDRIVER. o Some SCSI devices that provide parameters cannot be used. They cause controller errors when in fact nothing is wrong. o Tapes, especially the TZ87, run so slowly during COPY that they appear to be hung. -- COVER LETTER -- Page 16 3 March 2000 o During backup the TLZ6L (TLZ06 with autoloader) and TLZ7L can take so long to rewind the current tape, and load the next tape that a SCSI command timeout error occurs, and the backup aborts. o A device at target ID 0 can be lost after a SCSI bus reset. o Device errors on KZPSA devices. o SCSI $QIO( IO$_DIAGNOSE ) for write functions fails. o MOUNT/CLUSTER/NOWRITE does not write-lock the device on the node which owns the disk. On the serving node, a DCL SHOW DEVICE command will report the device as write-locked, but users on the serving node may still modify the device. o Compaction works only on first volume of a multi-volume saveset. o TSZ07 density cannot be changed back and forth between 6250 bpi and 1600 bpi. o PKCDRIVER resets the 53C94 chip if the target does not enter the next phase within two seconds. o A failure of the ISP1020 DUMP_RAM command causes a checksum error in the read firmware. This improperly causes a bugcheck. o Error log entries are improperly formatted. Not all registers are dumped. o Some diagnostic error messages are not seen for severe problems. o Driver does not set field in SPDT. o On OpenVMS Alpha systems containing greater than 2gb of memory, PKSDRIVER would fail to deallocate a single non-paged pool MISC (SGMAP) entry on most SCSI I/O requests. System will either hang or fail to recover from a non-paged pool expansion failure. 12 PROBLEMS ADDRESSED IN ALPSCSI03_062 KIT o Prior to this correction, occasional data corruption and adapter/system hangs could occur on disks attached to KZPSA adapters on systems with more than 1 Gigabyte of physical memory. -- COVER LETTER -- Page 17 3 March 2000 13 PROBLEMS ADDRESSED IN AXPSCSI01_062 KIT o The SYS$MKDRIVER.EXE image in this kit allows a SCSI tape driver to recover fully from the SCSI error condition known as RECOVERED ERROR. The SCSI tape class driver, MKDRIVER, may not handle recovered errors correctly. The symptom of this problem is a failure message of "%SYSTEM-F-DRVERR (fatal drive error)" when attempting such tape operations as INITIALIZE and MOUNT. In such cases, an EXTENDED SENSE DATA RECEIVED error will be logged in the system error log file, and the error log entry will indicate an extended sense data value of RECOVERED ERROR. Note that this correction resolves the problem described in Section 4.11.2.3.2 of the OpenVMS Version 6.2 Release Notes. o The SYS$PKEDRIVER.EXE in this kit prevents machine checks when booting a system that has a NCR 53C810 SCSI adapter. (The NCR 53C810 PCI-to-SCSI chip is the integral SCSI adapter on several recent Alpha systems, and it is used on the KZPAA add-on adapter.) Systems containing NCR 53C810 SCSI adapters (SYS$PKEDRIVER) will sometimes get a machine check just after the OpenVMS Banner is printed when they boot. The error log shows that the machine check is a PCI bus problem. Usually (but not always) the system will boot successfully after you try several more times. The beginning of the error log entry for the machine check will look like one of the following: MACHINE CHECK AlphaServer 2100 4/200 KERNEL EVENT HEADER FRAME REVISION 0000 SCB VECTOR 0660 SEVERITY 0000 FIELD NOT VALID CPU ID 0000 ERROR COUNT 0002 FAIL CODE 0000 Unknown ERROR_FIELD_0 00000000 00000000 ERROR_FIELD_1 00000000 00000005 T2 Detected Bus Cmd/Addr No-Ack T2 Detected Bus Read Data Par Error ERROR_FIELD_2 00000000 00000000 ERROR_FIELD_3 00000000 00000000 MACHINE CHECK AlphaServer 2100 4/200 KERNEL EVENT HEADER -- COVER LETTER -- Page 18 3 March 2000 FRAME REVISION 0000 SCB VECTOR 0660 SEVERITY 0000 FIELD NOT VALID CPU ID 0000 ERROR COUNT 0002 FAIL CODE 0000 Unknown ERROR_FIELD_0 00000000 00000000 ERROR_FIELD_1 00000000 00000010 ERROR_FIELD_2 00000000 00000000 ERROR_FIELD_3 00000400 00000000 NCR Rec. Targ-Abrt while Master Note that this information replaces Section 3.34.2.2 in the OpenVMS Version 6.2 Release Notes. 14 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. 15 INSTALLATION INSTRUCTIONS: ****< CAUTION >***** *** AlphaServer 8400 and 8200 (TURBOLASER) INSTALLATION WARNING ** If you are installing this remedial kit on an AlphaServer 8400 or 8200, you MUST make sure your console is at Rev 4.0 or later. Rev 4.0 is available on the Alpha Firmware Update CDROM V3.7. Installing this kit on a system that has a console revision earlier than 4.0 WILL RESULT IN AN UNBOOTABLE SYSTEM. To recover from this situation, you will need to back out the new drivers by either booting from an alternate system disk and deleting the drivers off your regular disk, or by rebuilding your regular system disk. ********************* ** Installation Procedure for AlphaServer 4100 Series Models ** -- COVER LETTER -- Page 19 3 March 2000 o If your system is an AlphaServer 4100 series model, running OpenVMS Version 6.2-1H3 and the KZPBA adapter is not installed, install this ALPSCSI07_062 kit first, according to the standard installation directions below. Then install the KZPBA adapter. You must ensure that your KZPSA-BB has firmware revision A09 or later. If you are in doubt about the current version, you may try the load procedure. It will tell you the current adapter firmware revision prior to the load and allow the process to be terminated without loading. This revision includes the changes necessary for support of systems with >1gb of memory when using OpenVMS. o If an KZPBA adapter is already installed on your system, Compaq recommends the alternate installation procedure in this section. The reason for this recommendation is because, in rare cases, an AlphaServer 4100 system with an KZPBA adapter already installed has machine checked. This problem occurs when a user attempts to install OpenVMS V6.2-1H3 before attempting to install this ALPSCSI07_062 kit. The following procedure prevents this problem from happening: 1. Select an install disk drive and target disk drive which are not on a bus interfaced through an KZPBA adapter. This example uses DKA500 for the install CD and DKB100 for the target disk. The installation is to SYS0. 2. Boot the install disk, using a conversational boot: >>> BOOT DKA500 -FL 0,1 3. At the SYSBOOT prompt, turn off AUTOCONFIGURE and type the CONTINUE command, as follows: SYSBOOT> SET NOAUTOCONFIGURE 1 SYSBOOT> CONTINUE 4. At the INSTALL menu, select the option to execute DCL command procedures. 5. Exclude those buses which have KZPBA adapters: $$$ MCR SYSMAN IO AUTO /EXCLUDE=(PKC*,PKD*,...) 6. Return to the INSTALL menu by typing $$$ LOGOUT 7. Install OpenVMS V6.2-1H3 to the target disk. 8. Upon returning to the INSTALL menu, select the option to execute DCL command procedures again. -- COVER LETTER -- Page 20 3 March 2000 9. Delete SYS$PKQDRIVER.EXE from SYS$LOADABLE_IMAGES, with the following command: $$ DELETE DKB100:[sys0.syscommon.sys$ldr]sys$pkqdriver.exe;* 10. Return to the INSTALL menu by typing: $$$ LOGOUT 11. Shut down the system and complete the install by booting the target disk, which will then AUTOGEN and reboot. 12. Install this kit following the directions later in these release notes and reboot. o If all the buses on your system use KZPBA adapters, select one of the following options to install OpenVMS V6.2-1H3 and this kit: 1. Install another bus on your system with a different SCSI adapter (not a KZPBA adapter), then follow the procedure above. 2. Use another system to build the system disk with OpenVMS V6.2-1H3 and to install this kit. Then move this new system disk to its home system. 3. Boot into a cluster that is running OpenVMS V6.2-1H3 with this kit already installed. STANDARD 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 ALPSCSI08_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 21 3 March 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.