Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
ALPSCSI08_062 Alpha V6.2 SCSI ECO Summary
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.
|
