Updated: 24-SEP-2003 (Use your browsers' Reload button to ensure you're viewing the most recent version)
VMS722_PTHREAD-V0100 Alpha V7.2-2 PTHREAD ECO Summary
*OpenVMS] VMS722_PTHREAD-V0100 Alpha V7.2-2 PTHREAD ECO Summary
New Kit Date: 24-SEP-2002
Modification Date: Not Applicable
Modification Type: NEW KIT
Copyright (c) Compaq Computer Corporation 2002. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: PTHREAD
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS722_PTHREAD-V0100
DEC-AXPVMS-VMS722_PTHREAD-V0100--4.PCSI
ECO Kits Superseded by This ECO Kit: None
ECO Kit Approximate Size: 1376 Blocks
Kit Applies To: OpenVMS Alpha V7.2-2
System/Cluster Reboot Necessary: No
Rolling Re-boot Supported: Information Not Available
Installation Rating: INSTALL_3
3 - To be installed by customers
experiencing the problems corrected.
Kit Dependencies:
The following remedial kit(s), or later, must be installed BEFORE
installation of this kit:
VMS722_UPDATE-V0100
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 PTHREAD on OpenVMS Alpha V7.2-2. This kit addresses the
following problems:
PROBLEMS ADDRESSED IN VMS722_PTHREAD-V0100 KIT
o The threads library has an abstraction called a Virtual
Processor (VP) for each CPU being used. A given VP can be
executing code at normal or at interrupt level. A flag keeps
track of which, so that certain nested interrupt operations
can be properly handled. This flag can be improperly cleared,
which can cause a context switch to occur in what should have
been an atomic update.
The problem is seen as a process hang at AST level, while one
of the internal null threads is hibernating. This could only
happen on a multi-processor system, in an application with use
of upcalls and multiple kernel threads enabled, under rare
timing conditions.
Images Affected:[SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
o The EXEC and the threads library implement a protocol which
uses shared memory to control when the EXEC can interrupt the
library with an upcall. Certain upcalls may be interrupted by
other upcalls. An accumulator is used to keep track of
nesting. This accumulator only allows 32 levels of nesting.
Normally this is plenty. However, under certain conditions,
activity in a null thread can go deeper than this. When this
happens, the threads library state gets confused and the
process can be terminated. The usual termination is a
DECthreads bugcheck which reports "selected a non-ready
thread" with a negative ID number in the blocked state. This
can only happen when use of upcalls and multiple kernel
threads are enabled on a multi-processor system.
Images Affected:[SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
o On multi-processor systems, the EXEC uses the Inner-Mode
Semaphore (IMS) to serialize execution of many system
services. Upcalls are used to allow the threads library to
execute one thread while another is blocked waiting for the
IMS. The services which the threads library uses to switch
threads are themselves users of the IMS. Under certain
conditions, the result is recursion of IMS-free upcalls. If
the recursion persists long enough, a stack overflow can occur
in a null thread which terminates the process. This can only
happen on a multi-processor system when use of upcalls and
multiple kernel threads are enabled.
Images Affected:[SYSLIB]PTHREAD$RTL.EXE
[SYSLIB]PTHREAD$DBGSHR.EXE
RELATED ARTICLES:
Detailed articles describing the problems listed above may exist in the
OPENVMS database(s). To view these articles, open the appropriate product
database and perform a query using either of the following search strings:
'VMS722_PTHREAD-V0100' or 'VMS722_PTHREAD'.
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:
No reboot is necessary after successful installation of the kit.
INSTALLATION INSTRUCTIONS:
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 VMS722_PTHREAD /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
- Add the following qualifiers to the PRODUCT INSTALL
command and add that command to the DCL procedure.
/PROD=DEC/BASE=AXPVMS/VER=V1.0
- De-assign the logicals assigned
For example, a sample command file to install the
VMS722_PTHREAD-V0100 kit would be:
$
$ DEFINE/SYS NO_ASK$BACKUP TRUE
$!
$ PROD INSTALL VMS722_PTHREAD/PROD=DEC/BASE=AXPVMS/VER=V1.0
$!
$ DEASSIGN/SYS NO_ASK$BACKUP
$!
$ exit
All trademarks are the property of their respective owners.
==========================================================================
| Table of Kit Image Information |
+----------------------------+----------+-----------------+--------------+
| | Overall | Image File | Image Link |
| Image Name | Checksum | Identification | Date/Time |
+----------------------------+----------+-----------------+--------------+
| PTHREAD$DBGSHR.EXE | DC91FB92 | V3.15-270 | 24-JUL-2002 |
| | | 14:13:01.55 |
+----------------------------+----------+-----------------+--------------+
| PTHREAD$RTL.EXE | 07A990A7 | V3.15-270 | 24-JUL-2002 |
| | | 14:12:53.10 |
+----------------------------+----------+-----------------+--------------+
|
