OpenVMS VMS712_DRIVER-V0300 DQDRIVER/DUDRIVER/TUDRIVER ECO Summary
TITLE: OpenVMS VMS712_DRIVER-V0300 DQDRIVER/DUDRIVER/TUDRIVER ECO Summary
New Kit Date : 04-APR-2001
Modification Date: Not Applicable
Modification Type: Updated Kit Supersedes VMS712_DRIVER-V0200 and
VMS712_DQCONFIG-V0200
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 2000, 2001. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: DQDRIVER
DUDRIVER
TUDRIVER
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS712_DRIVER-V0300
DEC-AXPVMS-VMS712_DRIVER-V0300--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS712_DRIVER-V0200 and
VMS712_DQCONFIG-V0200
ECO Kit Approximate Size: 640 Blocks
Kit Applies To: OpenVMS Alpha V7.1-2
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:
VMS712_UPDATE-V0300
VMS62TO71U2_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 DQDRIVER, DUDRIVER and TUDRIVER on OpenVMS Alpha
V7.1-2. This kit addresses the following problems:
PROBLEMS ADDRESSED IN VMS712_DRIVER-V0300 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 DRDRIVER deletes the UCB for unit 0 if there are no disks
configured on the adapter. This unit is being served to the
cluster before the keep/delete decision is made. When another
cluster node inquired about DR?0 via MSCP, the invalid UCB is
referenced resulting in a crash.
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
PROBLEMS ADDRESSED IN VMS712_DRIVER-V0200 KIT:
o A UCB (unit control block) is created for a device that has
already been configured into the I/O database. This causes an
INCONSTATE bugcheck to occur in either MOVE_IODB or
LINK_2P_UCB.
Images Affected: [SYS$LDR]DUDRIVER.EXE
o When initializing a FIBRECHANNEL (DG) device from a client,
one of the following errors may be returned:
INIT-F_DIAGPACK, 'Disk is a diagnostic pack'
or
INIT-W-NOBADDATA, 'Bad block data not found on volume'
Images Affected: [SYS$LDR]DUDRIVER.EXE
o If a mount command is issued for either a local or served TZ8X
drive that is connected to an HSJ/HSD controller, and the
drive has a COMPACT III tape loaded that has previously been
initialized at TK87 compacted density, the mount command hangs
or fails with a 'Volume not software enabled' error.
Images Affected: [SYS$LDR]SYS$TUDRIVER.EXE
[SYS$LDR]TUDRIVER.EXE
o An INVEXCEPTN bugcheck occurs at SYS$DUDRIVER_NPRO+10454.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
o During a tape mount verification,the system can crash due to
an INVEXCEPTN bugcheck.
Images Affected: [SYS$LDR]SYS$TUDRIVER.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 DUDRIVER functions inconsistently with IO$V_MSCPMODIFS
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
o During a port crash, failover event, mount verify or other
such occurrence, an invalid exception bugcheck can occur.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
o Update DQDRIVER to provide IO$_DIAGNOSE interface to ATAPI
devices, similar to the capabilities afforded in DKDRIVER for
SCSI devices.
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
o An INVEXCEPTN bugcheck can occur at SYS$DUDRIVER+0A690. See
partial dump below:
------------------------------
Bugcheck Type: INVEXCEPTN, Exception while above ASTDEL
CPU Type: AlphaServer 8400 5/625
Current Process: NULL
Current Image:
Failing PC: FFFFFFFF.A9454690 SYS$DUDRIVER+0A690
Failing PS: 20000000.00000804
Module: SYS$DUDRIVER (Link Date/Time: 29-APR-2000 21:54:11.29)
Offset: 0000A690
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
o After failover (the shutdown of a server), MSCP-served disks
hang in mount verify.
Images Affected: [SYS$LDR]SYS$DUDRIVER.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 five
minutes. SDA shows references to a disk with the same
allocation class as the server.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
o A process or the system can hang with stalled file I/Os.
Images Affected: [SYS$LDR]SYS$DUDRIVER.EXE
[SYS$LDR]SYS$TUDRIVER.EXE
Problems Addressed in VMS712_DQCONFIG_V0200:
o Use of a CD-ROM on a high performance Alpha system may cause
the PCI bus on the system to hang.
Images Affected: [SYS$LDR]SYS$DQDRIVER.EXE
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, 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-vms712_driver-v0300--4.README
dec-axpvms-vms712_driver-v0300--4.CHKSUM
dec-axpvms-vms712_driver-v0300--4.pcsi-dcx_axpexe
vms712_driver-v0300.CVRLET_TXT
|
