OpenVMS] ALPSCSI08_062 Alpha V6.2 SCSI ECO Summary
TITLE: OpenVMS] ALPSCSI08_062 Alpha V6.2 SCSI ECO Summary
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 1999, 2000. All rights reserved.
Modification Date: 08-NOV-2000
Modification Type: Documentation:
Added note regarding increasing GH_EXEC_CODE and
GH_EXEC_DATA.
**************************** NOTE ***************************
* *
* It may be neccesary to increase GH_EXEC_CODE = 1024 and *
* GH_EXEC_DATA = 224 after loading this patch the following *
* error occurs on reboot: *
* *
* PKQDRIVER-W-PKA0 initialization failed, device offline *
* *
******************************************************************
*****< 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
then deleting the drivers off your regular disk, or by rebuilding your
regular system disk.
*********************
PRODUCT: OpenVMS Alpha
COMPONENTS: SCSI Drivers - MKSET.EXE
SCSI_INFO.EXE
SYS$DKDRIVER.EXE
SYS$GKDRIVER.EXE
SYS$MKDRIVER.EXE
SYS$PKCDRIVER.EXE
SYS$PKEDRIVER.EXE
SYS$PKJDRIVER.EXE
SYS$PKQDRIVER.EXE
SYS$PKSDRIVER.EXE
SYS$PKTDRIVER.EXE
SYS$PKZDRIVER.EXE
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: ALPSCSI08_062
ECO Kits Superseded by This ECO Kit: ALPSCSI07_062
ALPSCSI06_062
ALPSCSI05_062
ALPSCSI04_062
ALPSCSI02_070 (For Alpha V6.2
systems only)
ALPSCSI01_070
ALPSCSI03_062
AXPSCSI01_062 (AXPSCSI)
ECO Kit Approximate Size: 1872 Blocks
Kit Applies To: OpenVMS Alpha V6.2, V6.2-1H1, V6.2-1H2, V6.2-1H3
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_3
3 - To be installed by customers experiencing
the problems corrected.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
None
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 SCSI Drivers on OpenVMS Alpha V6.2. This kit
addresses the following problems:
Problems Addressed in the ALPSCSI08_062
o DKDRIVER, status not returned in IOST1 on shadowset volume
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 Cannot clear write protection
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 Correction to the Behavior of IO$_DIAGNOSE
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.
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 GKDRIVER has a limit of 65535 bytes transfer rate
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 Skipfile works until a fatal error occurs.
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
o Process hang
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 using PKEDRIVER fail with MEDOFL.
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
- [SYS$LDR]SYS$PKWDRIVER.EXE
- [SYS$LDR]SYS$PKZDRIVER.EXE
Problems Addressed in the ALPSCSI07_062
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
%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 When an application (eg. HSZTERM, SMU) does an IO$_DIAGNOSE
command, then that command is canceled. (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.
Problems Addressed in the ALPSCSI06_062 Kit:
1.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 V6.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
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.compaq.com/storage/
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.
1.1.1 Installation Procedure for AlphaServer 4100 Series
Models
If your system is an AlphaServer 4100 series model,
running OpenVMS V6.2-1H3 the following procedures
detail different installation procedures for different
configurations.
1.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.
1.1.1.2 KZPBA adapter already installed
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, may have a machine check when an attempt
is made to install OpenVMS Version 6.2-1H3 before attempting
to install this kit.
This procedure requires that your system have another SCSI
bus that does not use a KZPBA adapter. 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 NOAUTOCONFIG 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.
1.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 V6.2-1H3
with this kit already installed.
1.2 Known Problems
Three known problems exist with the PKQDRIVER in this kit. In
rare instances, each can cause the system to crash. Because they
were discovered late in the testing cycle, the fixes are not
included in this kit. These problems are fixed in OpenVMS V7.2.
It is expected that these problems will also be fixed in OpenVMS
V7.1-2.
1.2.1 INVEXCEPTN Reported While Logging Errors
The UltraSCSI driver, PKQDRIVER, initially specifies an
error log buffer size that is insufficient in some cases.
If PKQDRIVER logs an error which requires a larger buffer
than what exists, it overwrites the header of the next error
log buffer. When another device attempts to log an error
into the buffer whose header is overwritten, the system can
crash. The error message reported is INVEXCEPTN (invalid
exception).
There is no known workaround for this problem. It has been
fixed in OpenVMS V7.2 and is planned to be fixed in OpenVMS
V7.1-2.
1.2.2 INCONSTATE Reported When Interrupts Received Out
of Order
If the UltraSCSI driver, PKQDRIVER, incurs an asynchronous
event error, such as BUS RESET, while awaiting a mailbox
completion interrupt, it bugchecks with the error message,
INCONSTATE (inconsistent I/O database).
There is no known workaround for this problem. It has been
fixed in OpenVMS V7.2 and is planned to be fixed in OpenVMS
V7.1-2.
Problems Addressed in the 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 If a target returns a Queue Full status, an unnecessary
Mount Verification occurs.
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 INCONSTATE crash due to a Qlogic controller error.
o Mount Verify not invoked for some recoverable errors.
Problems Addressed in the ALPSCSI04_062 Kit:
o Get or set volume does not work if CDROM_AUDIO.C is used.
CDROM_AUDIO.C is a sample program in SYS$EXAMPLES which shows
how to use the audio functions supported by DKDRIVER (a SCSI
disk class driver). The program logs CHECK CONDITIONS and
fatal drive errors.
o Mount fails on some devices.
o Some non-Digital disks cannot be accessed by DKdriver due
to "invalid mode sense" errors.
o Tagged Command Queuing cannot be disabled at the drive level.
o The Fujitsu M2512A drive does not work on OpenVMS Alpha.
o Copy/write_check fails to return an error when a known bad
block is written.
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 A problem may occur during configuration of SCSI devices.
o Mount verification occurs repeatedly with no error log
entries to explain why.
o Incorrect access to the mode page value for the WCE bit in the
Caching mode page may occur.
o Miscalculation of the DMA timeout value may occur.
o The maximum usable disk size is 8.6Gb. Disk drives with a
capacity of greater than 8.6 Gb 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 are treated as fatal except
for "data recovered" errors of some types.
o Some recoverable errors were being treated as successful,
which could lead to data corruption.
o Deferred errors leave I/O incomplete and no errors are
reported. This can lead to undetected errors in disk I/O.
o Geometry changes occur during packet acknowledgments packack)
which causes unexpected behavior in serving on OpenVMS clusters.
o Two names and two paths appear for SCSI disks when one side
of a shared bus configures before the other and the MSCP path
to the disk is seen first. This causes problems because when
f$device finds both, host-based RAID does not work, quorum
disks do not function correctly, and the local path is not
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 continues on using the pointers in SCDRP and other structures
as though they are valid. At least one crash has definitely been
traced to this, and several other mysterious crashes may be
related. The result can be pool corruption or, in some cases,
disk corruption.
o POOLCHECK crashes while disks are being mounted.
o A Burns platform (Alphabook 1xxx/4xxx) system disk (IBM DPRS)
is corrupted by INIT commands, by analyze/disk/repair or by
continued use.
o Badblock revectoring delivers incorrect negative block numbers
to the disk to be revectored. This will be rejected, but means
that bad blocks are 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) is incorrectly overwriting the boot block instead of the
block selected.
o IO$_AUDIO function may crash the system.
o Running HSZTERM while heavy I/O occurs results in an
INVEXCEPTN bugcheck in the port driver.
o Third-party archivers and Desktop Backup, which create
non-ANSI tapes, can see SS$_TAPEPOSLOST and SS$_DATAOVERUN
errors when they are positioning the tape.
o Fatal drive errors occur during attempts 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.
o Disks go into Mount Verify and never come out.
o Error log entries have an incorrect format.
o Controller errors occur in systems with greater than 4Gb
of memory.
o Controller errors may occur during one- and two-byte transfers.
o A system crash may occur after a bus reset or adapter errors.
o An RZ74 will not mount if the disk is not already spinning.
o Devices that require longer DMA and disconnect timeouts cannot
be used until a fixed driver is supplied.
o The mechanism for disabling SDTR, which was available in
ALPSCSI02_070, was not documented in that kit.
o Shadow copies and merges involving SCSI-attached disks may
cause a system crash.
Problems Addressed in the ALPSCSI02_070 Kit for OpenVMS Alpha V6.2,
V6.2-1H1, and V6.2-1H2:
o The 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
when a Raid set member fails.
o Premature command timeouts and SCSI bus resets may occur on
SMP systems. Occasionally, the SCSI bus resets will cause
a system crash. 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.
o Preventing SDTR negotiations may crash the system.
o System crashes may intermittently occur due to bugchecks
(INCONSTATE) in PKEdriver when the bus state is unknown.
o Some SCSI 1 devices generate phase errors with the SCSI 2
driver.
o The following DEVICE ERROR may appear in the error log on
Alpha 8400 and 8200 systems with SCSI disks connected to a
KFTIA (ITIOP) IO module:
ENTRY TYPE - Device Error
VMS SCSI Error type - Send SCSI Command Failed
Port status - Unknown Port Status (hex value is 32C)
o PKSDRIVER may crash with a ACCVIO BUG_CHECK when a second SCSI
cluster node boots.
o An insufficient number of queue elements are available 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 An INCONSTATE system crash may occur due to double deallocation
of map registers.
o DIAGNOSE reports unusual error log information for KZPSA
errors.
o The KZPSA takes 6 seconds to initialize. This time could be
reduced.
Problems Addressed in the ALPSCSI01_070 Kit for OpenVMS Alpha V6.2,
V6.2-1H1, and V6.2-1H2:
o A 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 may occur 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.
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 by
PKSDRIVER.
o Device errors may occur on KZPSA devices.
Problems Addressed in the ALPSCSI01_070 Kit for OpenVMS Alpha V6.2,
V6.2-1H1, and V6.2-1H2:
o SCSI $QIO(IO$_DIAGNOSE) for the 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. The system will either
hang or fail to recover from a non-paged pool expansion failure.
Problems Addressed in the ALPSCSI03_062 Kit:
o Random data corruption and adapter/system hangs may occur on
disks attached to KZPSA adapters on systems with 1 Gigabyte
or greater of physical memory.
Adapter/system hangs may occur due to pool consumption problems.
This consumption can be identified from a forced dump by seeing
that MISC and SGMAP registers are consuming pool.
This problem is corrected in OpenVMS Alpha V7.0.
o Nonpaged pool fills up with MISC (SGMAP) data packets in the size
range of 256-319 bytes each. If SYSTEM_CHECK or POOLCHECK is enabled
the SDA> SHOW POOL/STATISTICS will show large number of allocation
failures for the lookaside list of 256 bytes. When nonpaged pool
(NPAGEDYN) fills up, the system could either hang or crash. This
depletion of NPAGEDYN is most noticeable during heavy I/O load, such
as during BACKUP operations.
This problem has been seen on systems with more than 1Gb of memory
and that are using the KZPSA-BB (PCI to FastWideDifferential SCSI
adapter).
This problem is corrected in OpenVMS Alpha V7.0.
Problems Addressed in the 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: This correction resolves the problem described in
Section 4.11.2.3.2 of the OpenVMS V6.2 Release Notes.
This problem is corrected in OpenVMS Alpha V7.0.
o The SYS$PKEDRIVER.EXE in this kit prevents machine checks when
booting a system that has an NCR 53C810 SCSI adapter.
NOTE: 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
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: This information replaces Section 3.34.2.2 in the OpenVMS
V6.2 Release Notes.
This problem is corrected in OpenVMS Alpha V7.0.
INSTALLATION NOTES:
****< 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.
*********************
System should be rebooted after successful installation of this kit
and the new KZPSA-BB firmware. If you have other nodes in your
VMScluster, they should also be rebooted in order to make use of
the new images.
** Installation Procedure for AlphaServer 4100 Series Models **
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 kit first, according to the standard
installation directions. 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 a KZPBA adapter is already installed on your system, Compaq
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.
The following procedure prevents this from happening:
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 NOAUTOCONFIG 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.
o 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.
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.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
alpscsi08_062.README
alpscsi08_062.CHKSUM
alpscsi08_062.CVRLET_TXT
alpscsi08_062.a-dcx_axpexe
alpscsi08_062.CVRLET_TXT
|
