OpenVMS VAXPHV04_061 VAX V6.1 Ethernet Drivers ECO Summary

 
NOTE:  An OpenVMS saveset or PCSI installation file is stored
       on the Internet in a self-expanding compressed file.
       The name of the compressed file will be kit_name-dcx_vaxexe
       for OpenVMS VAX or kit_name-dcx_axpexe for OpenVMS Alpha.
 
       Once the file is copied to your system, it can be expanded
       by typing RUN compressed_file.  The resultant file will
       be the OpenVMS saveset or PCSI installation file which
       can be used to install the ECO.
 
Copyright (c) Digital Equipment Corporation 1994, 1996. All rights reserved.

OP/SYS:     OpenVMS VAX

COMPONENT:  Ethernet Drivers
              ECDRIVER
              EFDRIVER
              EPDRIVER
              ESDRIVER
              ETDRIVER
              EXDRIVER
              EZDRIVER
              FCDRIVER
              FQDRIVER
              FXDRIVER
              NET$CSMACD
              NET$FDDI
              XEDRIVER
              XQDRIVER

SOURCE:     Digital Equipment Corporation

ECO INFORMATION:

     ECO Kit Name:  VAXPHV04_061
     ECO Kits Superseded by This ECO Kit:  VAXPHV03_061
                                           VAXPHV02_061 (CSCPAT_0608)
                                           VAXPHV01_061
     ECO Kit Approximate Size:  1062 Blocks
     Kit Applies To:  OpenVMS VAX V6.1
     System/Cluster Reboot Necessary:  Yes
     Installation Rating:  3 - To be installed on all systems running
                               the listed versions of OpenVMS which
                               are experiencing the problems described.

     NOTE:  In order to receive the full fixes listed in this kit,
            the following remedial kits also need to be installed:

                 None.  



ECO KIT SUMMARY:

An ECO (patch) kit exists for Ethernet Drivers on OpenVMS VAX V6.1
only.  This kit addresses the following problems:

Problems addressed in the VAXPHV04_061 kit:

  o  A fix to cure a minor memory leak exposed a more severe
     problem, double deallocation of pool, resulting generally 
     in a system crash.  This kit removes the memory leak fix.


Problems addressed in the VAXPHV03_061 kit:

  o  If an FDDI driver is not fully enabled with respect to
     DECnet-OSI, any attempts to access non-existent DECnet-OSI
     network management data structures will crash the system.
     This typically occurs when an event is reported by the FDDI
     driver.

     This problem is corrected in OpenVMS VAX V6.2.

  o  A system crash may occur during the deletion of a LAT link
     from LATCP when the device is shutting down to perform a
     normal reset.  The system crash occurs in FQDRIVER or FCDRIVER.

  o  A system crash may occur in NET$FDDI during the processing
     of a set station directive as a result of a DECnet-OSI NCL
     command.

  o  A system crash may occur at NET$FDDI+50DD during shutdown
     startup when an attempt is made to access an FDDI network
     management data structure that does not exist.  It is
     possible for a DECnet-OSI user to create an FDDI station
     with CSMACD Network Management data structures.

  o  Allocating a local data structure and overwriting existing
     pointers causes 106 bytes of memory to be "lost" when the
     last user of the port is deleted.

  o  A system crash may occur during startup at NET$FDDI+51CD when  
     multiple FDDI adapters are installed on the system.

  o  On restart there is a very small window where a command could
     be completed while the driver state is 'resetting'.  The
     driver does not allow the "resetting" state and it should.
     The system crash occurs at FXDRIVER+0F07.

  o  The FXDRIVER driver inadvertently causes a DEMFA failure by
     issuing a transmit with a zero-length segment which causes the
     the DEMFA to halt with a fatal error.

  o  When FXDRIVER is doing error recovery, it returns success for
     transmit requests without returning the buffer.  This results
     in loss of the transmit buffer.  It should complete the
     transmit with error status and return the buffer.

  o  A machine check may occur on a Q-BUS system with a DEFQA
     FDDI controller installed.  The bugcheck reason is reported
     as an ASYNCWRTER, Asynchronous write memory failure.


Problems addressed in the VAXPHV02_061 kit:

  o  Clarifications were made to the documentation in the
     VAXPHV01_061 Kit.


Problems addressed in the VAXPHV01_061 kit:

  o  Remote Console connection to a DECbridge 90 with NCP
     may fail when showing port information.  A "Target
     does not respond" message will be displayed.  This
     failure only occurs when NCP is directed to use an
     FDDI device to connect to the DECbridge 90 on the
     Ethernet.


INSTALLATION NOTES:

In order for the corrections in this kit to take effect, the system
must be rebooted.  If the system is a member of a VAXcluster, the
entire cluster should be rebooted.

Colorado Site
Georgia Site

vaxphv04_061.README
vaxphv04_061.CHKSUM
vaxphv04_061.CVRLET_TXT
vaxphv04_061.a-dcx_vaxexe