Jump to page titleUNITED STATES
hp.com home products and services support and drivers solutions how to buy
» contact hp


more options
 
hp.com home
End of Jump to page title
HP Services software patches
Jump to content


» software & drivers
» ask Compaq
» reference library
» forums & communities
» support tools
» warranty information
» contact support
» parts
» give us feedback

associated links
» what's new
» contract access
» browse patch tree
» search patch tree
» join mailing list

patches by topic
» DOS
» OpenVMS
» Security
» Tru64 Unix
» Ultrix 32
» Windows
» Windows NT

connection tools
» nameserver lookup
» traceroute
» ping


Find Support Information and Customer Communities for Presario.
Content starts here
OpenVMS VMS731_FIBRE_SCSI-V0200 Alpha V7.3-1 FibreChannel/SCSI ECO Summary
TITLE: OpenVMS VMS731_FIBRE_SCSI-V0200 Alpha V7.3-1 FibreChannel/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.pcsi-dcx_axpexe or
       kitname.pcsi-dcx_vaxexe, then it can be expanded by typing
       RUN kitname.pcsi-dcx_axpexe or kitname.pcsi-dcx_vaxexe.  The
       resultant file will be the PCSI installation file which can be
       used to install the ECO.
 


New Kit Date:       17-MAR-2003
Modification Date:  Not Applicable
Modification Type:  NEW KIT

Copyright (c) Compaq Computer Corporation 2001,2002,2003.  All rights reserved.

OP/SYS:     OpenVMS Alpha

COMPONENT:  FibreChannel
            SCSI Drivers

SOURCE:     Compaq Computer Corporation

ECO INFORMATION:

     ECO Kit Name:   VMS731_FIBRE_SCSI-V0200
                     DEC-AXPVMS-VMS731_FIBRE_SCSI-V0200--4.PCSI
     ECO Kits Superseded by This ECO Kit: VMS731_FIBRE_SCSI-V0100
     ECO Kit Approximate Size:  5120 Blocks
     Kit Applies To:  OpenVMS Alpha V7.3-1
     System/Cluster Reboot Necessary:  Yes
     Rolling Re-boot Supported:  Yes
     Installation Rating:  INSTALL_2
                           2 - To  be  installed  by   all  customers  using  the  following
		               feature(s):
	
        		       Fibre Channel or SCSI devices.

     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 FibreChannel and SCSI Drivers on OpenVMS Alpha
V7.3-1.  This kit addresses the following problems:


PROBLEMS ADDRESSED IN VMS731_FIBRE_SCSI-V0200 KIT


      o  Shortly after the first OpenVMS boot message is displayed, a
         system can hang when booting from a Fibre Channel disk, that is
         on an Arbitrated Loop.

         Images Affected:[SYS$LDR]SYS$PGADRIVER.EXE


      o  FibreChannel storage (DG) disks fail over to the MSCP path due
         to the local direct paths becoming permanently inaccessible.

         Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE


      o  A system with an LP89802 can crash with the following error.

         Crashdump Summary Information:
         ------------------------------
         Bugcheck Type:     MACHINECHK, Machine check while
                            in kernel mode
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.80011690
                            EXE$SYSTEM_CORRECTED_ERROR_C+00510
         Failing PS:        20000000.00001F04
         Module:            SYS$CPU_ROUTINES_270F
                            (Link Date/Time: 20-NOV-2002 15:11:40.36)
         Offset:            00003690

         Failing Instruction:
         EXE$SYSTEM_CORRECTED_ERROR_C+00510:     BUGCHK

         Stack Pointers:
         KSP = FFFFFFFF.F0819C60   ESP = FFFFFFFF.F081B000
         SSP = FFFFFFFF.F0805000   USP = FFFFFFFF.F0805000

         Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE


      o  FibreChannel storage fails to configure on boot.

         Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE


      o  If a fibre channel device is power cycled or disconnected from
         the fabric, OpenVMS may permanently lose access to the device.

         Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE




      o  This kit provides a utility that will allow customers to update
         the firmware in an MSA1000 series Fibre SCSI raid controller.
         The utility can also do some diagnostics.

         Images Affected:[SYSHLP.UNSUPPORTED]MSA_UTIL.EXE


      o  I/O to one or more disks may stall with the following symptoms:

          o  WBEM$CPQSTORE (or any other process issuing an IO$_DIAGNOSE
             request) has a busy channel to a DGA device.

          o  The first IO on the port I/O queue to this disk on the
             current path is shown as a:  wrttmkr func,physio,extend IO
             in SDA> SHOW DEV DGAx

          o  The SCSI port descriptor (SPDT), for the Fibre Channel
             adapter of the current path to the disk, shows Total
             Outstanding I/Os and Curr I/Os On All ports to be nnn (
             SDA> CLUE SCSI/PORT= ), where nnn is any number
             greater than 0.

          o  Other processes trying to access any disk via this Fibre
             Channel port seem to hang.  An associated symptoms may be
             that no new logins are possible (access to SYSUAF and/or
             RIGHTSLIST hangs).

          o  The Fibre Channel adapter ring buffer shows mostly
             'WatchDog End' and 'WatchDog Beg' events, but no Read/WRITE
             IOCB events.


         Images Affected:[SYS$LDR]SYS$PGADRIVER.EXE



      o  DIR-E-TAPEPOSLOST errors when can occur when a DIRECTORY
         command is used on skip-filemark-capable tape drives.

         Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE



      o  A request can complete with a transferred-byte-count of up to
         511 bytes more than were requested.  The effect of this bug is
         application-dependent but has been seen to cause repeated
         PEDRIVER port initializations.

         Images Affected:[SYS$LDR]SYS$DKDRIVER.MAR



      o  A system can hang when backing up files to and SDLT with V35 or
         V46 firmware.

         Crashdump Summary:
         ------------------
         Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.80047904 
                            EXE_STD$QUEUE_FORK_C+00084
         Failing PS:        20000000.00001504
         Module:            SYSTEM_PRIMITIVES_MIN
         Offset:            0001B904


         Images Affected:[SYS$LDR]SYS$PKWDRIVER.EXE




      o  An 8MM tape unit, like a TKZ9E-SW, will log an error during
         driver initialization.

         Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE



      o  

         1.  It is possible for a command retry to fail with a bad
             status but a non-zero byte count of more or less data than
             it asked for.  The problem is that the SCDRP$L_TRANS_BCNT
             field was not being zeroed prior to every command being
             issued.

         2.  When an other-than-perfect FastPath command completes, it
             posts a transferred-byte count of SCDRP$L_BCNT.  This
             allows it use the stale byte count described in item 1.
             Even when the command completes successfully, this code
             lets the request complete with the pad byte count in it,
             causing it to report up to 511d more bytes than were
             requested.


         Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
			 [SYS$LDR]SYS$FGEDRIVER.EXE
			 [SYS$LDR]SYS$PKQDRIVER.EXE
			 [SYS$LDR]SYS$PGADRIVER.EXE



      o  A customer who uses the USERD1 SYSGEN parameter may see debug
         output.

         Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
			 [SYS$LDR]SYS$FGEDRIVER.EXE
			 [SYS$LDR]SYS$PKQDRIVER.EXE
			 [SYS$LDR]SYS$PGADRIVER.EXE


      o  When restoring a multivolume saveset created with a command
         similar to the following BACKUP command:

         $ MOUNT/FOREIGN ALPHA3$MKD0:
         $ BACKUP/IMAGE SY2:ALPHA3$MKD0:SY2_IMG/save_set/EXACT_ORDER

         The restore operation fails because BACKUP is requesting and
         waiting for the wrong tape to be loaded.

         Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE


      o  The system can crash with a fatal INCONSTATE bugcheck at
         SYS$PGADRIVER+0A7F4

         Crashdump Summary Information
         -----------------------------

         Bugcheck Type:     INCONSTATE, Inconsistent I/O
                            data base
         Current Process:   NULL
         Current Image:     
         Failing PC:        FFFFFFFF.804067F4
                            SYS$PGADRIVER+0A7F4
         Failing PS:        08000000.00000804
         Module:            SYS$PGADRIVER (Link Date/Time:
                            13-NOV-2002 10:01:38.48)
         Offset:            0000A7F4

         Stack Pointers:
         KSP = FFFFFFFF.8131B7C8   ESP = FFFFFFFF.93EB1000
         SSP = FFFFFFFF.93EAB000   USP = FFFFFFFF.93EAB000


         Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
			 [SYS$LDR]SYS$PGADRIVER


PROBLEMS ADDRESSED IN VMS731_FIBRE_SCSI-V0100 KIT


     o  A system can crash with a INVEXCEPTN, Exception while above
        ASTDEL bugcheck.

        Crashdump Summary Information
        -----------------------------
        Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
        Current Image:     $1$DGA510:[PRG]LPARTREQ.EXE;6
        Failing PC:        FFFFFFFF.80405E60
                           SYS$PGADRIVER+0BE60
        Failing PS:        38000000.00000804
        Module:            SYS$PGADRIVER (Link Date/Time:
                           24-AUG-2001 00:12:20.64)
        Offset:            0000BE60


         Images Affected:[SYS$LDR]SYS$PGADRIVER.EXE



     o  As a result of mount verification on SCSI tapes, the fastskip
        algorithm could be inadvertently turned off.

         Images Affected:[SYS$LDR]SYS$MKDRIVER.EXE


     o  The user will see unnecessary console messages from FGEDRIVER.

         Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE


     o  A system can crash with an INVEXCEPTN bugcheck.

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     INVEXCEPTN, Exception while above
                           ASTDEL
        Current Process:   STACONFIG
        Current Image:     STACONFIG.EXE
        Failing PC:        FFFFFFFF.80029F14
                           IOC$DEALLOC_CNT_RES_NOSYNC_C+00154
        Failing PS:        20000000.00000B04
        Module:            SYSTEM_PRIMITIVES_MIN (Link Date/Time:
                           28-MAR-2002 14:22:47.68)
        Offset:            00001F14

          Images Affected:[SYS$LDR]SYS$PKQDRIVER.EXE



     o  Paths to FibreChannel disks can become permanently unavailable
        without notification to the user and without any error log
        entries being written.

          Images Affected:[SYS$LDR]SYS$FGEDRIVER
   		          [SYS$LDR]SYS$PGADRIVER



     o  Disk drives that support the SCSI-3 SPC3 standard cannot be
        mounted.  When an attempt is made to mount such drives the
        error log records "invalid inquiry" messages.

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE


     o  When using FC$SDA to examine the FCP ring buffer, if the
        request was sent FastPath, the FC-LA field is always 0, which
        is an invalid value for FC-LA.

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
			  [SYS$LDR]SYS$MKDRIVER.EXE
			  [SYS$LDR]SYS$GKDRIVER.EXE
			  [SYS$LDR]SYS$PKRDRIVER.EXE
			  [SYS$LDR]SYS$FGEDRIVER.EXE
			  [SYS$LDR]SYS$PGADRIVER.EXE
			  [SYSLIB]FC$SDA.EXE


     o  During a hard reset the system can experience 64-byte LAL
        corruption or an ACCVIO system crash.

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
			  [SYS$LDR]SYS$MKDRIVER.EXE
			  [SYS$LDR]SYS$GKDRIVER.EXE
			  [SYS$LDR]SYS$PKRDRIVER.EXE
			  [SYS$LDR]SYS$FGEDRIVER.EXE
			  [SYS$LDR]SYS$PGADRIVER.EXE
			  [SYSLIB]FC$SDA.EXE


     o  When using FC$SDA to display STDTs, some useful fields (such as
        the new Queue Full handling cells and the target reset count)
        are missing.  Also, FC$SDA has no support for an FC STDT /ALL
        command.

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
 			  [SYS$LDR]SYS$MKDRIVER.EXE
			  [SYS$LDR]SYS$GKDRIVER.EXE
			  [SYS$LDR]SYS$PKRDRIVER.EXE
			  [SYS$LDR]SYS$FGEDRIVER.EXE
			  [SYS$LDR]SYS$PGADRIVER.EXE
			  [SYSLIB]FC$SDA.EXE


     o  The system can crash with a LOCKMGRERR, Error detected by Lock
        Manager bugcheck.

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     LOCKMGRERR, Error detected by Lock Manager
        Current Process:   NULL
        Current Image:     
        Failing PC:        FFFFFFFF.802F4148    
                           LCK$RCV_RM_BXFER_C+001F8
        Failing PS:        18000000.00000804
        Module:            SYS$CLUSTER   (Link Date/Time:  
                           4-MAR-2002 15:21:35.69)
        Offset:            0001C148

        Failing Instruction:
        LCK$RCV_RM_BXFER_C+001F8:       BUGCHK


        R0  =  00000000.00002044   %SYSTEM-F-INSFSPTS,
               insufficient SPTEs available

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
			 [SYS$LDR]SYS$MKDRIVER.EXE
			 [SYS$LDR]SYS$GKDRIVER.EXE
			 [SYS$LDR]SYS$PKRDRIVER.EXE
			 [SYS$LDR]SYS$FGEDRIVER.EXE
			 [SYS$LDR]SYS$PGADRIVER.EXE
			 [SYSLIB]FC$SDA.EXE



     o  The System can crash with an INVEXCEPTN at SYS$FGEDRIVER+177E0.
        (ERS$PLOGI_IND+3E0)

        Crashdump Summary Information:
        ------------------------------
        Bugcheck Type:     INVEXCEPTN, Exception while above ASTDEL
        Current Process:   NULL
        Current Image:     
        Failing PC:        FFFFFFFF.804157E0  SYS$FGEDRIVER+177E0
        Failing PS:        18000000.00000804
        Module:            SYS$FGEDRIVER    (Link Date/Time:
                           18-SEP-2002 10:30:49.38)
        Offset:            000177E0

        Failing Instruction:
        SYS$FGEDRIVER+177E0:  LDQ_U  R19,#X001C(R1)


          Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE



     o  Data underflow on Fast Path IO will cause SS$_NOTQUEUED errors
        to be logged, and cause a visible mount verification.

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE


     o  The user may see frequent mount verifications.  These can have
        several causes:

          -  Frequent quorum disk mount verification can occur when the
             quorum disk has a relatively heavy I/O load applied to it.
             This is not a problem when the quorum disk is used as
             recommended,meaning with no significant I/O load.  However,
             in some customer clusters this recommendation is ignored.

          -  Frequent TX/RX DMA failures can occur which result in mount
             verifications.

          Images Affected:[SYS$LDR]SYS$DKDRIVER.EXE
    			  [SYS$LDR]SYS$FGEDRIVER.EXE
			  [SYS$LDR]SYS$PGADRIVER.EXE


     o  If the system can not allocate a KPB for a Fast Path IO, an IO
        may not finish, putrtjgthe disk ina Mountverify state.

          Images Affected:[SYS$LDR]SYS$PKQDRIVER.EXE
			 [SYS$LDR]SYS$PKADRIVER.EXE



     o  During system boot, fibre channel storage devices may not be
        configured.

          Images Affected:[SYS$LDR]SYS$FGEDRIVER.EXE
                	  [SYS$LDR]SYS$PGADRIVER.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 INSTRUCTION:

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 VMS731_FIBRE_SCSI /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


Special Installation Instructions:

     o  Scripting of Answers to Installation Questions

        During installation, this kit will ask and require user
        response to several questions.  If you wish to automate the
        installation of this kit and avoid having to provide responses
        to these questions, you must create a DCL command procedure
        that includes the following definitions and commands:

           -  $ DEFINE/SYS NO_ASK$BACKUP TRUE

           -  $ DEFINE/SYS NO_ASK$REBOOT TRUE

           -  Add the following qualifiers to the PRODUCT INSTALL
              command and add that command to the DCL procedure.

                /PROD=DEC/BASE=AXPVMS/VER=V2.0


           -  De-assign the logicals assigned

        For example, a sample command file to install the
        VMS731_FIBRE_SCSI-V0200 kit would be:

          $
          $ DEFINE/SYS NO_ASK$BACKUP TRUE
          $ DEFINE/SYS NO_ASK$REBOOT TRUE
          $!
          $ PROD INSTALL VMS731_FIBRE_SCSI/PROD=DEC/BASE=AXPVMS/VER=V2.0
          $!
          $ DEASSIGN/SYS NO_ASK$BACKUP
          $ DEASSIGN/SYS NO_ASK$REBOOT
          $!
          $ exit


All trademarks are the property of their respective owners.


Files on this server are as follows:
»dec-axpvms-vms731_fibre_scsi-v0200--4.README
»dec-axpvms-vms731_fibre_scsi-v0200--4.CHKSUM
»dec-axpvms-vms731_fibre_scsi-v0200--4.pcsi-dcx_axpexe
privacy statement using this site means you accept its terms