SEARCH CONTACT US SUPPORT SERVICES PRODUCTS STORE
United States    
COMPAQ STORE | PRODUCTS | SERVICES | SUPPORT | CONTACT US | SEARCH
gears
compaq support options
support home
software & drivers
ask Compaq
reference library
support forum
frequently asked questions
support tools
warranty information
service centers
contact support
product resources
parts for your system
give us feedback
associated links
.
} what's new
.
} contract access
.
} browse patch tree
.
} search patches
.
} join mailing list
.
} feedback
.
patches by topic
.
} DOS
.
} OpenVMS
.
} Security
.
} Tru64 Unix
.
} Ultrix 32
.
} Windows
.
} Windows NT
.
connection tools
.
} nameserver lookup
.
} traceroute
.
} ping
OpenVMS VMS721_DRIVER-V0200 Alpha V7.2-1 Drivers ECO Summary

TITLE: OpenVMS VMS721_DRIVER-V0200 Alpha V7.2-1 Drivers ECO Summary New Kit Date : 09-MAR-2001 Modification Date: 14-MAR-2001 Modification Type: Documentation ONLY: Corrected typographical error. NOTE: An OpenVMS saveset or PCSI installation file is stored on the Internet in a self-expanding compressed file. For OpenVMS savesets, the name of the compressed saveset file will be kit_name.a-dcx_vaxexe for OpenVMS VAX or kit_name.a-dcx_axpexe for OpenVMS Alpha. Once the OpenVMS saveset is copied to your system, expand the compressed saveset by typing RUN kitname.dcx_vaxexe or kitname.dcx_alpexe. For PCSI files, once the PCSI file is copied to your system, rename the PCSI file to kitname-dcx_axpexe.pcsi, then it can be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant file will be the PCSI installation file which can be used to install the ECO. Copyright (c) Compaq Computer Corporation 2001. All rights reserved. OP/SYS: OpenVMS Alpha COMPONENT: Drivers SOURCE: Compaq Computer Corporation ECO INFORMATION: ECO Kit Name: VMS721_DRIVER-V0200 DEC-AXPVMS-VMS721_DRIVER-V0200--4.PCSI ECO Kits Superseded by This ECO Kit: VMS721_DRIVER-V0100 VMS721_DQCONFIG-V0200 ECO Kit Approximate Size: 944 Blocks Kit Applies To: OpenVMS Alpha V7.2-1 System/Cluster Reboot Necessary: Yes Rolling Re-boot Supported: Yes Installation Rating: INSTALL_1 1 - To be installed on all systems running the listed version(s) of OpenVMS. Kit Dependencies: The following remedial kit(s) must be installed BEFORE installation of this kit: VMS721_UPDATE-V0100 VMS721_PCSI-V0100 In order to receive all the corrections listed in this kit, the following remedial kits should also be installed: None ECO KIT SUMMARY: An ECO kit exists for drivers on OpenVMS Alpha V7.2-1. This kit addresses the following problems: PROBLEMS ADDRESSED IN VMS721_DRIVER-V0200 KIT: o When a user attempts to create a directory on an IDE disk device larger than 30 GB, the system crashes with a UNXSIGNAL bugcheck at OTS$REM_UL_C+000B4 (a divide-by-0 crash). Crashdump Summary Information: ------------------------------ Bugcheck Type: UNXSIGNAL, Unexpected signal name in ACP Current Process: face - 407 Current Image: $14$DKB0:[SYS4.SYSCOMMON.][SYSEXE]CREATE.EXE Failing PC: FFFFFFFF.80007268 OTS$REM_UL_C+000B8 Failing PS: 10000000.00000000 Module: SYS$BASE_IMAGE (Link Date/Time: 29-DEC-1999 03:52:51.75) Offset: 00005268 Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE o The system cannot play audio CDs. Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE o A second instance of a GALAXY can not be booted. Also observed are repeated Bus Addressable Pool (BAP) errors with subsequent AUTOGEN runs. Images Affected: [SYS$LDS]SYS$DQDRIVER.EXE o Not all DRcu:: disks are seen by all cluster members. Images Affected: [SYS$LDR]SYS$DRDRIVER.EXE o V7.2-1 systems will not be able to access Fibre Channel tapes which are served by systems running verions of VMS later than V7.2-1H1. This change allows this access. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE [SYS$LDR]SYS$DUDRIVER.EXE o BACKUP between a V7.2-1 client and a V7.1 TMSCP served tape fails with POSITERR and IVDENS errors. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE [SYS$LDR]SYS$TUDRIVER.EXE o A MOUNT/FOR/NOASSIST/DENSITY=6250 command can be is issued for devices such as TA90 and TZ88. These commands make no sense for these devices but c ustomers have command files, that issue this command, without regard to the type of drive. Wehn sucha command file runs, the process or tape device will hang. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o A system can crash with an INVEXCEPTN bugcheck when a UCB (unit control block) was served prematurely. Crashdump Summary Information: ------------------------------ Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Current Process: NULL Current Image: Failing PC: FFFFFFFF.8022C8AC SCS$MSCP_CHECK_SERVICE_C+0085C Failing PS: 10000000.00000804 Module: MSCP Offset: 000028AC Images Affected: [SYS$LDR]SYS$DRDRIVER.EXE o DRA devices can not be served to the cluster because not all DRcu:: disks are seen by all cluster members. For example, MOUNT/CLUSTER $1$DRA0: will not fail or signal an error. Images Affected: [SYS$LDR]SYS$DRDRIVER.EXE Problems Addressed in VMS721_DRIVER-V0100: o IRP (I/O request packets) exit packets are not logged if FAST_PATH is enabled. Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE o A tape device hangs following MOUNT-F-SERIOUSEXCP errors. The tape device encounters a SEREXCP condition, which could be related to bad media being cycled through a tape library. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o The system can crash with an INVEXCEPTN in SYS$DUDRIVER. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE o Fix two DUDRIVER FAST_PATH checks. 1. Change the testing of IRP$M_SHDIO from IRP$L_STS to IRP$L_STS2. 2. Change the "obsolete modifiers" constant from ^X180 to ^80, since ^X100 is a IO$M_MSCPMODIFS bit. These fixes ensure FAST_PATH is used in all appropriate instances. Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE o The system can experience an invalid exception bugcheck in DUDRIVER. Images Affected: - [SYS$LDR]SYS$DUDRIVER.EXE - [SYS$LDR]SYS$TUDRIVER.EXE o Update the DQDRIVER to provide an IO$_DIAGNOSE interface to ATAPI devices, similar to the capabilities afforded in DKDRIVER for SCSI devices. Images Affected: [SYS$LDR]SYS$DKDRIVER.EXE o An INVPTEFMT bugcheck occurred in IO_ROUTINE_MON.EXE. See the dump summary below: Crash Time: 10-APR-2000 17:41:30.51 Bugcheck Type: INVPTEFMT, Invalid page table entry format Node: WILD11 (Cluster) CPU Type: Compaq AlphaServer ES40 VMS Version: X700-FT1 Current Process: NULL Current Image: Failing PC: FFFFFFFF.800CB0EC IOC_STD$PTETOPFN_C+0008C Failing PS: 38000000.00000804 Module: IO_ROUTINES_MON (Link Date/Time: 1-APR-2000 00:01:45.84) Offset: 000050EC Images Affected: [SYS$LDR]SYS$PBDRIVER.EXE o An INVEXCEPTN crash occurs @SYS$PBDRIVER+13088. A call to delete a shared memory region results in a NOWAIT error, and contacting the virtual address (VA) of the region ultimately results in the crash. See the partial dump below: ------------------------------ Crash Time: 15-MAY-2000 08:55:51.89 Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL Node: WILD5 (Cluster) CPU Type: Compaq AlphaServer GS160 6/731 VMS Version: X70V-SSB Current Process: NULL Current Image: Failing PC: FFFFFFFF.80481088 SYS$PBDRIVER+13088 Failing PS: 20000000.00000804 Module: SYS$PBDRIVER (Link Date/Time: 5-MAY-2000 23:36:55.31) Offset: 00013088 Boot Time: 15-MAY-2000 08:41:35.00 System Uptime: 0 00:14:16.89 Crash/Primary CPU: 08/08 System/CPU Type: 2308 Saved Processes: 23 Pagesize: 8 KByte (8192 bytes) Physical Memory: 8192 MByte (67108864 PFNs, discontiguous memory) Images Affected: [SYS$LDR]SYS$PBDRIVER.EXE o A tape device can hang following MOUNT-F-SERIOUSEXCP errors. BHAK$ mount/over=id $90$MUA2: %MOUNT-F-SERIOUSEXCP, serious exception detected by TMSCP controller BHAK$ sho dev /full mua2 Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o After failover, MSCP-served disks hang in MNTVER (MOUNT VERIFY). See a portion of an OPERCRASH dump below: - On the EBJB19:: client, check device $1$DGA2014: [WILD3$DGA2014 (WILD5$DGA2014)] Device status: 08265810 ONLINE,valid,unload,mntverip, Device status: 08265810 ONLINE,valid,unload,mntverip, Process (index=22) "O-2-BAD" stuck in LEF on this disk. B400222 0022 O-2-BAD SYSTEM LEF 4 Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE o BACKUP/MED=COMPACTION to an HSJ-based TZ87 fails with an SS-F-IVDENS (invalid density) error. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o A MOUNT command issued on V7.1 client for an Alpha V7.2-1, TMSCP served HSJ/TZ88 device fails with a MOUNT-F_VOLIN (MOUNT violation) error. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o The MOUNT/MED=COMPACTION command issued from a client does not enable compaction on TMSCP-served SCSI tape devices. Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o An INIT/MED=NOCOMP command to a SUPER-DLT (TZXX) drive, does not go into non-compacted mode. See example below: BTANKA> init/media=comp $255$MKC600: test BTANKA> sh dev/fu $255$MKC600: Magtape $255$MKC600: (DAVID3), device type COMPAQ DLT8000, is ONLINE, file-oriented device, available to cluster, error logging is enabled, controller supports compaction (compaction disabled). Error count 0 Operations completed 1339 Owner process "" Owner UIC [SYSTEM] Owner process ID 00000000 Dev Prot S:RWPL,O:RWPL,G:R,W Reference count 0 Default buffer siz 2048 Density DLT8000 Format Normal-11 Host name "DAVID3" Host type, avail Digital Personal WorkStation, yes Allocation class 255 Volume status: no-unload on dismount, beginning-of-tape, odd parity. BTANKA> Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE o A satellite system cannot boot when its allocation class is the same as the allocation class of the system disk, yet different from the allocation class of the MSCP disk server. The system will crash with an MSCPCLASS bugcheck after 5 minutes. SDA shows references to disk with an allocation class of the server. Crash Time: 14-MAR-2000 17:00:14.02 Bugcheck Type: MSCPCLASS, Fatal error detected by MSCP class driver Node: TSTPC3 (Cluster) CPU Type: VMS Version: V7.2-1 Current Process: SWAPPER Current Image: Failing PC: FFFFFFFF.81C49B90 SYS$DUDRIVER+09B90 Failing PS: 18000000.00000804 Module: SYS$DUDRIVER (Link Date/Time: 28-MAY-1999 23:19:57.92) Offset: 00009B90 Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE o A process or system hangs with file I/Os stalled and the class driver data block (CDDB) stuck in a single stream mode. Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE [SYS$LDR]SYS$TUDRIVER.EXE PROBLEMS ADDRESSED IN VMS721_DQCONFIG-V0200 KIT: o Use of CD-ROMs on high performance Alpha systems may cause system to hang. Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE PROBLEMS ADDRESSED IN VMS721_DQCONFIG-V0100 KIT: o On systems that include IDE/ATA or ATAPI drives, when booted from one of these devices, a second unit on the same IDE bus would not autoconfigure. For example, if system boot is from DQA0:, drive DQA1: would not be auto-configured, and vice-versa. Currently the only systems affected are the DS10/VS10/XP90. Images Affected: [SYS$LDR]SYS$ICBM.EXE o ES40 machines crash when a KZPAC is installed in Hose 0 and an attempt is made to mount a CD-ROM. This problem is also seen, to a lesser degree, on other platforms. Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE o Remove DMA support on the following platforms: o DPWS-xxxau o XP1000 o DS20 o DS20E o SMARTengine 21264/Alpha PCI/ISA SBC Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE INSTALLATION NOTES: 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. INSTALLATION INSTRUCTIONS: 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 VMS721_DRIVER /SOURCE=[location of Kit] The kit location may be a tape drive, CD, or a disk directory that contains the kit. Additional help on installing PCSI kits can be found by typing HELP PRODUCT INSTALL at the system prompt All trademarks are the property of their respective owners.



This patch can be found at any of these sites:

Colorado Site
Georgia Site



Files on this server are as follows:

dec-axpvms-vms721_driver-v0200--4.README
dec-axpvms-vms721_driver-v0200--4.CHKSUM
dec-axpvms-vms721_driver-v0200--4.pcsi-dcx_axpexe
vms721_driver-v0200.CVRLET_TXT

privacy and legal statement