OpenVMS VMS712_SYS-V0300 Alpha V7.1-2 System Component ECO Summary
TITLE: OpenVMS VMS712_SYS-V0300 Alpha V7.1-2 System Component ECO Summary
Modification Date: 30-JAN-2001
Modification Type: Updated Kit: Supersedes VMS712_SYS-V0200
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-dcx_axpexe.pcsi, then it can
be expanded by typing RUN kitname-dcx_axpexe.pcsi. The resultant
file will be the PCSI installation file which can be used to install
the ECO.
Copyright (c) Compaq Computer Corporation 2001. All rights reserved.
OP/SYS: OpenVMS Alpha
COMPONENT: System Components
SOURCE: Compaq Computer Corporation
ECO INFORMATION:
ECO Kit Name: VMS712_SYS-V0300
DEC-AXPVMS-VMS712_SYS-V0300--4.PCSI
ECO Kits Superseded by This ECO Kit: VMS712_SYS-V0200
VMS712_SYS-V0100
ECO Kit Approximate Size: 10,096 Blocks
Kit Applies To: OpenVMS Alpha V7.1-2
System/Cluster Reboot Necessary: Yes
Rolling Re-boot Supported: Yes
Installation Rating: INSTALL_1
1 - To be installed on all systems running
the listed version(s) of OpenVMS.
Kit Dependencies:
The following remedial kit(s) must be installed BEFORE
installation of this kit:
VMS712_UPDATE-V0300
VMS62TO71U2_PCSI-V0200
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 system components on OpenVMS Alpha V7.1-2. This
kit addresses the following problems:
Problems Addressed In VMS712_SYS-V0300:
o After installation of the VMS712_SYS-V0200 kit and then
re-booting, the system version is changed to V7.2-1. This can
be seen if a SHOW SYSTEM command is issued after re-boot.
o The following problem was corrected in the VMS712_SYS-V0200
kit but was undocumented.
A sychronization issue in handling ASTs within the CLUSTER_SERVER
process can result in process hangs and errors while using SYSMAN.
Processes may hang in RWAST state while doing cluster-wide functions.
SYSMAN may fail with SYSTEM-F-UNREACHABLE errors.
Images Affected: [SYS$LDR]SYS$CLUSTER.EXE
Problem Addressed In VMS712_SYS-V0200:
o OpenVMS Alpha systems may crash with a DOUBLDEALO bugcheck at
EXE$DEALLOCATE_C+00108 in $BRKTHRU.
Images Affected: [SYS$LDR]SYS$CLUSTER.EXE
o Queue and other cluster-wide operations fail with SS$_BADPARAM
when a COE-baselevel node when a COE-baselevel node is in the
cluster.
Images Affected: [SYS$LDR]SECURITY.EXE
o A process is not able to join the default domain within a
$GETLKI system service call, and the error SS$_RSDMNOTFOU is
returned. Affected layered products include Rdb, DECedi, and
others.
Images Affected: [SYS$LDR]LOCKING.EXE
o A system crash occurs with a KRNLSTACKNV bugcheck during heavy
disk I/ O activity, such as BACKUP.
Images Affected:
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.EXE
- [SYS$LDR]IO_ROUTINES.STB
- [SYS$LDR]IO_ROUTINES_MON.STB
o A shadow merge occurs as a result of the pagefile not closing.
During reboot, the system attempts to mount the disk where the
pagefile is located and the following error message displays:
%MOUNT-I-REBUILD, volume was improperly dismounted;
rebuild in progress
Because the system is shadowed, the re-build and a shadow
merge occur.
Images Affected:
- [SYS$LDR]SYS$VM.EXE
- [SYS$LDR]IO_ROUTINES.EXE
- [SYS$LDR]IO_ROUTINES_MON.EXE
- [SYSEXE]OPCCRASH.EXE
o Single CPU OpenVMS Alpha systems may not interact properly
with SCH$GQ_PFWQ, which result in the following occurrences:
- Processes may get stuck in CUR on the PFW queue and not
execute, or
- Processes may get stuck in PFW on the PFW queue and not
execute, or
- The PFW queue may merge with a COM queue, usually
resulting in an INCON_SCHED bugcheck, or
- An INVEXCEPTN at SCH$QEND_C+38 may occur when trying to
access the cell CTL$GL_REPORT_USER_FAULTS.
These problems will not occur on multi-processor systems.
Images Affected: [SYS$LDR]SYS$VM.EXE
o A synchronization issue in handling ASTs within the CLUSTER_SERVER
process can result in process hangs and errors while using SYSMAN.
Processes may hang in RWAST state while doing cluster-wide functions.
SYSMAN may fail with SYSTEM-F-UNREACHABLE errors.
Problem Addressed In VMS712_SYS-V0100:
o A BASIC application terminates abnormally with a BAS$_PROLOSSOR,
DEVFOREIGN or ACCVIO status. An AST (asynchronous system trap)
delivery stack frame was in the process of being torn down while
a saved FP (frame pointer) still pointed to it. This caused BASIC
RTL routines, which follow call chains, to terminate with error
statuses.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o MFPR_xxx and MTPR_xxx PALcode instructions leave registers R1,
R16 and R17 with unpredictable results. These registers were
not always saved and restored in ASTDEL_STACK.M64. Although
corruptions of these registers have not been known to happen,
the potential is there, particularly on newer platforms.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o During a system boot with SYSTEM_CHECK set to 0 and with XFC
(Extended File Cache) loaded (VCC_FLAGS = 2), a system could
crash.
Images Affected: [SYS$LDR]MESSAGE_ROUTINES.EXE
o Attempting to run a program linked to /DEBUG results in an
ACCVIO. The program will fail with an improperly handled
condition error. It does not get to the DBG> prompt.
Images Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE
o The system can crash with an INVSECURESTATE, Invalid state
detected by SECURITY subsystem, at NSA$FREE_RIGHTS_CHAIN_C+0004C /
SECURITY+0000A58C. See crash dump summary below:
Crash dump Summary Information:
------------------------------
Crash Time: 20-JUL-1999 10:12:19.18
Bugcheck Type: INVSECURESTATE, Invalid state detected by
SECURITY subsystem
Node: OAK (Cluster)
CPU Type: DEC 7000 Model 720
VMS Version: V7.2
Current Process: _LTA6788:
Current Image: DSA0:[SYS0.SYSCOMMON.][SYSEXE]DSM.EXE
Failing PC: FFFFFFFF.8018E58C NSA$FREE_RIGHTS_CHAIN_C+0004C
Failing PS: 20000000.00000203
Module: SECURITY (Link Date/Time: 16-DEC-1998
11:52:52.40)
Offset: 0000A58C
Boot Time: 19-JUL-1999 15:22:52.00
System Uptime: 0 18:49:27.18
Crash/Primary CPU: 01/00
System/CPU Type: 0302
Saved Processes: 8
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 768 MByte (98304 PFNs, contiguous memory)
Press RETURN for more.
SDA>
Images Affected:
- [SYS$LDR]SECURITY.EXE
- [SYS$LDR]]SECURITY_MON.EXE
o A DECthread may hang waiting for an event flag upcall.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o A kernel thread may deadlock waiting for the inner mode
semaphore when, in fact, it already owns it.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o A kernel thread may get stuck in an AST (asynchronous system
trap) delivery loop trying to deliver an AST when there are
none queued.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o The system may crash with a 'Pagefault with IPL (interrupt
priority level) too high' bugcheck when trying to deliver an
AST (asynchronous system trap).
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o An entire system can hang with many un-serviced fork blocks on
the IPL 8 (interrupt priority level 8) fork queue. These fork
blocks were entered onto the fork queue from an IPL below
IPL$_RESCHED.
Images Affected:
- [SYS$LDR]SYSTEM_PRIMITIVES.EXE
- [SYS$LDR]SYSTEM_PRIMITIVES_MIN.EXE
o Two class schedulers running on the same system can cause a
system crash. The two class schedulers attempt to insert the
same TQE (timer queue element) onto the system-wide TQE queue
multiple times, which causes the system to crash.
Images Affected: [SYS$LDR]CLASS_SCHEDULER.EXE
o Documentation states that a process joins the system and
default group resource domains when it is created. In fact,
the process only joins the system domain. The first $ENQ will
result in the process joining the default group domain. If
however, a process begins to issue $GETLKI system services
without having issued an $ENQ prior to the $GETLKI calls, the
process will not be able to read the value blocks for locks
and will get back SS$_ILLRSDM errors.
Images Affected: [SYS$LDR]LOCKING.EXE
o In IEEE trap handler, a denormal value rounds up to an
in-range value. See examples below:
int main() {
FLOAT_INT d1, d2, res, expected_sum, intm;
d1.i = 0x00ffffff;
d2.i = 0x3f000000;
expected_sum.i = 0x00800000;
plain_value(d1, d2, expected_sum);
printf("expected result = -0.0 or 0.0\n\n");
d1.i = 0x00ffffff;
d2.i = 0xbf000000;
expected_sum.i = 0x80800000;
plain_value(d1, d2, expected_sum);
printf("expected result = 0.0\n\n");
Images Affected:
- [SYS$LDR]EXCEPTION.EXE
- [SYS$LDR]EXCEPTION_MON.EXE
o IEEE rounding is producing incorrect results in some cases.
Images Affected:
- [SYS$LDR]EXCEPTION.EXE
- [SYS$LDR]EXCEPTION_MON.EXE
o A system can crash in the exception handling code because a
register is not being restored properly.
Images Affected:
- [SYS$LDR]EXCEPTION.EXE
- [SYS$LDR]EXCEPTION_MON.EXE
o A SET SECURITY/OBJECT=DEVICE command can affect the wrong
device in a cluster.
Images Affected:
- [SYSLIB]IOGEN$SHARE.EXE
- [SYS$LDR]SYS$BASE_IMAGE.EXE
- [SYS$LDR]IO_ROUTINES_MON.EXE
- [SYSLIB]SDA$SHARE.EXE
o The system could crash with a PFIPLHI within the SECURITY
execlet.
Images Affected: [SYS$LDR]SECURITY.EXE
o A KRNLSTAKNV, Kernel stack not valid, crash can occur. See
partial crash summary below:
SDA> clue crash
Crashdump Summary Information:
------------------------------
Crash Time: 12-MAY-2000 03:26:20.84
Bugcheck Type: KRNLSTAKNV, Kernel stack not valid
Node: ITSCLI (Standalone)
CPU Type: AlphaServer 2100 4/275
VMS Version: V7.1-2
Current Process: BATCH_148
Current Image: ITSCLI$DRA1:[PMIS_V502.][PMIS]PMIS.EXE
Failing PC: FFFFFFFF.80074708 EXE$BUGCHECKHANDLER_C+00770
Failing PS: 00000000.00001F00
Module: EXCEPTION
Offset: 00018708
Boot Time: 11-MAY-2000 04:27:01.00
System Uptime: 0 22:59:19.84
Crash/Primary CPU: 01/00
System/CPU Type: 0902
Saved Processes: 31
Pagesize: 8 KByte (8192 bytes)
Physical Memory: 640 MByte (81920 PFNs, contiguous memory)
Dumpfile Pagelets: 94198 blocks
Dump Flags: olddump,writecomp,errlogcomp,dump_style
Dump Type: compressed,selective
EXE$GL_FLAGS: poolpging,init,bugdump
Paging Files: 1 Pagefile and 1 Swapfile installed
Stack Pointers:
KSP = FFFFFFFF.83B5BFF8 ESP = FFFFFFFF.83B5D000 SSP = FFFFFFFF.83B59000
USP = FFFFFFFF.83B59000
General Registers:
R0 = 00000000.00000001 R1 = 00000000.000000C0 R2 = FFFFFFFF.800C7BA0
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o A crash in EXE$CREATE_BUFOBJ can be caused by a user process
running out of BYTLM, e.g., an ORACLE process using Fast I/O.
See the example below:
SYSLKWSET - LOCK/UNLOCK FROM WORKING SET
X-58 CREATE BUFFER OBJECT
;
18294 BBS #CBO$V_EXMAXLIM,-
18295 MMG$L_VFYFLAGS(FP),12$
18296
18297
18298 ; Would creating this buffer object exceed
18299 ; systemwide limits?
18300 CLRL R9
18301 MOVL #SS$_EXBUFOBJLM,R0
18302 CMPL PMS$GL_BUFOBJ_PAGES_S0S1,-
18303 MMG$GL_MAXBOBS0S1_PAGES
18304 .BRANCH_UNLIKELY
18308 BGTRU 50$
18309 12$: MOVL #SS$_BADPARAM,R0
Images Affected: [SYS$LDR]SYS$VM.EXE
o A batch process aborts with SS$_IVCHNLSEC during the image
activation of RDMPRV.EXE.
Images Affected: [SYS$LDR]SYS$VM.EXE
o Provide necessary enhancements to allow the use of the
replacement ANALYZE/PROCESS utility.
Images Affected:
- [SYS$LDR]PROCESS_MANAGEMENT.EXE
- [SYS$LDR]PROCESS_MANAGEMENT_MON.EXE
o The system can crash with a SPLRELERR, 'Spinlock to be
released is not owned' bugcheck.
Images Affected: [SYS$LDR]LOCKING.EXE
o An INCONSTATE bugcheck occurs at SYS$VCC_FILE+208 while
attempting to set up HOSTBASED RAID sets. See the partial
crashdump summary below:
Images Affected: [SYS$LDR]SYS$VCC.EXE
o An Inconstate bugcheck can occur during a RAID unbind
operation.
Images Affected: [SYS$LDR]SYS$VCC.EXE
o For a call from SYS$DELPRC, an ACCVIO occurred resulting in a
system crash.
Image(s) Affected: [SYS$LDR]IMAGE_MANAGEMENT.EXE
INSTALLATION NOTES:
The images in this kit will not take effect until the system is
rebooted. If there are other nodes in the VMScluster, 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.
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 VMS712_SYS /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
All trademarks are the property of their respective owners.
This patch can be found at any of these sites:
Colorado Site
Georgia Site
Files on this server are as follows:
dec-axpvms-vms712_sys-v0300--4.README
dec-axpvms-vms712_sys-v0300--4.CHKSUM
dec-axpvms-vms712_sys-v0300--4.pcsi-dcx_axpexe
vms712_sys-v0300.CVRLET_TXT
|
