Australia - Updated: 24-SEP-2003
hp.com home products and services support and drivers solutions how to buy
» contact hp
hp.com home hp OpenVMS ECOs

IMPORTANT NOTICE

The online distribution of OpenVMS and related product patches is being migrated to the HP ITRC (Information Technology Resource Center) patch distribution site. The new ITRC patch server will allow OpenVMS customers to take advantage of many enhanced features for patch searching and distribution.

Beginning August 1, 2003, OpenVMS and related Layered Product, publicly available patches will be available from the HP ITRC web site at

http://itrc.hp.com/service/patch/mainPage.do

The same patches will still be available from the existing patch server in Colorado Springs (http://www.support.compaq.com/patches/) through the end of October 2003, to give customers sufficient time to update their bookmarks and make the transition to the HP ITRC web site.

ECO kits will also be available by raw FTP from (ftp://ftp.itrc.hp.com/).

PLEASE UPDATE YOUR BOOKMARKS AND REGISTER ON THE NEW SITE NOW

Note: if you're having trouble connecting to the ITRC site, please delete any cookies for "itrc.hp.com" from your browser and try again. Report any difficulties with or suggestions to MrVMS

» Sydney CSC home page

Navigation
» ECOinfo main index
» Search ECOs
» Search FTP site
» Browse FTP site

ECO Indexes
» Chronological Index
» Indexed by Version
» Indexed by Rating
» Alpha Indexed by Name
» VAX Indexed by Name
» On Hold List

Associated Links
» OpenVMS Home Page
» OpenVMS News
» DIA/WIS Web Service

Feedback
» mail to CSC
.
Sydney Customer Support Centre OpenVMS ECO information
    Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)

ALPCPU0C04_071 Alpha V7.1 CPU Diagnostics Routines ECO Summary

To obtain this kit please call the Customer Support Centre or use the FTP site

Search for this ECO kit and dependencies
Search the Compaq FTP web site this kit (exact match)
Search the Compaq FTP web site this or related ECOs

    
    
    Copyright (c) Compaq Computer Corporation 1998.  All rights reserved.
    
    Modification Date:  25-OCT-1999
    Modification Type:  Added note regarding Dual CPU Card.
    
    PRODUCT:    OpenVMS Alpha
    
    COMPONENT:  CPU Diagnostics Routines
    
    SOURCE:     Compaq Computer Corporation
    
    ECO INFORMATION:
    
         ECO Kit Name:  ALPCPU0C04_071
         ECO Kits Superseded by This ECO Kit:  ALPCPU0C03_071 aka ALPCPUC03_071
                                               ALPCPUC02_071
                                               ALPCPU001_071 aka ALPCPUC01_071
                                               (Only Released Through Factory
                                                Installed Software - FIS)
    
         ECO Kit Approximate Size:  558 Blocks
         Kit Applies To:  OpenVMS Alpha V7.1 through V7.1-1H2
         System/Cluster Reboot Necessary:  Yes
         Rolling Reboot Supported:  No
         Installation Rating:    2 : INSTALL_2
                                     To be installed by customers using the
                                     following features:
    
                                       Turbo-Laser systems with PCI-to-PCI
                                       bridged devices
    
         KIT DEPENDENCIES:
    
            The  following  remedial  kit(s)  must  be  installed   BEFORE
            installation of this kit:
    
              ALPBASE02_071
    
            In order to receive the all the  corrections  listed  in  this
            kit, the following remedial kits should also be installed:
    
              None.
    
    
    ECO KIT SUMMARY:
    
    An ECO kit exists for the CPU Diagnostics Routines on OpenVMS Alpha V7.1
    though V7.1-1H2. This kit addresses the following problems:
    
    Problems Addressed in ALPCPU0C04_071:
    
      o  Although improvements to Scatter/Gather code were made, no
         customer-visible changes were made.  A potential, but so far
         unseen problem was fixed.  Specifically, an extra read of the
         Scatter/Gather maps and a copy of the Scatter/Gather map into
         main memory during shutdown was provided.  In addition,
         changes were made so that any future Scatter/Gather register
         crashes could be more easily debugged.
    
         A call to exe_std$alononpaged could cause the system not to
         boot if it ran out of nonpaged pool.  It was replaced by a
         call to exe_std$alophycntg.  If this call fails, the boot
         proceeds normally, but the Scatter/Gather map is not copied
         from I/O space into the dump during a crash.
    
      o  Two problems discovered by the new C compiler were fixed,
         although neither problem had been reported by customers yet:
    
         1.  A RETURN statement was missing the return value
             SS$_NORMAL.
    
         2.  The variable "ihae" was used when "mhae" was supposed to
              have been used.
    
      o  When booting a Turbo-Laser, if it crashes before the final exec
         initial break point, the user will see a kernel stack not valid
         error.  The reason for the crash was that the copy_sg_map routine
         will access violate if you crash before ioc$init_io_bridge fills
         in the virtual address for the scatter gather map.
    
    
    Problems Addressed in ALPCPUC03_071:
    
      o  A hang condition on OpenVMS V7.1-1H1 occurs during initialization
         of the I/O database.  This hang occurs shortly after the OpenVMS
         banner.  It can be seen on a verbose boot just after the INITIODB
         message.  Issuing a CTRL P (^P) to pause the console is ineffective
         during the hang.
    
    
    Problems Addressed in ALPCPUC02_071 ECO:
    
      o  CRD errors on the Turbo Laser 4GB memory module (TMEM4) always
         contain zero in the failing string register.   A hardware
         problem in the TMEM4 causes a failure to report the correct
         failing string on CRD errors.  The inability to determine the
         correct failing string prevents DECEVENT from determining the
         failing memory SIMM.
    
      o  After the installation of a dual CPU card, the cards are not seen
         by the operating system or when the DCL 'SHOW CPU/ACTIVE' command
         is executed.
    
         NOTE:  It is also important to insure that ALL CPU modules are at
                similar revisions so that they all have the same version
                of the Alpha chip.
    
    
    Problems Addressed in ALPCPU001_071:
    
      o  SMPSTART_MIXEDCPU has been added to the Turbo Laser Link file
         so that it will link in the new SMPSTART_MIXEDCPU module which
         contains code patches to allow mixing of EV5/EV6 and mixed CPU
         passes.
    
    
    RELATED ARTICLES:
    
    Detailed articles describing the problems listed above may exist in
    the OPENVMS database.  To view these articles, open the appropriate
    product database and perform a query using either of the following
    search strings: 'ALPCPU0C04_071,' 'ALPCPU0C0,' 'ALPCPU0C,' 'ALPCPUC,'
    or 'ALPCPU'.
    
    
    ECO KIT ORDERING INSTRUCTIONS:
    
    If after an evaluation you wish to obtain this kit, request it
    electronically using the appropriate Advanced Electronic Services
    (AES) Service Tool.  If you are not familiar with how to request
    kits electronically, open the DIA, WIS or DSNLINK database and
    review the article entitled:
    
         [AES] How To Electronically Request ECO Kits Using Service Tools
    
    
    INSTALLATION NOTES:
    
    This kit cannot be booted from a user prompt because it contains  a
    fix  for a problem that prevents OpenVMS from booting.  The problem
    occurs when devices that use PCI-to-PCI bridged devices are used on
    Turbo-Laser   systems.    To  correct  this  problem,  perform  the
    following steps:
    
      o  Remove the devices from the system.
    
              *  the PCI-PCI devices for a Turbo-Laser system are:
    
                  -  ATM350
    
                  -  KZPDA
    
      o  Reboot the system
    
      o  Use the the VMSINSTAL utility to install the TIMA kit.
    
          -  log into the SYSTEM account and type the following  at  the
             DCL prompt:
    
             @SYS$UPDATE:VMSINSTAL ALPCPUC03_071 [saveset location]
    
             The saveset  location  may  be  a  tape  drive  or  a  disk
             directory that contains the kit saveset.
    
      o  Shut down the system.
    
      o  Re-install the PCI-PCI devices
    
      o  Re-boot the system
    
    The images in this kit will not take effect until the system is rebooted.
    
    The fix only applies to TurboLaser systems with PCI-to-PCI  bridged
    devices installed in them.  If you have other TurboLaser nodes with
    these devices in your OpenVMS cluster, they must also  be  rebooted
    in  order  to  make  use  of  the  new image(s).  If the Turbolaser
    systems do not use a shared system  disk,  before  each  system  is
    rebooted, the above installation procedure must be performed.
    
    As an alternative to removing the PCI-to-PCI bridged  devices,  you
    can install the TIMA saveset to the destination disk from a working
    system.  To do this, the destination disk must be a shared disk  or
    be  manually  relocated  from the destination system to the working
    system for installation purposes.
      
      ==========================================================================
      |                     Table of Kit Image Information                     |
      +----------------------------+----------+-----------------+--------------+
      |                            | Overall  | Image File      | Image Link   |
      | Image Name                 | Checksum | Identification  | Date/Time    |
      +----------------------------+----------+-----------------+--------------+
      | SYS$CPU_ROUTINES_0C05.EXE  | FAF82D17 | X-5             |  8-SEP-1998  |
      |                                       |                 | 12:53:31.94  |
      +----------------------------+----------+-----------------+--------------+
    
privacy statement using this site means you accept its terms feedback to the webmaster
VMS rules VMS rocks OpenVMS rules OpenVMS rocks