|
Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com |
From: IT Resource Center (support_feedback_at_us-support-mail.external.hp.com)
Date: Sun Sep 22 2002 - 10:59:46 CDT
HP Support Information Digests
===============================================================================
o IT Resource Center World Wide Web Service
---------------------------------------------------
If you subscribed through the IT Resource Center and would
like to be REMOVED from this mailing list, access the
IT Resource Center on the World Wide Web at:
Login using your IT Resource Center User ID and Password.
Then select Support Information Digests (located under
Maintenance and Support). You may then unsubscribe from the
appropriate digest.
To download a patch referenced below, access the
IT Resource Center on the World Wide Web at:
Login using your IT Resource Center User ID and Password.
Then select Individual Patches (under Maintenance and Support)
to access the patch. You may also download a patch via anonymous
ftp(1) from ftp.itrc.hp.com.
===============================================================================
Digest Name: weekly HP-UX series 800 11.X patch digest
Created: Sun Sep 22 3:05:08 PDT 2002
Table of Contents:
Document ID Title
--------------- -----------
PHSS_27867 s700_800 11.X OV NNM6.2 Garbled Asian char display in ovw
PHSS_27341 s700_800 11.00 OV ITO6.0X Intermediate Server Patch A.06.13
PHCO_27780 s700_800 11.11 HP-UX Patch Tools
PHCO_27779 s700_800 11.00 HP-UX Patch Tools and White Paper
PHKL_27830 s700_800 11.11 VxFS cumulative;VxFS 3-way deadlock;sendfile
PHKL_27778 s700_800 11.11 V-Class EPIC error handler patch
PHKL_27759 s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,AIO,T600,FS,Hang
PHSS_27684 s700_800 11.00 OV ITO6.0X AIX Agent Patch A.06.11
PHSS_27455 s700_800 11.X OV OB4.10 patch - CS packet
PHSS_27425 s700_800 11.11 X/Motif Runtime Patch
PHSS_26890 s700_800 11.X OV OB3.50 patch - CS packet
PHSS_26882 s700_800 11.X OV OB3.50 patch - MA packet
PHSS_26560 s700_800 11.11 ld(1) and linker tools cumulative patch
PHSS_26559 s700_800 11.00 ld(1) and linker tools cumulative patch
PHSS_26558 s700_800 11.11 linker startup code / SLLIC ELF support
PHSS_26557 s700_800 11.00 linker startup code / SLLIC ELF support
PHSS_26057 s700_800 11.X Cluster Object Manager B.01.04
PHKL_27711 s700_800 11.04 (VVOS) LVM Cumulative Patch w/Perf Upgrades
PHCO_27653 s700_800 11.04 (VVOS) LVM commands cumulative patch
PHSS_27790 s700_800 11.04 Virtualvault 4.5 Apache rc stop scripts
PHSS_27718 s700_800 11.00 ODBCLINK/SE G.00.01 Run-Time Patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHSS_27867
Date Loaded: 20020920
Title: s700_800 11.X OV NNM6.2 Garbled Asian char display in ovw
Patch Name: PHSS_27867
Patch Description: s700_800 11.X OV NNM6.2 Garbled Asian char display in ovw
Creation Date: 02/09/17
Post Date: 02/09/20
Hardware Platforms - OS Releases:
s700: 11.00 11.11
s800: 11.00 11.11
Products:
OpenView Network Node Manager 6.2
Filesets:
OVNNMgr.OVNNM-RUN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP
OVNNMgr.OVNNMGR-JPN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP
OVPlatform.OVEVENT-MIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP
OVPlatform.OVWIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27867
Symptoms:
PHSS_27867:
ovw, xnmevents, xnmgraph do not display Asian characters
correctly.
Defect Description:
PHSS_27867:
ovw, xnmevents or any gui application needs locale
specific resource file to show correct fonts. For Chinese,
Korean or any Asian character display, these locale
specific resource files are missing.
Resolution:
Locale specific resource files have been provided in the
patch. These files will get installed into $OV_NEW_CONF
directory and then later they will be copied under
directory /usr/lib/X11/$LANG/app-defaults/, where the GUI
applications look for it. $LANG refers to locale name in
which GUI applications are running. This patch provides
the resource files for ko_KR.eucKR, zh_CN.hp15CN, and
zh_TW.big5 locales.
Enhancement:
No
SR:
8606267276
Patch Files:
OVNNMgr.OVNNM-RUN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/newconfig/OVNNM-RUN/app-defaults/C/XNm
/opt/OV/newconfig/OVNNM-RUN/app-defaults/C/XNmappmon
/opt/OV/newconfig/OVNNM-RUN/app-defaults/C/XNmgraph
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_TW.big5/XNm
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_TW.big5/
XNmappmon
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_TW.big5/XNmgraph
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_CN.hp15CN/XNm
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_CN.hp15CN/
XNmappmon
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_CN.hp15CN/
XNmgraph
/opt/OV/newconfig/OVNNM-RUN/app-defaults/ko_KR.eucKR/XNm
/opt/OV/newconfig/OVNNM-RUN/app-defaults/ko_KR.eucKR/
XNmappmon
/opt/OV/newconfig/OVNNM-RUN/app-defaults/ko_KR.eucKR/
XNmgraph
OVNNMgr.OVNNMGR-JPN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/newconfig/OVNNMGR-JPN/conf/ja_JP.eucJP/trapd.conf
/opt/OV/newconfig/OVNNMGR-JPN/conf/ja_JP.SJIS/trapd.conf
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/XNm
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmappmon
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmgraph
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmevents
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmtrap
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/XNm
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmappmon
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmgraph
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmevents
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmtrap
OVPlatform.OVEVENT-MIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/C/XNmevents
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/C/XNmtrap
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_TW.big5/
XNmevents
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_TW.big5/
XNmtrap
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_CN.hp15CN/
XNmevents
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_CN.hp15CN/
XNmtrap
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/ko_KR.eucKR/
XNmevents
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/ko_KR.eucKR/
XNmtrap
/opt/OV/newconfig/OVEVENT-MIN/conf/C/trapd.conf
/opt/OV/newconfig/OVEVENT-MIN/conf/zh_TW.big5/trapd.conf
/opt/OV/newconfig/OVEVENT-MIN/conf/zh_CN.hp15CN/trapd.conf
/opt/OV/newconfig/OVEVENT-MIN/conf/ko_KR.eucKR/trapd.conf
OVPlatform.OVWIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/newconfig/OVWIN/app-defaults/zh_TW.big5/OVw
/opt/OV/newconfig/OVWIN/app-defaults/zh_CN.hp15CN/OVw
/opt/OV/newconfig/OVWIN/app-defaults/ko_KR.eucKR/OVw
what(1) Output:
OVNNMgr.OVNNM-RUN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/newconfig/OVNNM-RUN/app-defaults/C/XNm:
XNm Resources
HP OpenView NNM Release B.06.20 Sep 17 2002
Copyright (c) 1990-2002 Hewlett-Packard Company
/opt/OV/newconfig/OVNNM-RUN/app-defaults/C/XNmappmon:
XNmappmon Resources
HP OpenView NNM Release B.06.20 Sep 17 2002
Copyright (c) 1990-2002 Hewlett-Packard Company
/opt/OV/newconfig/OVNNM-RUN/app-defaults/C/XNmgraph:
XNmgraph Resources
HP OpenView NNM Release B.06.20 Sep 17 2002
Copyright (c) 1990-2002 Hewlett-Packard Company
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_TW.big5/XNm:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_TW.big5/
XNmappmon:
HP OpenView XNmappmon Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_TW.big5/
XNmgraph:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_CN.hp15CN/XNm:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_CN.hp15CN/
XNmappmon:
HP OpenView XNmappmon Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/zh_CN.hp15CN/
XNmgraph:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/ko_KR.eucKR/XNm:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/ko_KR.eucKR/
XNmappmon:
HP OpenView XNmappmon Resources
/opt/OV/newconfig/OVNNM-RUN/app-defaults/ko_KR.eucKR/
XNmgraph:
HP OpenView XNm Resources
OVNNMgr.OVNNMGR-JPN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/newconfig/OVNNMGR-JPN/conf/ja_JP.eucJP/trapd.conf:
None
/opt/OV/newconfig/OVNNMGR-JPN/conf/ja_JP.SJIS/trapd.conf:
None
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/XNm:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmappmon:
HP OpenView XNmappmon Resources
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmgraph:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmevents:
HP OpenView Resources for event browser
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.SJIS/
XNmtrap:
HP OpenView Resources for event configurator
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/XNm:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmappmon:
HP OpenView XNmappmon Resources
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmgraph:
HP OpenView XNm Resources
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmevents:
HP OpenView Resources for event browser
/opt/OV/newconfig/OVNNMGR-JPN/app-defaults/ja_JP.eucJP/
XNmtrap:
HP OpenView Resources for event configurator
OVPlatform.OVEVENT-MIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/C/XNmevents:
HP OpenView Resources for event browser
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/C/XNmtrap:
HP OpenView Resources for event configurator
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_TW.big5/
XNmevents:
HP OpenView Resources for event browser
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_TW.big5/
XNmtrap:
HP OpenView Resources for event configurator
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_CN.hp15CN/
XNmevents:
HP OpenView Resources for event browser
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/zh_CN.hp15CN/
XNmtrap:
HP OpenView Resources for event configurator
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/ko_KR.eucKR/
XNmevents:
HP OpenView Resources for event browser
/opt/OV/newconfig/OVEVENT-MIN/app-defaults/ko_KR.eucKR/
XNmtrap:
HP OpenView Resources for event configurator
/opt/OV/newconfig/OVEVENT-MIN/conf/C/trapd.conf:
None
/opt/OV/newconfig/OVEVENT-MIN/conf/zh_TW.big5/trapd.conf:
None
/opt/OV/newconfig/OVEVENT-MIN/conf/zh_CN.hp15CN/trapd.conf:
None
/opt/OV/newconfig/OVEVENT-MIN/conf/ko_KR.eucKR/trapd.conf:
None
OVPlatform.OVWIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/newconfig/OVWIN/app-defaults/zh_TW.big5/OVw:
HP OpenView OVw Resources
/opt/OV/newconfig/OVWIN/app-defaults/zh_CN.hp15CN/OVw:
HP OpenView OVw Resources
/opt/OV/newconfig/OVWIN/app-defaults/ko_KR.eucKR/OVw:
HP OpenView OVw Resources
cksum(1) Output:
OVNNMgr.OVNNM-RUN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP:
1453477935 20938 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
ko_KR.eucKR/XNm
3808301638 10594 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
ko_KR.eucKR/XNmappmon
6197672 23220 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
ko_KR.eucKR/XNmgraph
1122687254 20938 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
zh_CN.hp15CN/XNm
4051044643 10594 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
zh_CN.hp15CN/XNmappmon
4093955672 23220 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
zh_CN.hp15CN/XNmgraph
667605914 20938 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
zh_TW.big5/XNm
1950899568 10594 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
zh_TW.big5/XNmappmon
2494898719 23220 /opt/OV/newconfig/OVNNM-RUN/app-defaults/
zh_TW.big5/XNmgraph
1275254037 20281 /opt/OV/newconfig/OVNNM-RUN/app-defaults/C/
XNm
722460271 10042 /opt/OV/newconfig/OVNNM-RUN/app-defaults/C/
XNmappmon
3559529326 21699 /opt/OV/newconfig/OVNNM-RUN/app-defaults/C/
XNmgraph
OVNNMgr.OVNNMGR-JPN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1277234564 20953 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.eucJP/XNm
590805189 10462 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.eucJP/XNmappmon
1591671941 22768 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.eucJP/XNmgraph
3254717490 20918 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.eucJP/XNmevents
1426674623 6394 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.eucJP/XNmtrap
1026723747 20763 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.SJIS/XNm
4245385614 10462 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.SJIS/XNmappmon
2998183050 22768 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.SJIS/XNmgraph
358630502 20924 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.SJIS/XNmevents
2932325753 6394 /opt/OV/newconfig/OVNNMGR-JPN/app-defaults/
ja_JP.SJIS/XNmtrap
1060424385 359086 /opt/OV/newconfig/OVNNMGR-JPN/conf/
ja_JP.SJIS/trapd.conf
2914131464 359086 /opt/OV/newconfig/OVNNMGR-JPN/conf/
ja_JP.eucJP/trapd.conf
OVPlatform.OVEVENT-MIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,
v=HP:
3266679330 371743 /opt/OV/newconfig/OVEVENT-MIN/conf/
ko_KR.eucKR/trapd.conf
3249491629 371729 /opt/OV/newconfig/OVEVENT-MIN/conf/
zh_CN.hp15CN/trapd.conf
883125937 371744 /opt/OV/newconfig/OVEVENT-MIN/conf/
zh_TW.big5/trapd.conf
3885363869 354174 /opt/OV/newconfig/OVEVENT-MIN/conf/C/
trapd.conf
747494324 21231 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
ko_KR.eucKR/XNmevents
778228296 5746 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
ko_KR.eucKR/XNmtrap
1828781139 21223 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
zh_CN.hp15CN/XNmevents
541315396 5738 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
zh_CN.hp15CN/XNmtrap
1828781139 21223 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
zh_TW.big5/XNmevents
541315396 5738 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
zh_TW.big5/XNmtrap
3441967092 20067 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/
C/XNmevents
541315396 5738 /opt/OV/newconfig/OVEVENT-MIN/app-defaults/C/
XNmtrap
OVPlatform.OVWIN,fr=B.06.20.00,fa=HP-UX_B.11.00_32/64,v=HP:
2802082829 22278 /opt/OV/newconfig/OVWIN/app-defaults/
ko_KR.eucKR/OVw
3710384976 22278 /opt/OV/newconfig/OVWIN/app-defaults/
zh_CN.hp15CN/OVw
2194310505 22278 /opt/OV/newconfig/OVWIN/app-defaults/
zh_TW.big5/OVw
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes: None
Equivalent Patches:
PHSS_27866:
s700: 10.20
s800: 10.20
Patch Package Size: 2780 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_27867
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27867.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27867. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_27867.text file is
available in the product readme:
swlist -l product -a readme -d 
/tmp/PHSS_27867.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27867.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
========================================================
BEFORE LOADING THIS PATCH...
If there are any ovw sessions running on either the
Management Station or on any Management Consoles, these
sessions need to be closed. The "ovstop" command
should then be executed.
WARNING : the patch will not install if any
Network Node Manager processes are
detected.
BACKUP ALL OpenView DIRECTORIES TO TAPE. This
pre-caution ensures that if you have problems after
installing the patch, you will be able to restore your
current state from tape.
NOTE : ovstart is NOT executed after the patch is loaded
You will need to manually run ovstart.
Also, in order to keep a history of the patches
installed on your system the post-install script
will attempt to copy this <patch_name>.text file
to /usr/OV/ReleaseNotes/patches
(or /opt/OV/ReleaseNotes/patches). Please make
sure this file is in /tmp before installation.
========================================================
PHSS_27867:
Since $OV_CONF/$LANG/trapd.conf is a user modifiable
resource file, patch installation will not over write it.
So after the patch installation, user has to copy or merge
the $OV_NEW_CONF/OVEVENT-MIN/app-defaults/$LANG/trapd.conf
to $OV_CONF/$LANG/trapd.conf.
-----End of Document ID: PHSS_27867------------------------------------------
Document ID: PHSS_27341
Date Loaded: 20020920
Title: s700_800 11.00 OV ITO6.0X Intermediate Server Patch A.06.13
Patch Name: PHSS_27341
Patch Description: s700_800 11.00 OV ITO6.0X Intermediate Server Patch A.06.13
Creation Date: 02/09/13
Post Date: 02/09/20
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products:
OpenView IT/Operations 6.0
Filesets:
OVOPC.OVOPC-MAN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC.OVOPC-LIB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC.OVOPC-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-ORA.OVOPC-GUI-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC.OVOPC-UX-MGR78,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC.OVOPC-GUI-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-WWW.OVOPC-WWW-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-ORA.OVOPC-UX-ORAA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-OVW.OVOPC-LIB-UTIL,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-JPN.OVOPC-GUI-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
OVOPC-ORA.OVOPC-UX-ORAB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHSS_27341
Symptoms:
PHSS_27341:
- SR: H555007902
Throughout the code, multithread-unsafe system calls have
been used. This may cause various problems, especially if
multiprocessor machines are used.
- SR: H555008031
The XML parser used by the ServiceNavigator product will
not detect if a CalcRule definition is missing, thus
causing 'opcservice -check' to abort.
- SR: H555008233
The Request Sender may coredump when ovstop is run. It
is possible that this will not be noticed, as it will not
be displayed on the console nor will there be a message
in the logfile/browser.
- SR: H555008627
opcecm may core dump after once successfully detecting
a message storm.
- SR: 8606143216
The Distribution Manager now supports selective
distribution of actions/commands/monitor binaries.
- SR: 8606249669
No undefined variable warning was given if the
<$MSG_NODE_ID> variable was used in a field other than
the service name.
- SR: 8606258715
opcnode -listnodes gives incorrect information for
Communication Type and Network Type.
- SR: 8606268400
New OVO 7.X "Tier 4 Agent" licenses are not accepted by
the opclic utility. You get the error message:
Error /opt/OV/bin/OpC/install/opclic(7008) :
The specified license password is invalid. (OpC40-1106)
- SR: B555014586
The opcdbreorg(1M) man page has a wrong restriction.
- SR: B555014546
When the suppress and count duplicates feature is enabled
with adding annotations for duplicates and a lot of
duplicates are received because of a message storm, this
might add a lot of annotations for a message. This might
cause performance problems and fill up the disk.
- SR: B555011914
In rare cases the opcsvcm and opcuiwww processes might
abort if there are problems during the error handling of
configuration requests (list, add, replace, remove of
services). The stacktrace contains a ThrowException()
call.
- SR: B555012633
The JavaGUI does not replace the $OPC_SERVICE_VALUE[]
variable in customized applications started from a
service submap popup menu.
- SR: B555012996
opcuiwww is growing when many service changes come in.
The growth could be at almost 1 KB per message.
- SR: B555013993
Removing the A.06.08 consolidated server patch PHSS_24264
together with one of the following intermediate patches
(A.06.09, A.06.10 or A.06.12) will remove the
/opt/OV/bin/OpC/opc.bin file from your system so the ITO
GUI cannot be started.
- SR: B555014034
The JavaGUI does not show messages for non-IP nodes in a
filtered history browser unless you open another browser
to get the messages from the database into the cache.
- SR: B555014110
The forward manager, opcforwm, uses high amounts of CPU
even if no message forwarding is setup. This happens only
if the 'suppress and count duplicates' feature on the
server is enabled.
- SR: B555014123
The ITO application which is integrated in CDE will not
start if it writes some startup message like "ovw:
Allocated ... colors."
- SR: B555014169
The itochecker tool does not warn you if required patches
are missing on the management server.
- SR: B555014226
The Control Manager did not pass the name of the
expired license together with the expiration message
(OpC40-1122).
- SR: B555014396
The message throughput dramatically drops when using
message key relations.
- SR: B555014435
When a message which has been forwarded to a second
management server is unacknowledged, it is owned on the
original management server, but not on second server.
- SR: B555014465
opcdbreorg -consolidate does not consider in disk space
check, that old files still need space until restart of
the database.
- SR: B555014471
opcforwm produces ORA-01405: fetched column value is NULL
messages because two threads use the same database
connection at the same time.
- SR: B555014507
Cannot start Input/Output Applications from a SJIS
management server on an EUC managed node.
- SR: B555014545
opcforwm consumes a lot of CPU if suppress and count
duplicates is enabled and annotations are added for the
duplicates.
- SR: B555014596
Including fixes from the ECS runtime engine with
PHSS_26909 and equivalent.
- SR: B555014597
Use direct=y for export to avoid Oracle export bug
199416.1 in opcdbreorg.
- SR: B553003516
When trying to run X-OVw applications from the
Motif GUI, the application starts, but when closing
the resulting ovw window, you may get an error message
about non-existent file or directory.
The applications "Highlight Selected Node" and
"Highlight Message Node" may not work correctly.
PHSS_26757:
- SR: 8606221643
Message change events for added annotations, own and
disown in the Java GUI or API functions are not forwarded
to other managers.
- SR: B555013854
Messages that are forwarded to another management server
and acknowledged on the local management server are not
counted as duplicate on the target manager.
This was explicitly implemented this way (a check was
done if the message is forwarded and forwarded messages
were not included in the counting).
Now, also forwarded messages are considered. To avoid
loops and duplicate counting in other scenarios (both
managers see all messages), duplicate count changes are
not forwarded back to the source manager.
Since there are so many configuration possibilities and
customer may want to keep the existing behavior, the
current behavior is still the default behavior, but it is
possible to select the new behavior by setting following
opcsvinfo variable to TRUE:
OPC_COUNT_FORW_MSGS TRUE
- SR: 8606236858
A message that has been forwarded and is acknowledged on
the target management server is also acknowledged on the
source management server even though opcsvinfo variable
OPC_ACCEPT_CTRL_SWTCH_ACKN is set to FALSE.
- SR: 8606236875
Request to make the management server aware of messages
storms as they arrive and to allow actions as soon as the
storm has been detected.
- SR: 8606241653
Java GUI background process opcuiwww aborts if you use
numerical expressions, for example <10 -le <#> -le 30>
in a filter pattern.
- SR: B555012015
Illegal japanese characters in messages lead to an empty
JavaGUI message browser. Illegal characters in
application responses lead to an empty application output
window. You get the error message on the client:
"Unknown serialization error. ITO210-83"
- SR: 8606242736
opcmsgm dies due to (uncritical) Oracle error: ORA-01756.
- SR: 8606243312
The administrator GUI will not print a warning if an
undefined variable is used in the set node or automatic
action node field.
- SR: 8606248137
Message that is acknowledged through message key relation
is not acknowledged on management server where it was
forwarded.
- SR: R555001915
Annotations created by opcmsgm are not forwarded to other
management server.
- SR: B555011695
Downloading service logs into a file using 'opcsvcdwn'
may loop while writing the file until the disk is full.
- SR: B555012020
The 'Source' field in the Message Details window
(JavaGUI: Message Properties window) contains no
information about the matched condition.
- SR: B555013716
The JavaGUI client opens a new database connection each
time you open a message properties window instead of
reusing the existing connection.
- SR: B555012081
opccfgupld -replace changes the file name of templates
under which they are stored in the directory tree
/etc/opt/OV/share/conf/OpC/mgmt_sv/templates. This causes
the directory tree gets filled with unused files.
- SR: B555013232
The implementation of the new parameters
OPC_NOTIF_WHEN_DUPLICATE and OPC_TT_WHEN_DUPLICATE is
incomplete. Modification of the do_notification or
trouble_ticket flags of a message by the outage or
service hours template are ignored for messages suppressed
as duplicates.
- SR: B555013235
The API functions opcnode_add() and opcnode_modify()
will always uses the first node name returned by the
name service. But they do not return an error or warning
if the node name specified is different than the used
node name.
- SR: B555013450
The Message Browser suddenly exchanged the contents of
the details window and showed the details of a different
message which was modified by the API routine
opcmsg_modify() in the background.
- SR: B555013489
opcdistm aborts when distributing non-existing files
(i.e. if one of the distribution directories contains a
link which points to a file which is not there)
- SR: B555013575
opccfgupld aborts with an internal error when uploading
regroup conditions, if the description of a regroup
condition is the same as the description of a template
condition.
- SR: B555013712
The JavaGUI displays not all messages in a filtered
History Browser if you use relative times. Only those
messages are displayed which are already in the cache
because they are displayed in some other browser.
If the filter specifies no "To" time, the query takes
a lot of time, and actually often looks like hanging.
PHSS_25639:
- SR: B555012596
Message manager may randomly abort with SIGSEGV if
duplicate message count is enabled.
- SR: B555012299
opcactm aborts when processing annotations over 16 MByte
- SR: B555011579
During startup ovoareqsdr and opcctlm may kill processes
that do not belong to ITO, if their process ID matches
the process ID of ITO processes before the shutdown.
- SR: 8606136342
The variable $OPC_USER which can be used in application
calls cannot be used in operator initiated actions.
- SR: 8606175519
opcnode hangs when given an invalid node group name.
- SR: 8606180181
The "suppress and count duplicate" message feature is
applied even to log-on-server-only messages, which is not
the desired behavior.
- SR: 8606202492
It is not possible to have more than 15 SNMP trap
variables.
- SR: 8606215969
opcdbidx -all should not perform the -lower task.
- SR: 8606225322
Error message OpC40-427 sometimes misses additionnal
information
- SR: B555008838
Event correlation engine creates "Time cannot go
backwards" error if the system is very busy.
- SR: B555010948
Nested alternatives were not handled correctly in the
pattern matching algorithm, e.g. the pattern '[a|b]c|d'
was handled like '[a|b|d]c'.
- SR: B555012300
The opcappl_start() API function has a memory leak.
- SR: B555012417
When using opcragt to distribute templates, commands and
similar to a node, it might return error OpC40-103.
This has been seen especially in very large environments
with a large number of NT nodes.
- SR: B555012554
Distribution manager was not always updated when node's
names or IP address was changed. This can lead to denied
template distribution requests.
- SR: B555012210
ECS circuit using reset on unless node causes opcecm to
abort.
- SR: B553000078
Message severity and own counters in the Motif Message
Browser are wrong if a lot of opcmsg_modify() and
opcmsg_disown() API functions are called very fast.
- SR: H553000345
The Service API call RemoveRegCon("myservice") does not
remove this specific service from registration object.
- SR: B555012609
In some environments the text fields in the JavaGUI
message properties window are all black due to a wrong
background color selection.
- SR: B555012448
The JavaGUI aborts with "Communication Error - Trying to
reconnect" if you chose to display all messages
and have a large amount of messages (e.g. 30000)
- SR: 8606221493
If a message is owned, the node status changes in the
Java GUI although OPC_OWN_DISPLAY is set to
STATUS_PROPAGATE.
- SR: H553000562
The JavaGUI does not warn you if you create a browser
filter where the "From" date is more recent than the
"To" date.
- SR: H553000575
Minimized windows in the JavaGUI are not automatically
restored when they are chosen from the 'Window' menu.
- SR: H553000717
If you click 'OK' in the 'Add Annotation' window of the
JavaGUI without having added some text, you get an
ArrayIndexOutOfBoundsException exception (but the JavaGUI
will still work fine).
- SR: H553000815
Doubleclicking a service icon in a graph which was opened
using the "Show Submap" or "Show in Custom map" popup
menu selection from a service causes a
NullPointerException. The JavaGUI can freeze.
- SR: B555011638
Pattern matching cannot match new line of multi line
messages.
PHSS_24687:
- SR: H555005726
Non-ASCII characters in service definition files for
several character sets are ignored. Affected are the
character sets ISO-8859-2 - ISO-8859-15 and on Solaris
additionally all multi byte character sets except EUC-JP.
- SR: H555006218
The Motif GUI sometimes does not reconnect to opcdispm
after server restart. This leads to wrong service states
and other GUIs not being updated.
- SR: 8606179981
If you have enabled "Suppression of duplicated messages"
then the local automatic action is launched on each
message whereas the notification service is only launched
once.
- SR: 8606180178
If "suppress and count duplicates" is enabled on the
management server and there is already a message in the
browser with the same message key as an incoming message,
the incoming message will not autoacknowledge any
messages with the same message keys specified in the
"Acknowledge Message Matching This Message Key Pattern"
field.When the incoming message is counted as a
duplicate message by the MSI, the MSI ignores the auto-
acknowledgements configured in the template.
- SR: 8606182989
It may take a long time to start the Java GUI in an
environment with many nodes.
- SR: 8606189679
Duplicate suppression on the server is done before
messages are forwarded to message stream interface (MSI)
applications. Therefore suppressed messages do not
arrive at the MSI. Since check for duplication has to
be done based on the state of the active browser, it
should be done as late as possible in the event
processing flow, i.e. after the message is processed by
the MSI.
- SR: 8606208349
The opc.hosts mapping file does not allow hostnames
starting with a number.
- SR: 8606208352 / B553000079
A message with a message key relation gets an unnecessary
annotation if no message was acknowledged.
- SR: 8606212408
<$OPC_MGMTSV> can only be used in action node fields.
- SR: 8606214551
The instruction text for OpC20-12 should contain a hint
on the name of the kernel parameter which should be
increased.
- SR: R555002040
The JavaGUI does not display any errors from failing
"No Output" applications.
- SR: B555009102
Sometimes the request sender calculates the wrong heart
beat polling (HBP) intervals which lead to inaccurate
timing or in rare cases causes request sender to loop
which loads the CPU.
- SR: B555010978
ITO 6.0 supports NNM 6.2 but does not provide a
suitable SNMP template yet.
- SR: B555011204
The JavaGUI ignores the startup option
"passwd=<my password>" given in the ito_op.bat (NT) or
ito_op (UNIX) startup script.
- SR: B555011294
If an integrated application uses the Message Stream
Interface (MSI) for Application Responses, opcdispm
will grow in size. The size of the memory leak depends
on the size of the output of the started applications.
- SR: B555011399
ovoareqsdr's internal data structures are not up-to-date
after opcnode -del_node or opcchgaddr -sync are used.
- SR: B555011401
Enhancement request to restrict execution of remote
automatic actions to a list of nodes
- SR: B555011420
Service status is not updated after acknowledging a
message when opcmsgm aborted previously.
- SR: B555011541
Manual agent installation using inst.sh from management
server does not work correctly if no commandline options
are used (query for all information). The error displayed
is:
/opt/OV/bin/OpC/agtinstall/inst.sh[242]: test: A ]
character is missing.
/opt/OV/bin/OpC/agtinstall/inst.sh[243]: 1: not found.
- SR: B555011550
itochecker has problems checking mpe/ncs nodes:
1. The status output is:
lb_admin tool does not exist.
2. When checking nodes via snmp, itochecker cannot
determine hardware and operating system.
3. itochecker does not report about console interceptor
status.
- SR: B555011575
Calling 'opcragt -distrib -all' on the server will
distribute the configuration to all nodes, including
VP390 managed nodes which connect to VPO using the LLI
interface. VP390 nodes should be treated like external
nodes as distribution to LLI nodes is not permitted.
- SR: B555011619
The JavaGUI needs a long time to open history browsers
on service elements if there are many history messages.
- SR: B555011632 / B553000077
opcuiwww has a memory leak. It grows with each refresh.
The amount depends on the number of managed nodes.
- SR: B555011678
Message manager consumes 100% CPU while still working
correctly. CPU time is spent opening, reading and closing
msgkeyq/p files.
- SR: B555011690
itochecker does not report the number of messages in the
active message tables that are marked acknowledged.
- SR: B555011765
opcnode fails with a node name of more than 63 characters
- SR: B555011833
The opcdata_get_str() API call contains a memory leak
if you access the OPCDATA_SERVICE_NAME attribute of an
OPCDTYPE_MESSAGE_EVENT.
- SR: B555011979
Pattern matching hangs if only single byte Japanese
HANKAKU KANA characters are used.
- SR: B555011990
ECS event log (ecevilg) has invalid time difference to
the next message which can cause the ECS simulator
to hang or appear to hang when loading an event log file
with such values.
- SR: B555012013
You cannot use the new Secure SHell (SSH) agent
distribution mechanism for Linux 2.4 nodes.
- SR: B555012055
The JavaGUI shows wrong message times (1 hour late)
if you are in the timezone GMT+10 (Canberra, Sydney and
Melbourne) and run the JavaGUI on a Windows system.
- SR: B555012067
Performance of count duplicates is much slower if trace
is enabled, even though the SQL trace area is not enabled.
- SR: B553000107
The message text field in the set attributes section
of the condition window truncates texts with more than
512 characters.
- SR: B553000108
opccfgdwn and opccfgupld do not handle user profile
assignments for the administrator.
- SR: H553000487
Service actions without a defined label appear as empty
popup menu items.
- SR: H553000492
Manual refresh of the JavaGUI does not properly update
the status of service graphs once you open and close an
"filter active browser" on the toplevel service of the
graph.
Defect Description:
PHSS_27341:
- SR: H555007902
Multithread-unsafe system calls have been replaced with
their threadsafe counterparts without changing the
functionality of the code.
- SR: H555008031
The XML parser used by the ServiceNavigator product will
not detect if a CalcRule definition is missing thus
causing 'opcservice -check' to abort. Now the library
will throw an error.
Note that for the full fix you need a ServiceNavigator
patch level of A.06.13 or higher, otherwise you only get
this error:
"Error: unknown error".
- SR: H555008233
An ICMP response could trigger a write to a memory queue
after the destructor for this object has already been
called and has freed the memory. This is fixed by
disabling signal handling for SIGIO before calling exit.
- SR: 8606143216
The Distribution Manager now supports selective
distribution. The concept and required configuration
steps are explained in a separate white paper
/opt/OV/doc/C/OpC/SelectiveDistribution.pdf
- SR: B555014546
It is now possible to restrict the number of annotations
by adding the opcsvinfo variable
OPC_MAX_DUPL_ANNO <max duplicate counter number>. If the
duplicate counter is higher than the specified number,
no further annotations will be added for duplicate
messages.
- SR: B555012996
A memory leak was fixed.
- SR: B555013993
The intermediate patches patched the opc.bin file and did
an swmodify on the A.06.08 patch to avoid swverify errors
there. Now, if the underlying A.06.08 is deinstalled the
opc.bin gets removed but cannot be restored as it was not
backed up (was not contained in A.06.08). A workaround is
to run this command before removing the A.06.08 patch:
/usr/sbin/swmodify -u -x files='/opt/OV/bin/OpC/opc.bin'
PHSS_24264.OVOPC-GUI
- SR: B555014034
The JavaGUI does not show messages for non-IP nodes in a
filtered history browser because the database query had
a net_type parameter of 'IP' even for non-IP nodes so
the query fails.
- SR: B555014110
This is related to defect number B555014545. In addition
to the fix made there, opcforwm is now only started if
message forwarding is setup (if a
/etc/opt/OV/share/conf/OpC/mgmt_sv/respmgrs/msgforw file
is present).
- SR: B555014123
The ITO application which is integrated in CDE will not
start if it writes some startup message like "ovw:
Allocated ... colors." because it was registered as
NO_STDIO type and CDE does not know where to write the
message to.
Now the message will appear in $HOME/.dt/errorlog
- SR: B553003516
The problem was a result of incorrect usage of strings
in combination with putenv. putenv is now called
in a safe way.
PHSS_26757:
- SR: 8606236875
Management server or agent are currently not able to
detect message storms.
In order to detect message storm an ECS circuit has been
designed that is able to detect storms on a per node
basis.
For further details about these feature see:
/opt/OV/contrib/OpC/MsgStorm
and a WhitePaper is available under:
/opt/OV/doc/C/OpC/MessageStormDetection_1_0.pdf
- SR: B555011695
Downloading service logs into a file using 'opcsvcdwn'
may loop while writing the file until the disk is full.
If during the database access there are any problems
it starts from scratch instead of just retrying the last
step.
- SR: B555013716
Requesting message properties information does not use
the existing database connection but opens a new one for
each request.
- SR: B555013235
opcnode_add() and opcnode_modify() will now return
the warning OPC_WARN_NODE_NAME_DIFFERENT if the node
name or IP address is different than specified by the
caller. It is possible to switch back to the old
behavior by adding the following line to opcsvinfo:
OPC_NO_API_NODE_NAME_CHANGE_WARN TRUE
- SR: B555013712
The JavaGUI displays not all messages in a filtered
History Browser if you use relative times because the
database query was using relative times but the messages
are stored with the absolute times.
for SR's not listed in this section please see
the list of symptoms
PHSS_25639:
- SR: B555012596
In order to add the number of duplicates (message
counter) to the message structure, it might be necessary
to reallocate the memory for this structure. Not all
references to the message were updated.
- SR: B555011579
Comparison was based only on the process ID. Now an
additional check for the process name is performed.
- SR: 8606136342
It is now possible to use $OPC_USER, $OPC_MGMTSV and
$OPC_ENV in operator initiated actions.
- SR: 8606202492
It was not possible to have more than 15 SNMP trap
variables. Now, VPO allows up to 32 SNMP trap
variables.
- SR: 8606225322
In some cases there was no additional information, just
'Network communication problems occurred. (OpC40-427)'
The message was changed to 'Network communication
problem: Could not obtain endpoint information from node
<hostname>. (OpC40-399)'
- SR: B555010948
The grammar was changed to allow nested alternatives and
process it correctly.
- SR: B555012417
When doing a distribution by using opcragt the error
OpC40-103 might be generated, that mostly happens
while distributing to a large number of NT nodes.
The reason is that on some of the NT nodes the control
agent died with a Dr. Watson. The Dr. Watsons waits
till it is closed now. This will block one of the
free slots in the distribution manager on the server
side. Since the number of parallel distributions
cannot be higher than 10 the distribution manager
might generate this error as soon as 10 nodes are
hanging.
The issues with the dying NT nodes is fixed with
a previous agent patch. But it also turned out
that a maximum number of 10 parallel distributions
might be to low.
So the GUI has been changed to allow
up to 100 parallel distributions.
- SR: B555012210
ECS circuit using reset on unless node causes opcecm to
abort. Linked with new ECS runtime library that contains
a fix for this problem.
- SR: B555012609
The background was set to System.inactiveCaptionText
instead of System.textHighlightText
- SR: B555011638
VPO could not match for new line in multi line messages.
Following changes have been made to allow this:
It is now possible to use ^M (\r) as field separator.
Introduced a new pattern </> to match any number of line
breaks (UNIX style \n or NT style \r\n) and <n/> to match
exactly n line breaks, for example <1/> will match
exactly one line break.
This change works only for sources that already can
create multi line messages (for example opcmsg or NT
event log), it does not allow multi line logfile
encapsulation.
This change requires a fix on the management server and
the agent. Therefore a patch on the management server and
a patch for the agent is required to use the new
functionality.
for SR's not listed in this section please see
the list of symptoms
PHSS_24687:
- SR: 8606179981
If you have enabled "Suppression of duplicated messages"
then the local automatic action is launched on each
message whereas the notification service is only launched
once.
Now you can change this using the opcsvinfo settings
OPC_NOTIF_WHEN_DUPLICATE TRUE
OPC_TT_WHEN_DUPLICATE TRUE
which will pass duplicates to the interfaces, with a
16th parameter containing the duplicate counter.
The counter is zero if it is the first message or if this
feature is not switched on.
- SR: 8606182989
The opcuiwww process was loading the node information
from the database several times. Now, the opcuiwww
process loads this information only once which reduces
the startup time.
- SR: 8606189679
Since check for duplication has to be done based one the
state of the active browser, it is now done as late as
possible in the event processing flow. The check for
duplication is now AFTER the message is processed by
the message stream interface (MSI).
Howwever the old behavior is still available by adding to
opcsvinfo:
OPC_SUPPRESS_DUPL_AFTER_MSI FALSE
TRUE is default, new behavior. FALSE is old behavior.
- SR: 8606208349
The opc.hosts mapping file does not allow hostnames
starting with a number. The processing routine in the
libopcsv_r thinks it must be an IP address then
generates an errors as soon as the first letters are
parsed.
- SR: 8606212408
It is now possible to use <$OPC_MGMTSV> in all set
attributes of a condition except for the message key
relation.
- SR: 8606214551
The instruction text for OpC20-12 should contain a hint
on the name of the kernel parameter which should be
increased:
"The configurable kernel parameter on HP-UX is called
nflocks."
- SR: R555002040
The JavaGUI does not display any errors from failing
"No Output" applications because there was no link
from opcdispm to opcuiwww to pass back the result.
- SR: B555009102
When switching from the first (random) heart beat
polling (HBP) interval to the configured one, there was
a chance that one value is changed by another thread
(race condition).
- SR: B555010978
ITO 6.0 supports NNM 6.2 but does not provide a
suitable SNMP template yet. For convenience this patch
contains a template for manual upload using opccfgupld:
'opccfgupld -add /opt/OV/contrib/OpC/SNMP6.2_cfgdwn'
- SR: B555011204
It is now possible to specify the startup option
"passwd=<my password>" in the ito_op.bat (NT) / ito_op
(UNIX) startup script or in the itooprc file. On UNIX it
is also possible to specify the passwd option as
command line option to the ito_op script, for example:
ito_op user=opc_op passwd=OpC_op myserver.hp.com
- SR: B555011401
The action manager now understands a new opcsvinfo
variable OPC_ALLOW_REMOTE_ACTIONS_FROM <nodelist>. If
this variable is set, it implies
OPC_DISABLE_REMOTE_ACTIONS TRUE, but allows remote
actions if they originated from one of the nodes in
<nodelist>.
- SR: B555011420
Service status is not updated after acknowledging a
message when opcmsgm aborted previously due to a bug in
the registration mechanism which is used by opcuiwww
to register at the opcdispm process.
- SR: B555011541
In one line of the shell script a trailing backslash '\'
was missing.
- SR: B555011550
1. itochecker has to check if lb_admin tool is available
2. added several node platforms to agent_platform.conf
file
3. added statements in check_agent_processes function to
check and report status about console interceptor.
- SR: B555011619
The JavaGUI will only load messages from the database
that have a service name set.
- SR: B555011678
When the file handle for msgkeyp was >31 (due to
previously opened files), the used select() call did not
delay execution but immediately returned, forcing opcmsgm
to check the msgkeyq queue file.
- SR: B555011833
The opcdata_get_str() API call contains a memory leak
if you access the OPCDATA_SERVICE_NAME attribute of an
OPCDTYPE_MESSAGE_EVENT because it returns a pointer
to a copy of the requested string instead of a reference
to the string.
- SR: B555011990
The read procedure missed the first digit of the time
stamp of the previous ECS message.
- SR: B555012013
You cannot use the new Secure SHell (SSH) agent
distribution mechanism for Linux 2.4 nodes because
the itosshupdate utility does not update the database
table for this platform.
- SR: B555012055
The JavaGUI shows wrong message times (1 hour too late)
if you are in the timezone GMT+10 (Canberra, Sydney and
Melbourne) due to a bug in the Winddows JRE 1.3.0.
The bug is fixed with the JRE 1.3.1_01 version.
- SR: B555012067
The SQL trace requires some processing overhead that
leads to worse database access performance. This overhead
was spent, even if the SQL trace was not enabled. Now,
it is only spent if the SQL trace area is enabled.
- SR: B553000107
The message text field in the set attributes section
of the condition window truncates texts with more than
512 characters. This limit has now been increased
to 2048 characters.
- SR: H553000487
Service actions without a defined label appear as empty
popup menu items. The JavaGUI is now intelligent enough
to use the action name as a fallback.
Enhancement:
No
SR:
R555002040 R555001915 H555008627 H555008233 H555008031
H555007902 H555007630 H555006218 H555005726 H553000815
H553000717 H553000575 H553000562 H553000492 H553000487
H553000345 B555014597 B555014596 B555014586 B555014546
B555014545 B555014507 B555014471 B555014465 B555014435
B555014396 B555014226 B555014169 B555014123 B555014110
B555014034 B555013993 B555013854 B555013716 B555013712
B555013575 B555013489 B555013450 B555013235 B555013232
B555012996 B555012633 B555012609 B555012596 B555012554
B555012448 B555012417 B555012300 B555012299 B555012210
B555012081 B555012067 B555012055 B555012020 B555012015
B555012013 B555011990 B555011979 B555011914 B555011833
B555011765 B555011695 B555011690 B555011678 B555011638
B555011632 B555011619 B555011579 B555011575 B555011550
B555011541 B555011420 B555011401 B555011399 B555011294
B555011204 B555010978 B555010948 B555010312 B555009102
B555008838 B553003516 B553000108 B553000107 B553000080
B553000079 B553000078 B553000077 8606268400 8606258715
8606249669 8606248137 8606243312 8606242736 8606241653
8606236875 8606236858 8606229181 8606225322 8606221643
8606221493 8606216884 8606215969 8606214551 8606212408
8606208352 8606208349 8606202492 8606189679 8606182989
8606180181 8606180178 8606179981 8606175519 8606143216
8606136342
Patch Files:
OVOPC.OVOPC-MAN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/man/man1m.Z/opcdbidx.1m
/opt/OV/www/htdocs/ito_man/opcdbidx.1m.html
/opt/OV/man/man1m.Z/opcnode.1m
/opt/OV/www/htdocs/ito_man/opcnode.1m.html
/opt/OV/man/man1m.Z/opcragt.1m
/opt/OV/www/htdocs/ito_man/opcragt.1m.html
/opt/OV/man/man1m.Z/opcseldist.1m
/opt/OV/www/htdocs/ito_man/opcseldist.1m.html
/opt/OV/man/man1m.Z/opcdbreorg.1m
/opt/OV/www/htdocs/ito_man/opcdbreorg.1m.html
/opt/OV/www/htdocs/ito_man/itoman_run.htm
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ITO_JAVA.exe
/opt/OV/www/htdocs/ito_op/ito_op.jar
/opt/OV/www/htdocs/ito_op/ito_op_install.tar
/opt/OV/www/htdocs/ito_op/ito_op
OVOPC.OVOPC-LIB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/lib/libopcsv_r.sl
/opt/OV/lib/libopcpb.sl
/opt/OV/lib/libopcsvcapi.sl
/opt/OV/lib/libopcsvcreader.sl
OVOPC.OVOPC-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/bin/OpC/opc.bin
/opt/OV/lib/libopcuiadm.sl
OVOPC-ORA.OVOPC-GUI-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/libopcdb.sl
/opt/OV/bin/OpC/opcuiop
OVOPC.OVOPC-UX-MGR78,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/C/SNMP6.2_.idx
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/C/TEMPLATES/TRAP/trap.dat
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/download.dsf
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/ja_JP.SJIS/SNMP6.2_.idx
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/ja_JP.SJIS/TEMPLATES/
TRAP/trap.dat
/opt/OV/bin/OpC/opcuiadm.bin
/opt/OV/bin/OpC/opcuitadm.bin
/opt/OV/bin/OpC/ovoareqhdlr
/opt/OV/bin/OpC/install/opcagtutil
/opt/OV/contrib/OpC/opcqschk
/opt/OV/contrib/OpC/itochecker
/opt/OV/contrib/OpC/stacktrace
/opt/OV/contrib/OpC/agent_platform.conf
/opt/OV/contrib/OpC/opcgetsvctree
/opt/OV/doc/C/OpC/MessageStormDetection_1_0.pdf
/opt/OV/doc/C/OpC/SelectiveDistribution.pdf
/opt/OV/contrib/OpC/gdb32
/opt/OV/contrib/OpC/gdb64
/opt/OV/bin/OpC/agtinstall/inst.sh
/opt/OV/contrib/OpC/checkuiwww
/opt/OV/contrib/OpC/MsgStorm/README
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/EC/
CIRCUITS/ECmsg_storm.eco
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/EC/
CIRCUITS/ECmsg_storm.ecs
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/EC/ec.dat
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/
INTERFACE/interface.dat
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/
TEMPLGROUP/templgroup.dat
/opt/OV/contrib/OpC/MsgStorm/Templates/C/Template.idx
/opt/OV/contrib/OpC/MsgStorm/Templates/download.dsf
/opt/OV/contrib/OpC/MsgStorm/dstore.ds
/opt/OV/contrib/OpC/MsgStorm/stormstartagt.sh
/opt/OV/contrib/OpC/MsgStorm/stormstopagt.sh
/etc/opt/OV/share/conf/OpC/mgmt_sv/seldist.tmpl
/opt/OV/bin/OpC/install/opclic
OVOPC.OVOPC-GUI-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/lib/nls/C/opcsv.cat
/opt/OV/lib/nls/C/opcinstr.cat
/opt/OV/OpC/dt/appconfig/types/C/opc.dt
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/C/opcwww.cat
/opt/OV/lib/nls/C/opcwwwinstr.cat
OVOPC-WWW.OVOPC-WWW-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/libopcwww.sl
/opt/OV/bin/OpC/opcuiwww
/opt/OV/lib/libopcwwwmgrs.sl
/opt/OV/lib/libopcwwwpb.sl
/opt/OV/lib/libopcsvcmgr.sl
OVOPC-ORA.OVOPC-UX-ORAA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/bin/OpC/opcactm
/opt/OV/bin/OpC/opccmm
/opt/OV/bin/OpC/opcctlm
/opt/OV/bin/OpC/opcdispm
/opt/OV/bin/OpC/opcdistm
/opt/OV/bin/OpC/opcecm
/opt/OV/bin/OpC/opcmsgm
/opt/OV/bin/OpC/utils/opcnode
/opt/OV/bin/OpC/opcragt
/opt/OV/bin/OpC/opcttnsm
/opt/OV/bin/OpC/ovoareqsdr
/opt/OV/bin/OpC/opcforwm
/opt/OV/bin/OpC/opccfgout
/opt/OV/bin/OpC/opcannoadd
/opt/OV/bin/OpC/opcackmsg
/opt/OV/bin/OpC/opcackmsgs
/opt/OV/bin/OpC/utils/opcseldist
/opt/OV/bin/OpC/agtinstall/itosshupdate
OVOPC-OVW.OVOPC-LIB-UTIL,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/libopcutil.sl
/opt/OV/lib/libopcxml.sl
OVOPC-JPN.OVOPC-GUI-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/ja_JP.SJIS/opcsv.cat
/opt/OV/lib/nls/ja_JP.SJIS/opcinstr.cat
/opt/OV/OpC/dt/appconfig/types/ja_JP.SJIS/opc.dt
OVOPC-ORA.OVOPC-UX-ORAB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/bin/OpC/opccfgdwn
/opt/OV/bin/OpC/opccfgupld
/opt/OV/bin/OpC/opcdbidx
/opt/OV/bin/OpC/opcuiopadm
/opt/OV/bin/OpC/opcuitadm
/opt/OV/bin/OpC/opcdbreorg
what(1) Output:
OVOPC.OVOPC-MAN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/man/man1m.Z/opcdbidx.1m:
None
/opt/OV/www/htdocs/ito_man/opcdbidx.1m.html:
None
/opt/OV/man/man1m.Z/opcnode.1m:
None
/opt/OV/www/htdocs/ito_man/opcnode.1m.html:
None
/opt/OV/man/man1m.Z/opcragt.1m:
None
/opt/OV/www/htdocs/ito_man/opcragt.1m.html:
None
/opt/OV/man/man1m.Z/opcseldist.1m:
None
/opt/OV/www/htdocs/ito_man/opcseldist.1m.html:
None
/opt/OV/man/man1m.Z/opcdbreorg.1m:
None
/opt/OV/www/htdocs/ito_man/opcdbreorg.1m.html:
None
/opt/OV/www/htdocs/ito_man/itoman_run.htm:
None
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/www/htdocs/ito_op/ITO_JAVA.exe:
None
/opt/OV/www/htdocs/ito_op/ito_op.jar:
None
/opt/OV/www/htdocs/ito_op/ito_op_install.tar:
None
/opt/OV/www/htdocs/ito_op/ito_op:
None
OVOPC.OVOPC-LIB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/lib/libopcsv_r.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcpb.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcsvcapi.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcsvcreader.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
OVOPC.OVOPC-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/bin/OpC/opc.bin:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcuiadm.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
OVOPC-ORA.OVOPC-GUI-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/libopcdb.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcuiop:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
OVOPC.OVOPC-UX-MGR78,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/C/SNMP6.2_.idx:
None
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/C/TEMPLATES/TRAP/
trap.dat:
None
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/download.dsf:
None
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/ja_JP.SJIS/SNMP6.2_.idx:
None
/opt/OV/contrib/OpC/SNMP6.2_cfgdwn/ja_JP.SJIS/TEMPLATES/
TRAP/trap.dat:
None
/opt/OV/bin/OpC/opcuiadm.bin:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcuitadm.bin:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/ovoareqhdlr:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/install/opcagtutil:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/contrib/OpC/opcqschk:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/contrib/OpC/itochecker:
HP OpenView VantagePoint A.06.13 (09/03/02)
/opt/OV/contrib/OpC/stacktrace:
HP OpenView VantagePoint A.06.13 (08/26/02)
/opt/OV/contrib/OpC/agent_platform.conf:
None
/opt/OV/contrib/OpC/opcgetsvctree:
$Revision: 92453-07 linker linker crt0.o B.11.30 011
005 $
HP92453-02A.11.00 HP-UX SYMBOLIC DEBUGGER (END.O ILP
32) $Revision: 75.04 $
/opt/OV/doc/C/OpC/MessageStormDetection_1_0.pdf:
None
/opt/OV/doc/C/OpC/SelectiveDistribution.pdf:
None
/opt/OV/contrib/OpC/gdb32:
Hewlett-Packard Wildebeest 3.0.01 19-Nov-2001 09:51
hppa1.1-hp-hpux11.00
$ Sep 8 2000 23:13:51 $
/opt/OV/contrib/OpC/gdb64:
Hewlett-Packard Wildebeest 3.0.01 19-Nov-2001 10:18
hppa2.0w-hp-hpux11.00
$ Sep 8 2000 23:13:51 $
/opt/OV/bin/OpC/agtinstall/inst.sh:
HP OpenView VantagePoint A.06.13 (08/26/02)
/opt/OV/contrib/OpC/checkuiwww:
HP OpenView VantagePoint A.06.13 (08/26/02)
/opt/OV/contrib/OpC/MsgStorm/README:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/EC/
CIRCUITS/ECmsg_storm.eco:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/EC/
CIRCUITS/ECmsg_storm.ecs:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/EC/
ec.dat:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/
INTERFACE/interface.dat:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/C/TEMPLATES/
TEMPLGROUP/templgroup.dat:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/C/Template.idx:
None
/opt/OV/contrib/OpC/MsgStorm/Templates/download.dsf:
None
/opt/OV/contrib/OpC/MsgStorm/dstore.ds:
None
/opt/OV/contrib/OpC/MsgStorm/stormstartagt.sh:
None
/opt/OV/contrib/OpC/MsgStorm/stormstopagt.sh:
None
/etc/opt/OV/share/conf/OpC/mgmt_sv/seldist.tmpl:
None
/opt/OV/bin/OpC/install/opclic:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
OVOPC.OVOPC-GUI-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
/opt/OV/lib/nls/C/opcsv.cat:
None
/opt/OV/lib/nls/C/opcinstr.cat:
None
/opt/OV/OpC/dt/appconfig/types/C/opc.dt:
None
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/C/opcwww.cat:
None
/opt/OV/lib/nls/C/opcwwwinstr.cat:
None
OVOPC-WWW.OVOPC-WWW-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/libopcwww.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcuiwww:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcwwwmgrs.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcwwwpb.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcsvcmgr.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
OVOPC-ORA.OVOPC-UX-ORAA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/bin/OpC/opcactm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opccmm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcctlm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcdispm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcdistm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcecm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
trace.c $Revision: 1.12 $ $Date: 1998/03/12 04:48:38
$
annotate.c $Revision$ $Date$
circuit.c $Revision: /main/ECS3.0/4 $ $Date: 1999/04
/16 12:40 UTC $
DFIX12000:circuit.c 19mar99
endecode.c $Revision: 1.89 $ $Date: 1998/03/12 06:15
:55 $
engine.c $Revision: 1.15 $ $Date: 1997/08/14 00:08:4
2 $
engine_control.c $Revision: /main/ECS3.0/2 $ $Date:
1999/03/19 12:49 UTC $
DFIX12000:engine_control.c 19mar99
fatal.c $Revision: 1.13 $ $Date: 1998/05/07 02:26:33
$
input.c $Revision: /main/ECS3.0/2 $ $Date: 2001/03/2
0 13:13 UTC $
DFIX12007:input.c Mar2001
log.c $Revision: 1.7 $ $Date: 1997/07/04 07:34:11 $
mesgbuf.c $Revision: 1.18 $ $Date: 1998/05/07 00:28:
35 $
stream.c $Revision: 1.10 $ $Date: 1998/02/24 02:46:1
5 $
value.c $Revision: /main/ECS3.0/3 $ $Date: 2002/07/0
4 11:53 UTC $
DFIX12003:value.c 03April,2000
anno_event.c $Revision: 1.18 $ $Date: 1997/08/29 00:
49:58 $
bus.c $Revision$ $Date$
clock.c $Revision: /main/ECS3.0/2 $ $Date: 1999/03/1
9 12:47 UTC $
DFIX12000:clock.c 19mar99
combine.c $Revision: /main/ECS3.0/4 $ $Date: 2000/08
/29 09:10 UTC $
PATCH PHSS_22048, Sept 2000
DFIX12004 : combine.c, June2000
container.c $Revision: 1.17 $ $Date: 1998/02/18 00:4
9:18 $
count.c $Revision: /main/ECS3.0/2 $ $Date: 2000/07/1
3 08:54 UTC $
create.c $Revision$ $Date$
ctxtmap.c $Revision: 1.3 $ $Date: 1998/01/29 08:58:2
4 $
datastore.c $Revision: 1.8 $ $Date: 1998/07/25 18:31
:39 $
dfstore.c $Revision: /main/2 $ $Date: 1998/08/07 15:
39 UTC $
extract.c $Revision$ $Date$
factstore.c $Revision: 1.8 $ $Date: 1998/07/25 18:36
:10 $
filter.c $Revision$ $Date$
interpreter.c $Revision: /main/ECS3.0/2 $ $Date: 200
2/07/23 07:24 UTC $
loader.c $Revision$ $Date$
memory.c $Revision: /main/ECS3.0/1 $ $Date: 2002/04/
19 10:34 UTC $
modify.c $Revision$ $Date$
node.c $Revision: 1.44 $ $Date: 1998/05/01 04:33:53
$
nodeclass.c $Revision: 1.16 $ $Date: 1997/09/26 07:3
7:47 $
notify.c $Revision: 1.2 $ $Date: 1997/08/07 08:13:22
$
output.c $Revision$ $Date$
port.c $Revision: 1.11 $ $Date: 1996/05/15 05:45:40
$
query.c 1.16 1996/11/20 23:28:02
rate.c $Revision: /main/ECS3.0/4 $ $Date: 1999/09/01
10:30 UTC $
DFIX12000:rate.c 19mar99
PATCH PHSS_18006, Consolidated patch Mar 1999
rearrange.c $Revision$ $Date$
sequence.c $Revision: 1.17 $ $Date: 1998/01/28 03:39
:17 $
streamio.c $Revision: 1.13 $ $Date: 1998/04/01 06:16
:03 $
table.c $Revision: /main/ECS3.0/2 $ $Date: 1999/03/1
9 12:45 UTC $
DFIX12000:table.c 19mar99
unless.c $Revision: /main/ECS3.0/5 $ $Date: 2002/04/
19 14:00 UTC $
PATCH PHSS_26909, Apr 2002
DFIX12000:unless.c 19mar99
vstring.c $Revision: /main/2 $ $Date: 1998/08/21 10:
54 UTC $
memory.c $Revision$ $Date$
assembler.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:32 UTC $
bif_oid.c $Revision: 1.1 $ $Date: 1997/09/25 05:08:2
4 $
dicts.c $Revision: 1.18 $ $Date: 1998/03/27 09:02:35
$
delay.c $Revision$ $Date$
dicts.c $Revision: /main/ECS3.0/4 $ $Date: 2002/07/0
4 11:49 UTC $
PATCH PHSS_25944, Jan 2002
engine_dict.c $Revision: 1.7 $ $Date: 1998/03/23 07:
30:52 $
library.c $Revision: /main/ECS3.0/2 $ $Date: 2002/07
/23 07:25 UTC $
opc_pattern.c $Revision: /main/2 $ $Date: 1998/08/21
10:33 UTC $
trace.c $Revision: 1.4 $ $Date: 1998/06/10 09:01:45
$
transit.c $Revision$ $Date$
char_sets.c $Revision: /main/2 $ $Date: 1998/08/21 1
0:39 UTC $
dictionary.c $Revision: 1.23 $ $Date: 1998/04/01 06:
13:08 $
endecrypt.c $Revision: 1.1 $ $Date: 1997/10/15 09:57
:37 $
patching.c $Revision: 1.8 $ $Date: 1997/12/15 06:19:
31 $
/opt/OV/bin/OpC/opcmsgm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/utils/opcnode:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcragt:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcttnsm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/ovoareqsdr:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcforwm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opccfgout:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcannoadd:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcackmsg:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcackmsgs:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/utils/opcseldist:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/agtinstall/itosshupdate:
HP OpenView VantagePoint A.06.13 (08/26/02)
OVOPC-OVW.OVOPC-LIB-UTIL,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/libopcutil.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/lib/libopcxml.sl:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
OVOPC-JPN.OVOPC-GUI-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/lib/nls/ja_JP.SJIS/opcsv.cat:
None
/opt/OV/lib/nls/ja_JP.SJIS/opcinstr.cat:
None
/opt/OV/OpC/dt/appconfig/types/ja_JP.SJIS/opc.dt:
None
OVOPC-ORA.OVOPC-UX-ORAB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/opt/OV/bin/OpC/opccfgdwn:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opccfgupld:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcdbidx:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcuiopadm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcuitadm:
HP OpenView VantagePoint A.06.13 PHSS_27341 (08/26/0
2)
/opt/OV/bin/OpC/opcdbreorg:
HP OpenView VantagePoint A.06.13 (08/26/02)
cksum(1) Output:
OVOPC.OVOPC-MAN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
3521541489 2434 /opt/OV/man/man1m.Z/opcdbidx.1m
1989116479 5845 /opt/OV/www/htdocs/ito_man/opcdbidx.1m.html
3364614890 4633 /opt/OV/man/man1m.Z/opcnode.1m
1567446416 13197 /opt/OV/www/htdocs/ito_man/opcnode.1m.html
2499591430 3121 /opt/OV/man/man1m.Z/opcragt.1m
3509697846 7644 /opt/OV/www/htdocs/ito_man/opcragt.1m.html
4044817796 1602 /opt/OV/man/man1m.Z/opcseldist.1m
1186838775 4274 /opt/OV/www/htdocs/ito_man/
opcseldist.1m.html
1279119932 2759 /opt/OV/man/man1m.Z/opcdbreorg.1m
3522463028 8556 /opt/OV/www/htdocs/ito_man/
opcdbreorg.1m.html
1147276901 10072 /opt/OV/www/htdocs/ito_man/itoman_run.htm
OVOPC-WWW.OVOPC-WWW-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1410851091 11513326 /opt/OV/www/htdocs/ito_op/ITO_JAVA.exe
1640612107 1297060 /opt/OV/www/htdocs/ito_op/ito_op.jar
1448791772 3512320 /opt/OV/www/htdocs/ito_op/
ito_op_install.tar
782872526 4728 /opt/OV/www/htdocs/ito_op/ito_op
OVOPC.OVOPC-LIB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
3181082947 4366336 /opt/OV/lib/libopcsv_r.sl
1432895223 327680 /opt/OV/lib/libopcpb.sl
1158549898 540672 /opt/OV/lib/libopcsvcapi.sl
812270624 630784 /opt/OV/lib/libopcsvcreader.sl
OVOPC.OVOPC-GUI,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
2439975944 71407 /opt/OV/bin/OpC/opc.bin
1376900422 495616 /opt/OV/lib/libopcuiadm.sl
OVOPC-ORA.OVOPC-GUI-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
772474477 1732608 /opt/OV/lib/libopcdb.sl
4083435022 585728 /opt/OV/bin/OpC/opcuiop
OVOPC.OVOPC-UX-MGR78,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
70227969 12044 /opt/OV/contrib/OpC/SNMP6.2_cfgdwn/C/
SNMP6.2_.idx
2341946679 506351 /opt/OV/contrib/OpC/SNMP6.2_cfgdwn/C/
TEMPLATES/TRAP/trap.dat
3271129544 34 /opt/OV/contrib/OpC/SNMP6.2_cfgdwn/
download.dsf
2856844423 12052 /opt/OV/contrib/OpC/SNMP6.2_cfgdwn/
ja_JP.SJIS/SNMP6.2_.idx
1035630141 413694 /opt/OV/contrib/OpC/SNMP6.2_cfgdwn/
ja_JP.SJIS/TEMPLATES/TRAP/trap.dat
2872777661 1291270 /opt/OV/bin/OpC/opcuiadm.bin
2489130752 646028 /opt/OV/bin/OpC/opcuitadm.bin
2050201655 57344 /opt/OV/bin/OpC/ovoareqhdlr
1193130965 45056 /opt/OV/bin/OpC/install/opcagtutil
1852888904 69632 /opt/OV/contrib/OpC/opcqschk
3392680455 177246 /opt/OV/contrib/OpC/itochecker
2594054326 15389 /opt/OV/contrib/OpC/stacktrace
58292262 2766 /opt/OV/contrib/OpC/agent_platform.conf
4089131680 980320 /opt/OV/contrib/OpC/opcgetsvctree
1978187310 150603 /opt/OV/doc/C/OpC/
MessageStormDetection_1_0.pdf
391241650 118889 /opt/OV/doc/C/OpC/SelectiveDistribution.pdf
2689424960 4124672 /opt/OV/contrib/OpC/gdb32
1167072824 4214784 /opt/OV/contrib/OpC/gdb64
2555948319 75186 /opt/OV/bin/OpC/agtinstall/inst.sh
618923312 6706 /opt/OV/contrib/OpC/checkuiwww
4224285574 139 /opt/OV/contrib/OpC/MsgStorm/README
3416461613 162957 /opt/OV/contrib/OpC/MsgStorm/Templates/C/
TEMPLATES/EC/CIRCUITS/ECmsg_storm.eco
251237528 54637 /opt/OV/contrib/OpC/MsgStorm/Templates/C/
TEMPLATES/EC/CIRCUITS/ECmsg_storm.ecs
790168978 153 /opt/OV/contrib/OpC/MsgStorm/Templates/C/
TEMPLATES/EC/ec.dat
2684229053 1537 /opt/OV/contrib/OpC/MsgStorm/Templates/C/
TEMPLATES/INTERFACE/interface.dat
107440589 1801 /opt/OV/contrib/OpC/MsgStorm/Templates/C/
TEMPLATES/TEMPLGROUP/templgroup.dat
3617935661 818 /opt/OV/contrib/OpC/MsgStorm/Templates/C/
Template.idx
1752853610 177 /opt/OV/contrib/OpC/MsgStorm/Templates/
download.dsf
2151207863 626 /opt/OV/contrib/OpC/MsgStorm/dstore.ds
4257729337 2138 /opt/OV/contrib/OpC/MsgStorm/
stormstartagt.sh
1586649873 2146 /opt/OV/contrib/OpC/MsgStorm/stormstopagt.sh
2844128088 3842 /etc/opt/OV/share/conf/OpC/mgmt_sv/
seldist.tmpl
7438525 164872 /opt/OV/bin/OpC/install/opclic
OVOPC.OVOPC-GUI-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,v=HP:
1883371664 325352 /opt/OV/lib/nls/C/opcsv.cat
3607068445 323120 /opt/OV/lib/nls/C/opcinstr.cat
420180554 996 /opt/OV/OpC/dt/appconfig/types/C/opc.dt
OVOPC-WWW.OVOPC-WWW-ENG,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
334593754 6027 /opt/OV/lib/nls/C/opcwww.cat
3405345883 6675 /opt/OV/lib/nls/C/opcwwwinstr.cat
OVOPC-WWW.OVOPC-WWW-ORA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
1778463344 1712128 /opt/OV/lib/libopcwww.sl
2588324591 65536 /opt/OV/bin/OpC/opcuiwww
2811505831 675840 /opt/OV/lib/libopcwwwmgrs.sl
2442174791 122880 /opt/OV/lib/libopcwwwpb.sl
3516036875 630784 /opt/OV/lib/libopcsvcmgr.sl
OVOPC-ORA.OVOPC-UX-ORAA,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
566041173 86016 /opt/OV/bin/OpC/opcactm
3017301538 57344 /opt/OV/bin/OpC/opccmm
2986915134 148488 /opt/OV/bin/OpC/opcctlm
3183138230 143360 /opt/OV/bin/OpC/opcdispm
2928770966 237568 /opt/OV/bin/OpC/opcdistm
506091757 1458176 /opt/OV/bin/OpC/opcecm
1386489292 147456 /opt/OV/bin/OpC/opcmsgm
1466286241 61440 /opt/OV/bin/OpC/utils/opcnode
3950572735 94208 /opt/OV/bin/OpC/opcragt
3007632690 65536 /opt/OV/bin/OpC/opcttnsm
77020972 184320 /opt/OV/bin/OpC/ovoareqsdr
2298457648 94208 /opt/OV/bin/OpC/opcforwm
4203756305 40960 /opt/OV/bin/OpC/opccfgout
2505023620 40960 /opt/OV/bin/OpC/opcannoadd
2997857812 45056 /opt/OV/bin/OpC/opcackmsg
4081389156 49152 /opt/OV/bin/OpC/opcackmsgs
263718949 45056 /opt/OV/bin/OpC/utils/opcseldist
53541353 40398 /opt/OV/bin/OpC/agtinstall/itosshupdate
OVOPC-OVW.OVOPC-LIB-UTIL,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
3167356461 671744 /opt/OV/lib/libopcutil.sl
3943386577 544768 /opt/OV/lib/libopcxml.sl
OVOPC-JPN.OVOPC-GUI-JPN,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
3405176987 350203 /opt/OV/lib/nls/ja_JP.SJIS/opcsv.cat
1799187494 318597 /opt/OV/lib/nls/ja_JP.SJIS/opcinstr.cat
420180554 996 /opt/OV/OpC/dt/appconfig/types/ja_JP.SJIS/
opc.dt
OVOPC-ORA.OVOPC-UX-ORAB,fr=A.06.00,fa=HP-UX_B.11.00_32/64,
v=HP:
2734602672 245760 /opt/OV/bin/OpC/opccfgdwn
1590192151 892928 /opt/OV/bin/OpC/opccfgupld
461833701 77824 /opt/OV/bin/OpC/opcdbidx
1431605444 561152 /opt/OV/bin/OpC/opcuiopadm
2072374341 274432 /opt/OV/bin/OpC/opcuitadm
3827629827 66626 /opt/OV/bin/OpC/opcdbreorg
Patch Conflicts: None
Patch Dependencies:
s700: 11.00: PHSS_24264
s800: 11.00: PHSS_24264
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHSS_26757 PHSS_25639 PHSS_24687
Equivalent Patches:
ITOSOL_00156:
sparcSOL: 2.6 2.7 2.8
Patch Package Size: 48430 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHSS_27341
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHSS_27341.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHSS_27341. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHSS_27341.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHSS_27341.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHSS_27341.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
BEFORE LOADING THIS PATCH...
o This is an Intermediate Patch based on the
consolidated ITO patch PHSS_24264.
You MUST ensure that PHSS_24264 is installed
and configured BEFORE PHSS_27341 is installed.
You cannot install both PHSS_24264 and PHSS_27341
in the same swinstall session.
(A) Patch Installation Instructions
-------------------------------
(A1) Stop all VPO processes on your management server;
this includes manager processes, communication
processes and user-interface processes on the
machine.
1. Stop all VPO GUIs (including all Java GUIs
connected to this server). Use the "File: Exit"
menu bar item.
2. Stop the VPO manager processes:
# ovstop opc ovoacomm
If any VPO processes are still running, kill them
manually:
# kill -9 <pid-of-orphaned-process>
If you are running VPO in an MC/ServiceGuard
installation, you must apply this patch to all
MC/SG cluster nodes.
1. Files on the shared disk volumes at
/var/opt/OV/share and/or /etc/opt/OV/share
will be patched. Therefore either put the
package in maintenance mode or mount
the shared disks manually before installing
PHSS_27341.
- Put the package in maintenance mode
and leave the shared disks mounted:
# touch /tmp/maint_NNM
# ovstop opc ovoacomm
- Mount the shared disks manually:
# cmhaltpkg OpC
# vgchange -a e <shared_vg>
# mount <etc_shared_vol> /etc/opt/OV/share
# mount <var_shared_vol> /var/opt/OV/share
2. Install the patch on the first cluster node.
3. On the other cluster nodes, make sure the
OpC package is not running and the shared disks
are not mounted when PHSS_27341 is installed.
4. Install the patch on the other cluster nodes.
5. After the patch installation remove the following
files from the local disks because they already
exist on the shared disk:
# rm -rf /etc/opt/OV/share/*
# rm -rf /var/opt/OV/share/*
Note whenever you need to deinstall PHSS_27341, you
need to have the same state of the shared disks as
during the patch installation.
That is, for the patch deinstallation they must be
mounted where they were mounted during the patch
installation, and they must not be mounted where
they were not mounted at that time.
(A2) Install the patch following the standard installation
instructions provided above under "Installation
Instructions".
Observe that you can use opc_backup(5) for backing up
your system before installing a patch.
(A3) After installing PHSS_27341, restart the VPO
processes on your management server system:
- Restart the VPO manager processes, and check that
the processes are running:
# /opt/OV/bin/OpC/opcsv -start
# /opt/OV/bin/OpC/opcsv -status
If you are running VPO in an MC/ServiceGuard
installation:
- If you entered maintenance mode, return to full
monitoring:
# ovstart opc
# rm /tmp/maint_NNM
- If you stopped the OpC package, restart it:
# cmrunpkg OpC
(B) Patch Deinstallation Instructions
---------------------------------
NOTE: Before removing the patch, stop all
VPO server processes, as described in
the Patch Installation Instructions (A1).
If you are running VPO in an MC/ServiceGuard
installation, make sure to mount the shared
disks on the node and only on the node that
had them mounted during the patch installation.
Otherwise restoring the original files
onto the shared disk will fail. Be sure to
deinstall PHSS_27341 from all cluster nodes so that
all cluster nodes have the same revision.
(B1) To deinstall the patch PHSS_27341, run swremove:
# swremove PHSS_27341
-----End of Document ID: PHSS_27341------------------------------------------
Document ID: PHCO_27780
Date Loaded: 20020920
Title: s700_800 11.11 HP-UX Patch Tools
Patch Name: PHCO_27780
Patch Description: s700_800 11.11 HP-UX Patch Tools
Creation Date: 02/09/11
Post Date: 02/09/20
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CMDS-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_27780
Symptoms:
PHCO_27780:
( SR:8606218505 CR:JAGad87654)
check_patches identifies patch filesets that do not match
the current systems architecture as missing.
( SR:8606266501 CR:JAGae30748)
check_patches does not recognize directories as a valid
file type.
( SR:8606271930 CR:JAGae36108)
check_patches does not recognize swconfig version
B.11.20.00.06 as containing the required fix for patch
requisites.
( SR:8606274823 CR:JAGae38900)
check_patches reports missing filesets when the patch and
ancestor do not have the same fileset tags.
PHCO_24630:
( SR:8606195722 CR:JAGad64926 )
( SR:8606206277 CR:JAGad75452 )
The cleanup, show_patches, and check_patches tools are
not provided on HP-UX 11.11
Defect Description:
PHCO_27780:
( SR:8606218505 CR:JAGad87654)
Some patches apply only to 32- or 64-bit environments in
cases where the fileset being patched exists in both. The
check_patches utility did not contain the logic to
recognize that the filesets in the patch did not apply and
reported a split-patch error.
( SR:8606266501 CR:JAGae30748)
check_patches does not recognize directories as a valid
file type.
( SR:8606271930 CR:JAGae36108)
The version checking code for the swconfig fix-level test
was reporting certain newer versions as older and reporting
an error.
( SR:8606274823 CR:JAGae38900)
check_patches reports missing filesets when the patch and
ancestor do not have the same fileset tags.
PHCO_24630:
( SR:8606195722 CR:JAGad64926 )
( SR:8606206277 CR:JAGad75452 )
The improvements to SD-UX in HP-UX 11.11 did not eliminate
the need for patch tools. The cleanup tool is used to
commit patches while preserving a set level of rollback,
remove HP-UX 10.X patch information from the IPD, and prune
superseded patches from a depot. The check_patches utility
checks for partially installed (split) patches, incorrect
patch_state, patch attribute corruption, and objects within
an archive library. The show_patches tool can display the
set of active or superseded patches on a system.
Enhancement:
No (superseded patches contained enhancements)
PHCO_24630:
This patch delivers a set of tools to list, commit,
and verify HP-UX patches.
SR:
8606195722 8606206277 8606218505 8606266501 8606271930
8606274823
Patch Files:
OS-Core.CMDS-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/contrib/bin/check_patches
/usr/contrib/bin/show_patches
/usr/sbin/cleanup
/usr/contrib/man/man1m/check_patches.1m
/usr/contrib/man/man1/show_patches.1
/usr/share/man/man1m.Z/cleanup.1m
what(1) Output:
OS-Core.CMDS-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
/usr/contrib/bin/check_patches:
$Revision: 1.4 $ $Date: 2002/08/31 16:53:16 $
/usr/contrib/bin/show_patches:
$Revision: 1.2 $ $Date: 2001/07/16 02:11:31 $
/usr/sbin/cleanup:
$Revision: 1.5 $ $Date: 2001/07/17 02:11:15 $
/usr/contrib/man/man1m/check_patches.1m:
None
/usr/contrib/man/man1/show_patches.1:
None
/usr/share/man/man1m.Z/cleanup.1m:
None
cksum(1) Output:
OS-Core.CMDS-AUX,fr=B.11.11,fa=HP-UX_B.11.11_32/64,v=HP:
3890623847 28722 /usr/contrib/bin/check_patches
2483508162 7342 /usr/contrib/bin/show_patches
3064785842 48438 /usr/sbin/cleanup
783611235 1768 /usr/contrib/man/man1m/check_patches.1m
275196232 1526 /usr/contrib/man/man1/show_patches.1
1740596734 2195 /usr/share/man/man1m.Z/cleanup.1m
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_24630
Equivalent Patches:
PHCO_27779:
s700: 11.00
s800: 11.00
Patch Package Size: 120 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_27780
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_27780.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_27780. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_27780.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_27780.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_27780.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_27780------------------------------------------
Document ID: PHCO_27779
Date Loaded: 20020920
Title: s700_800 11.00 HP-UX Patch Tools and White Paper
Patch Name: PHCO_27779
Patch Description: s700_800 11.00 HP-UX Patch Tools and White Paper
Creation Date: 02/09/11
Post Date: 02/09/20
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
SW-DIST.SD-CMDS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.01,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.10.07,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.10.07.01,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.10.14,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.11.00.02,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.11.00.05,fa=HP-UX_B.11.00_32/64,v=HP
SW-DIST.SD-CMDS,fr=B.11.11.00.05.01,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.RELEASE-NOTES,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
Automatic Reboot?: No
Status: General Release
Critical: No
Category Tags:
defect_repair enhancement general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHCO_27779
Symptoms:
PHCO_27779:
- check_patches identifies patch filesets that do not match
the current systems architecture as missing.
SR: 8606218505 / CR: JAGad87654
- check_patches does not recognize directories as a valid
file type.
SR: 8606266501 / CR: JAGae30748
- check_patches reports missing filesets when the patch and
ancestor do not have the same fileset tags.
SR: 8606274823 / CR: JAGae38900
PHCO_24347:
- PHCO_22044 and prior patches do not install if a version
of Software Distributor newer than version B.11.00 is
installed. If explicitly marked for installation, the
following note will be displayed in the swagent.log file:
NOTE: The patch fileset "PHCO_22044.SD-CMDS,r=1.0" may
only be installed upon a previously installed
base fileset. The specification for this base
fileset is "SW-DIST.SD-CMDS,fr=B.11.00,v=HP".
Since there is no fileset on the target or
selected from the source which matches this
specification, fileset
"PHCO_22044.SD-CMDS,r=1.0" will be excluded.
SR: 8606164878 / CR: JAGad34175
- The cleanup utility does not 'commit' superseded patches
on systems with a version of SD-UX that turns off the
display of superseded patches.
SR: 8606169413 / CR: JAGad38688
- The cleanup utility does not recognize the
'committed/superseded' patch_state. Using the 'commit'
option of cleanup on patches with a patch_state of
'committed/superseded' causes errors similar to the
following to be displayed:
ERROR: swmodify(1M) encountered problems committing
the superseded patches:
ERROR: Cannot commit the patch fileset
"PHCO_13363.UX-CORE" in the target "/" because
its patch state is not "applied" or
"superseded".
SR: 8606193894 / CR: JAGad63104
PHCO_22044:
- The check_patches utility incorrectly reports that
PHKL_18543 should be reinstalled when incremental kernel
patches have been installed.
SR: 8606126914 / CR: JAGac59755
- The check_patches utility reports several instances of
'unknown line is_volatile true' if PHCO_19047 is
installed.
SR: 8606147011 / CR: JAGad16354
- Enhance the check_patches utility to check for the
situation where a patch fileset from an installed
multi-fileset patch is missing when the associated
product fileset is installed. This may occur when
a product fileset is installed, or reinstalled, after
a patch.
SR: 8606147015 / CR: JAGad16358
- The show_patches utility does not display any superseded
patches if SD-UX patch PHCO_20078, or one of its
successors, is installed and the 'show_superseded_patches'
option is set to 'false' in the defaults file.
SR: 8606147019 / CR: JAGad16362
PHCO_19550:
- The 'cleanup -i' command may exit without removing
HP-UX 10.X patches from the Installed Product Database.
SR: 8606103358 / CR: JAGab16794
- The 'cleanup -d' command cannot be used to manage depots
on an HP-UX 11.00 system that contain 10.X patches.
SR: 5003451245/ CR: JAGaa93182
- The cleanup(1M) utility cannot be used to remove
superseded patch information from /var/adm/sw/save, like
it could on the HP-UX 10.X releases. It is difficult to
recover space from /var/adm/sw/save using the
'swmodify -x patch_commit' command when dealing with a
large number of superseded patches.
SR: 5003451245 / CR: JAGab17265
SR: 5003465427 / CR: JAGab20769
SR: 5003467225 / CR: JAGab25232
- The patch_state attributes on HP-UX 11.00 patches can
be left in an inconsistent state due to incorrect or
inconsistent behavior by the SD-UX commands.
PHCO_18519:
- The check_patches utility checks for common problems
related to patches on HP-UX 11.00.
- The show_patches utility displays active and superseded
patches.
PHCO_13753:
- The remove_patches tool is intended to supplement the new
patch functionality of 11.0 SD. The tool is the swremove
counterpart of swinstall using the patch filter. It will
aid in the removal of patches, according to category
tags, from the large bundles that will be delivered as
part of 11.0's release plan.
- The cleanup utility can serve two purposes. First, it is
used to remove 10.X patches from the Installed Product
Database after updating to HP-UX 11.X. Second, it is
also used to remove patches from a software depot if the
patches have been superseded by patches also available in
the same depot.
- The HP-UX 11.X Patch Program White Paper is intended to
provide information, to system administrators, regarding
the 11.X patch structure as well as information on how to
acquire, install, check, commit and remove patches. It
also provides information on depot management and
installing patches from a depot.
Defect Description:
PHCO_27779:
- Some patches apply only to 32- or 64-bit environments in
cases where the fileset being patched exists in both. The
check_patches utility did not contain the logic to
recognize that the filesets in the patch did not apply
and reported a split-patch error.
SR: 8606218505 / CR: JAGad87654
Resolution:
- The filesets verified by check_patches now must match
the architecture of the active kernel.
- check_patches does not recognize directories as a valid
file type.
Resolution:
- The check for invalid file types was removed. It is not
a problem that is likely to be introduced on customer
systems.
SR: 8606266501 / CR: JAGae30748
- check_patches reports missing filesets when the patch and
ancestor do not have the same fileset tags.
SR: 8606274823 / CR: JAGae38900
Resolution:
- A check was added to see if a fileset might apply to more
than one ancestor.
PHCO_24347:
- PHCO_22044 and prior patches were designed when there was
only one supported version of Software Distributor (SD-UX)
on HP-UX 11.00. Now that multiple versions of SD-UX are
distributed and supported on HP-UX 11.00, this utility
patch must be constructed to install on any version of
SD-UX present on HP-UX 11.00.
SR: 8606164878 / CR: JAGad34175
Resolution:
- PHCO_24347 and superseding patches will be constructed
with the appropriate ancestor attributes to allow the
patches to be installed on any version of SD-UX.
- The cleanup utility was designed before Software
Distributor was modified to allow users to disable the
display of superseded patches in the swlist(1M) command.
SR: 8606169413 / CR: JAGad38688
Resolution:
- The cleanup utility has been updated to recognize
superseded patches even if the swlist(1M) command
does not display them by default.
- The cleanup utility was designed before Software
Distributor introduced the 'committed/superseded'
patch_state on HP-UX 11.00.
SR: 8606193894 / CR: JAGad63104
Resolution:
- The cleanup utility has been updated to recognize
the 'committed/superseded' patch state.
PHCO_22044:
- The check_patches utility was written before the release
of PHKL_18543 and was designed when only one
non-superseded patch contained information in the IPD
about a given kernel object module. The release of
PHKL_18543, the Line-In-The-Sand patch, and its
incremental patches changed this policy and invalidated
the design specification of check_patches.
SR: 8606126914 / CR: JAGac59755
Resolution:
- The check_patches utility will use the prerequisite
attribute that exists in all kernel incremental patches
to avoid reporting incorrect information about PHKL_18543.
- The check_patches utility only expected certain
information to be present in the IPD for patches. If it
encountered an attribute it did not expect, it reported an
'unknown line' message.
SR: 8606147011 / CR: JAGad16354
Resolution:
- The check_patches utility will ignore all attributes
in the IPD that do not provide information it requires.
- The check_patches utility was enhanced to check for
the situation where a patch fileset from an installed
multi-fileset patch is missing when the associated
product fileset is installed.
SR: 8606147015 / CR: JAGad16358
Resolution:
- A new option, '-m', has been added to the check_patches
utility to determine if patch filesets are missing. The
utility uses the patch README files stored in the IPD to
determine which product filesets to which the patch
applies. If one of these filesets is installed but the
corresponding patch fileset is missing it will report an
error.
- The behavior of swlist(1M) was modified in the SD-UX
patch PHCO_20078 to allow the suppression of superseded
patch information. Since the show_patches utility uses
swlist(1M) to obtain patch information, it did not report
superseded patch information since it was not provided by
swlist(1M).
SR: 8606147019 / CR: JAGad16362
Resolution:
- The show_patches utility will determine if the installed
version of swlist(1M) recognizes the
'show_superseded_patches' option and will use this option
when necessary.
PHCO_19550:
- The cleanup(1M) utility would exit prematurely when the
/var/adm/sw/patch directory was empty or non-existent,
even if HP-UX 10.X patches are present in the Installed
Product Database.
SR: 8606103358 / CR: JAGab16794
Resolution:
- Do not exit immediately if the /var/adm/sw/patch directory
is empty or non-existent.
- The cleanup(1M) depot management function was designed
only for depots containing 11.00 patches. However, HP-UX
11.00 systems can also be used to maintain depots with
10.X patches.
SR: 5003451245/ CR: JAGaa93182
Resolution:
- A new option, '-o', has been added to the cleanup(1M)
utility to specify if the depot contains HP-UX 10.X or
11.00 patches.
- The cleanup(1M) utility on HP-UX 11.00 was not designed
to commit patches, since this functionality is
implemented in the swmodify(1M) command. The cleanup(1M)
utility has been enhanced to provide an interface that
makes it easier to commit groups of superseded patches.
SR: 5003463851 / CR: JAGab17265
SR: 5003465427 / CR: JAGab20769
SR: 5003467225 / CR: JAGab25232
Resolution:
- A new option, '-c', has been added to the cleanup(1M)
utility to act as an interface to the
'swmodify -x patch_commit' command. This option allows
a group of superseded patches to be committed based on
the number of times they have been superseded on the
system. The actual committing of the patches is still
performed by the smwodify(1M) command, which is
invoked by cleanup(1M).
- The swconfig(1M), swinstall(1M), and swremove(1M) commands
are not consistent in the way the patch_state attribute is
set.
Resolution:
- A new option, '-s', has been added to the cleanup(1M)
utility to correct the patch_state attributes that are not
consistent. This does not solve the problem with the
SD-UX commands, but can be used to correct the patch_state
attributes after they have been set incorrectly.
PHCO_18519:
- The check_patches utility checks for common patch problems
on HP-UX 11.00 systems, such as:
- patches missing the SD-UX patch attributes
- patch object modules missing from archive libraries
- patch filesets not in the configured state
- patch filesets that fail swverify(1M)
- The show_patches utility displays the active and
superseded patches on the system in a formatted display.
Due to the different patch_states (applied, superseded,
and committed), using swlist(1M) to determine the state of
all patches on the system can be difficult. The
show_patches utility provides the information in a more
readable format.
PHCO_13753:
- As of 11.0, SD allows the filtering of installation of
patches with category tags. This filtering is not part
of the removal capability (swremove). The remove_patches
tool is being provided to allow patches to be removed
according to a specific category tag. By default, the tool
will remove all but the critical and hardware_enablement
patches.
- The cleanup utility is being provided to allow the removal
of patches belonging to HP-UX 10.X after a system has been
updated to HP-UX 11.X. It is also being provided to allow
the removal of superseded patches from a depot.
Enhancement:
No (superseded patches contained enhancements)
PHCO_18519:
Original deliver of check_patches(1m) and
show_patches(1).
PHCO_13753:
Original delivery of cleanup(1m)
SR:
5003451245 5003463851 5003465427 5003467225 8606103358
8606126914 8606147011 8606147015 8606147019 8606164878
8606169413 8606193894 8606218505 8606266501 8606274823
Patch Files:
SW-DIST.SD-CMDS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
SW-DIST.SD-CMDS,fr=B.11.01,fa=HP-UX_B.11.00_32/64,v=HP:
SW-DIST.SD-CMDS,fr=B.11.10.07,fa=HP-UX_B.11.00_32/64,v=HP:
SW-DIST.SD-CMDS,fr=B.11.10.07.01,fa=HP-UX_B.11.00_32/64,
v=HP:
SW-DIST.SD-CMDS,fr=B.11.10.14,fa=HP-UX_B.11.00_32/64,v=HP:
SW-DIST.SD-CMDS,fr=B.11.11.00.02,fa=HP-UX_B.11.00_32/64,
v=HP:
SW-DIST.SD-CMDS,fr=B.11.11.00.05,fa=HP-UX_B.11.00_32/64,
v=HP:
SW-DIST.SD-CMDS,fr=B.11.11.00.05.01,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/contrib/bin/check_patches
/usr/contrib/man/man1m/check_patches.1m
/usr/contrib/bin/show_patches
/usr/contrib/man/man1/show_patches.1
/usr/sbin/remove_patches
/usr/share/man/man1m/remove_patches.1m
/usr/sbin/cleanup
/usr/share/man/man1m.Z/cleanup.1m
OS-Core.RELEASE-NOTES,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/share/doc/patch_pgrm.txt
what(1) Output:
SW-DIST.SD-CMDS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
/usr/contrib/bin/check_patches:
$Revision: 1.30 (PHCO_22044)$ $Date: 00/07/14 $
/usr/contrib/man/man1m/check_patches.1m:
None
/usr/contrib/bin/show_patches:
$Revision: 1.04 (PHCO_22044)$ $Date: 00/07/14 $
/usr/contrib/man/man1/show_patches.1:
None
/usr/sbin/remove_patches:
$Revision: 1.17 $
/usr/share/man/man1m/remove_patches.1m:
None
/usr/sbin/cleanup:
$Revision: B.11.00.13 (PHCO_24347)$ $Date: 01/06/05$
/usr/share/man/man1m.Z/cleanup.1m:
None
OS-Core.RELEASE-NOTES,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
/usr/share/doc/patch_pgrm.txt:
None
cksum(1) Output:
SW-DIST.SD-CMDS,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP:
891280196 30964 /usr/contrib/bin/check_patches
3953708597 1732 /usr/contrib/man/man1m/check_patches.1m
328081655 7412 /usr/contrib/bin/show_patches
1449185154 1496 /usr/contrib/man/man1/show_patches.1
113848969 14668 /usr/sbin/remove_patches
4087050187 2152 /usr/share/man/man1m/remove_patches.1m
2001222442 49763 /usr/sbin/cleanup
2721765495 2199 /usr/share/man/man1m.Z/cleanup.1m
OS-Core.RELEASE-NOTES,fr=B.11.00,fa=HP-UX_B.11.00_32/64,
v=HP:
319935563 48725 /usr/share/doc/patch_pgrm.txt
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_13753 PHCO_18519 PHCO_19550 PHCO_22044 PHCO_24347
Equivalent Patches: None
Patch Package Size: 210 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHCO_27779
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHCO_27779.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHCO_27779. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHCO_27779.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHCO_27779.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_27779.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_27779------------------------------------------
Document ID: PHKL_27830
Date Loaded: 20020919
Title: s700_800 11.11 VxFS cumulative;VxFS 3-way deadlock;sendfile
Patch Name: PHKL_27830
Patch Description: s700_800 11.11 VxFS cumulative;VxFS 3-way deadlock;sendfile
Creation Date: 02/09/17
Post Date: 02/09/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27830: PANIC
PHKL_27554: HANG
PHKL_23374: CORRUPTION
PHKL_25022: HANG
PHKL_23241: PANIC HANG
PHKL_25463: HANG
Category Tags:
defect_repair enhancement general_release critical panic
halts_system corruption manual_dependencies
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27830
Symptoms:
PHKL_27830:
( SR:8606265910 CR:JAGae30163 )
Reallocation of a buffer with active sendcount may cause a
DPF in different subsystems that are using the same buffer.
The problem was observed when a file being transferred via
ftp or rcp over a slow network link got truncated by
another process while the transfer is still in progress.
The stack trace of the panicking thread may look like the
following but it could be different:
ip_csuma+0x68
ip_wput_ire+0x1cc
ip_wput+0xec
putnext+0xcc
tcp_wput+0x478
tcp_rput+0x3a18
puthere+0x148
put_release+0x194
put_release_return_one+0x10
ip_rput_local+0x778
ip_rput+0x16c
putnext+0xcc
hp_dlpi_mblk_fast_in+0x35c
hp_dlpi_mblk_intr_put+0x91c
streams_put+0xdc
streams_put_release+0x4c
hp_dlpi_mblk_intr+0x184
lanc_ether_ics+0xfc
btlan_receive_frame+0x5e4
btlan_isr+0xfc
sapic_interrupt+0x2c
mp_ext_interrupt+0x2f0
ihandler+0x90c
PHKL_27554:
( SR:8606262053 CR:JAGae26384 )
Filesystems commands that freeze filesystems (such as
fsadm resize) may deadlock with processes that use
F_WRLCK ioctl() to place locks on files in the filesystem.
A stack trace of the hung command will look similar to the
following:
_sleep+0x210
sleep_spinunlock+0x70
vx_event_wait+0xc0
vx_delay2+0x64
vx_freeze_level+0x278
vx_freeze+0x3c
vx_resize+0x120
vx_aioctl_full+0xf8
vx_aioctl_common+0x3b4
vx_aioctl+0xbc
vx_ioctl+0xc0
vno_ioctl+0x98
ioctl+0x120
syscall+0x750
$syscallrtn+0x0
Meanwhile, other threads will be sleeping with a stack trace
similar to the following:
_swtch+0xc4
_sleep+0x4cc
locked+0xd84
vx_rdwr+0x234
vno_rw+0x80
read+0x10c
syscall+0x204
$syscallrtn+0x0
_sleep+0x210
sleep_spinunlock+0x70
vx_event_wait+0xc0
vx_delay2+0x64
vx_active_common_flush+0xb8
vx_lockctl+0x3c
fcntl+0x2d4
syscall+0x750
$syscallrtn+0x0
PHKL_27121:
( SR:8606244250 CR:JAGae10740 )
After a file has been created with 000 permissions in a
directory with one or more default entries in its
Access Control List (ACL, see aclv(5)) on a VxFS
filesystem using the version 4 layout, all files created
in that directory will be created with 000 permissions
until the filesystem that directory is in is unmounted
and remounted, or the system is rebooted. The file which
initiated this condition need not have 000 permissions
at the end of the process that started its creation.
For example, if a file is copied into this directory
using cp(1), this condition will be triggered. cp(1)
first creates a file with 000 permissions, and then sets
the permissions as appropriate, using the permissions of
the copied file combined with the user's umask and the
parent directory's permission mask, which is based upon
the directory's default ACLs. Following this, some
commands such as cp(1) and mv(1) will behave as
documented since they explicitly set the permissions of
their target files, but others, such as touch(1) will
create files with 000 permissions since they do not
explicitly set the permissions of their targets, but
instead only use the user's umask and the parent
directory's mask. The permissions of affected files
can be corrected with chmod(1).
PHKL_26230:
( SR:8606224092 CR:JAGad93188 )
PHKL_25022 introduced behavior that can cause VxFS 3.3 file
system performance problems when sequential I/O requests of
less than 64KB are performed. This behavior can affect
backup utilities and other applications that perform
sequential I/O accesses to the file system.
PHKL_25885:
( SR:8606235772 CR:JAGae04912 )
Cannot deactivate a Volume Group that has at least one
VxFS file system, no mounted logical volumes, and no one
accessing any of the logical volumes in that VG:
# vgchange -a n /dev/vgtest
vgchange: Couldn't deactivate volume group "/dev/vgtest":
Device busy
( SR:8606221614 CR:JAGad90748 )
Access to a VxFS file system may hang when trying to
flush the intent log. A kernel stack trace of a hung
process will look similar to the following, and there
will be no process in vx_tranflush():
_sleep+0xa5c
sleep_spinunlock+0x70
vx_event_wait+0xc0
vx_delay2+0x64
vx_traninit+0x3d0
vx_write_alloc+0xc8
vx_write1+0x464
vx_rdwr+0x1e4
vno_rw+0x80
write+0x108
syscall+0x750
( SR:8606233921 CR:JAGae03144 )
VxFS performance may be slow when flushing the intent
log during intense file system modifications.
( SR:8606222925 CR:JAGad92031 )
VxFS performance may be slow when there is significant
write activity to the VxFS intent log.
PHKL_23374:
( SR:8606172239 CR:JAGad41499 )
close(2) may cause data corruption by truncating VxFS files.
PHKL_25022:
( SR:8606202113 CR:JAGad71287 )
VxFS may hang a 64 bit system by zeroing out the
interrupt mask (cr15).
( SR:8606198445 CR:JAGad67635 )
Applications invoking system calls fcntl(2) or lockf(2) may
deadlock with applications invoking system calls
truncate(2), ftruncate(2) or creat(2). An example of stack
traces of deadlocked threads is given below.
_sleep+0xa5c
sleep_spinunlock+0x70
vx_rwsleep_rec_lock_rec+0x90
vx_irwlock2_rec+0x3c
vx_getattr2+0x1b0
vx_getattr+0x58
enforcement_mode+0x48
locked+0x78
local_lockf+0xec
lockf+0x244
syscall+0xaec
syscallinit+0x554
_swtch+0x2d4
_mp_b_sema_sleep+0x108
vm_mmf_inval_lock+0x18
vx_setattr+0x304
vns_copen+0xc0
vn_open+0xb4
copen+0xa8
creat+0x44
syscall+0xaec
syscallinit+0x554
( SR:8606200313 CR:JAGad69497 )
Poor performance with VxFS compared to HP-UX 11.00 VxFS 3.1
while multiple threads/processes read from a file
simultaneously.
( SR:8606203915 CR:JAGad73093 )
PHKL_23240 introduced behavior that can cause multiple
threads to deadlock on a specific file. The behavior only
occurs if the file is being flushed at the same time it is
being remotely accessed, such as via NFS or other networking
access. The behavior could eventually lead to hung
processes and subsystems, such as NFS. This problem happens
only if VxFS fancy read ahead is turned on. Stacks of
deadlocked threads may look like as shown below.
_sleep+0x1fc
sleep_spinunlock+0x74
vx_event_wait+0xf0
vx_delay2+0x64
vx_vnode_flush+0x3bc
vx_do_putpage+0x11c
vx_idelxwri_flush+0xf8
vx_delxwri_flush+0x1dc
vx_worklist_process+0x1b0
vx_worklist_thread+0x4c
kthread_daemon_startup+0x24
_sleep+0x1fc
vx_rwsleep_lock+0x1f4
vx_iglock2+0x78
vx_iglock+0x28
vx_fancy_read_ahead+0x1c4
vx_read1+0x980
vx_vn_bread+0xfc
rfs_read+0x158
rfsexp_dispatch+0x210
svc_getreq+0x13c
svc_run+0x1e0
nfsexp_svc+0x4d4
nfs_stub_svc+0xa4
coerce_scall_args+0xcc
syscall+0x6f8
syscallinit+0x54c
PHKL_23241:
( SR:8606179185 CR:JAGad48409 )
Poor application performance with VxFS compared to VxFS 3.1
(default version of VxFS on HP-UX 11.00) when the
application does a lot of reads from random offsets of a
file.
( SR:8606183708 CR:JAGad52921 )
Data Page Fault while using Hyperfabric network. Stack of
the panic thread may look like,
panic+0x14
report_trap_or_int_and_panic+0x84
interrupt+0x1d4
$ihndlr_rtn+0x0
sendfile_rele+0x304
freeb_pullupmsg+0x238
freeb+0x7b4
CLIC_SEND+0x1ecc
clicdlpi_wput+0x140
putnext+0xcc
ip_wput_ire+0x454
ip_wput+0x470
putnext+0xcc
tcp_timer+0x334
tcp_wput+0x828
puthere+0x148
mi_timeout_exec+0x294
sw_service+0xb0
mp_ext_interrupt+0x150
ivti_patch_to_nop3+0x0
idle+0x81c
( SR:8606178276 CR:JAGad47503 )
System hang caused by a thread going through the buffer pool
to flush out dirty buffers. A buffer is marked dirty but
also marked busy, and the process or thread decides to wait
for it. Because of this, ServiceGuard commands such as
cmapplyconf and cmcheckconf hang. A typical stack of the
hung thread is given below.
_swtch+0x138
real_sleep+0x234
_sleep+0x14
syncip_flush_cache+0x190
vx_flushdev+0x10
vx_fsync+0x1cc
spec_fsync+0x17c
spec_inactive+0x14
vn_rele+0x1e8
vno_close+0x68
closef+0x68
close+0x30
syscall+0x75c
$syscallrtn+0x0
( SR:8606188296 CR:JAGad57504 )
Backup utilities such as fbackup take longer to finish
when JFS fancy read ahead is enabled, i.e., when
vx_fancyra_enable is set to a non-zero value in the system
file.
( SR:8606181938 CR:JAGad51154 )
Data Page Fault in allocbuf1(). Stack of the panic thread
may look like,
allocbuf1+0xd0
allocbuf+0x30
vx_allocbuf+0x30
vx_async_shorten+0xc30
vx_fsync+0x120
rfs3_commit+0x3a0
rfsexp_dispatch+0x810
svc_getreq+0x500
svc_run+0x930
nfsexp_svc+0x860
nfs_stub_svc+0x390
coerce_scall_args+0x570
syscall+0xe70
( SR:8606179211 CR:JAGad48435 )
sar -v and glance show ninode usage (count of active inodes
on the system) as 0.
PHKL_23240:
( SR:8606175335 CR:JAGad44577 )
Poor system performance with VxFS vs HFS, when applications
like Nastran and Abaqus, which read backward and forward
through a file which cannot be fully contained in the buffer
cache.
PHKL_25360:
( SR:8606209887 CR:JAGad79073 )
Poor vxfs mount performance on systems with large buffer
caches
PHKL_25463:
( SR:8606202670 CR:JAGad71844 )
High end systems may thrash when large number of threads
access a single VxFS filesystem. System may appear to be
hung.
Defect Description:
PHKL_27830:
( SR:8606265910 CR:JAGae30163 )
Reallocation of an active sendcount buffer may cause a DPF
panic in various subsystems when the size of the buffer
with active sendcnt, is changed (i.e., through a delayed
extended operation after truncation of a file).
Resolution:
Reallocation of an active sendcount buffer should invalidate
the buffer. The buffer should be flushed to the disk if it
is a delayed write buffer, before being invalidated.
PHKL_27554:
( SR:8606262053 CR:JAGae26384 )
A thread trying to read a file is allowed to sleep
waiting for the read/write lock owned by another
thread while the filesystem active count is incremented.
The hang occurs when another thread tries to freeze the
filesystem before the read/write lock can be released,
and hangs in vx_freeze_level(). When the thread tries
to release the read/write lock, it hangs in
vx_active_common_flush() due to the pending freeze.
Resolution:
The active count is now decremented before calling locked()
and sleeping on the read/write lock. Once the lock is
obtained, the active count is incremented again.
PHKL_27121:
( SR:8606244250 CR:JAGae10740 )
The mode of a newly created file on a VxFS filesystem
using the version 4 layout (see vxupgrade(1M)) is
determined by the mode passed into open(2) or creat(2)
combined with the user's umask and the modemask of a
directory, determined by its default ACLs. When default
ACLs exist, the modemask of the directory would be set to
the mode passed into open(2) or creat(2). From the time
when a file is created with mode 000 on, all subsequently
created files in that directory with default ACLs would be
given 000 permissions.
Resolution:
The modemasks of directories are no longer affected by the
modes of created files.
PHKL_26230:
( SR:8606224092 CR:JAGad93188 )
The readahead algorithm was incorrectly using
max_buf_data_size (default 8Kb) to calculate the readahead
size instead of read_pref_io (default 64kb)
which resulted in a smaller readahead size.
Resolution:
Use read_pref_io to calculate the readahead size.
PHKL_25885:
( SR:8606235772 CR:JAGae04912 )
A failed VxFS mount leaves the device opened.
Resolution:
Ensure device is closed when a VxFS mount fails.
( SR:8606221614 CR:JAGad90748 )
During the flushing of a transaction, a condition
occurred such that the transaction needed to be
retried, but was not. Since the transaction was
never flushed, the intent log fills up and access
to the file system hangs.
Resolution:
Assure proper retry of transactions under all
conditions.
( SR:8606233921 CR:JAGae03144 )
VxFS intent log processing is done using 1K buffers.
Resolution:
Allow larger I/O's when flushing the intent log by
introducing a new logiosize mount option. For
example:
mount -F vxfs -o logiosize=4096
Valid values for logiosize are 1024, 2048, and 4096.
( SR:8606222925 CR:JAGad92031 )
VxFS fails to detect that the intent log is filling
up.
Resolution:
Changed internal VxFS threshold values used to detect
how full the log is to lower values to allow earlier
detection that the log is filling up.
PHKL_23374:
( SR:8606172239 CR:JAGad41499 )
While closing (close(2)) a file, VxFS tried to free up extra
space (extents) allocated to the file. While doing this, it
incorrectly modified the actual file size, causing data
loss.
Resolution:
Corrected logic to prevent modification of file size while
freeing extra extents.
PHKL_25022:
( SR:8606202113 CR:JAGad71287 )
VxFS was using a wrong data type (unsigned int) with
spinlock functions. Spinlock functions use "unsigned long".
Resolution:
Use the correct data type (unsigned long) with spinlock
functions.
( SR:8606198445 CR:JAGad67635 )
A lock was acquired in the wrong order in a VxFS function
invoked by system calls fcntl(2) and lockf(2).
Resolution:
Eliminated the cases where the lock was acquired in the
wrong order.
( SR:8606200313 CR:JAGad69497 )
1. VxFS read ahead code relies on the unexpected read
(buffer cache miss) count to determine if there is any
pressure on buffer cache. If there is pressure on buffer
cache, the amount of read ahead performed is reduced. If
the read ahead performed is less than the size of the read
size, there will be unexpected reads. This turns out into a
self fulfilling prophecy and read ahead is completely turned
off causing each read to read the data from the disk
synchronously degrading performance.
2. VxFS uses the vxtunefs(1M) tunable "read_pref_io"
to calculate the intial and maximum read ahead region
length. But the read sizes could vary and this tunable may
not trigger enough read ahead for different read sizes.
Resolution:
1. Use the current read request size as the floor for the
read ahead region length.
2. Use the current read request size times the vxtunefs(1M)
"read_nstream" as the ceiling for the read ahead region
length.
( SR:8606203915 CR:JAGad73093 )
VxFS read code was acquiring two locks in the wrong
order causing deadlock.
Resolution:
VxFS read code is rewritten eliminating the need to
acquire the locks in the wrong order.
PHKL_23241:
( SR:8606179185 CR:JAGad48409 )
A sanity check at the wrong place in a function disabled
read ahead for random reads to a file.
Resolution:
Move the sanity check to the correct place in the function
so that some read ahead can be done for random reads.
( SR:8606183708 CR:JAGad52921 )
VxFS may free a vnode while a buffer associated with that
vnode is in use in sendfile(2). Later when the sendfile
code accesses the vnode through the buffer, the system
panics.
Resolution:
Set up a dummy vnode which is not freed and use that vnode
for buffers passed to sendfile(2) so that sendfile(2)
code will always be accessing a valid vnode.
( SR:8606178276 CR:JAGad47503 )
In some corner cases, some VxFS meta buffers (map buffers)
will be left in a busy and dirty state. This leads to a
process hang for any process which is directly or indirectly
doing a buffer cache flush.
Resolution:
Make sure the VxFS meta buffers are flushed before doing
a buffer cache flush.
( SR:8606188296 CR:JAGad57504 )
The VxFS fancy read ahead feature degrades read performance
when multiple process/threads read from a file
simultaneously. Because the VxFS fancy read ahead feature
was designed to handle only one reader for a file at a
time, when there are multiple readers for a file its read
ahead pattern matching algorithm fails. This results in
many unnecessary I/Os.
Resolution:
When there are multiple readers to a file, disable fancy
read and do sequential read ahead instead.
( SR:8606181938 CR:JAGad51154 )
allocbuf1() expects a non-zero value as its second
argument, but VxFS was not always passing a non-zero
value.
Resolution:
Make sure that a non-zero value is always passed as the
second argument to allocbuf1() from VxFS code.
( SR:8606179211 CR:JAGad48435 )
VxFS was decrementing the number of active inode count
instead of incrementing it when inodes became active.
Resolution:
Increment active inode count when inodes become active.
PHKL_23240:
( SR:8606175335 CR:JAGad44577 )
An incorrect sanity check in the VxFS read path turned off
both normal read ahead and fancy read ahead when the fancy
read ahead was enabled on the system. This caused large I/O
wait times for each read.
Resolution:
Corrected the logic error in the sanity check code such that
fancy read ahead is used when enabled.
PHKL_25360:
( SR:8606209887 CR:JAGad79073 )
VXFS mount(2) performance varies depending on the size of
the buffer cache but can be poor for systems with large
buffer caches. The majority of the time is spent in
flushing/invalidation routines which search all buffer
headers then search all hash buckets respectively at VXFS
file system initialization. These flushing/invalidation
routines should not be required since no data should reside
in the buffer cache for the device being mounted.
Resolution:
To reduce the mount time aforementioned,
flushing/invalidation calls are removed.
PHKL_25463:
( SR:8606202670 CR:JAGad71844 )
VxFS logs each operation on the filesystem. When a thread
cannot find free space in the log, it sleeps 2 seconds and
tries again.
The problem arises when there is a large number of threads
operating on the filesystem causing the log to be full most
of the time. All these threads sleep 2 seconds and then
check the log space. This causes the system to thrash
keeping the processors busy all the time. The threads which
are supposed to free up the log space can never do that.
Resolution:
Increase the sleeping time of the threads in each iteration
instead of sleeping 2 seconds always.
Enhancement:
No (superseded patches contained enhancements)
PHKL_27830:
Enhancements were delivered in a patch this one has
superseded. Please review the Defect Description
text for more information.
SR:
8606172239 8606175335 8606178276 8606179185 8606179211
8606181938 8606183708 8606188296 8606198445 8606200313
8606202113 8606202670 8606203915 8606209887 8606221614
8606222925 8606224092 8606233921 8606235772 8606244250
8606262053 8606265910
Patch Files:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o)
/usr/conf/lib/libvxfs.a(vx_ausum.o)
/usr/conf/lib/libvxfs.a(vx_bio.o)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o)
/usr/conf/lib/libvxfs.a(vx_freeze.o)
/usr/conf/lib/libvxfs.a(vx_full.o)
/usr/conf/lib/libvxfs.a(vx_iflush.o)
/usr/conf/lib/libvxfs.a(vx_inode.o)
/usr/conf/lib/libvxfs.a(vx_kdmi.o)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
/usr/conf/lib/libvxfs.a(vx_lct.o)
/usr/conf/lib/libvxfs.a(vx_lwrite.o)
/usr/conf/lib/libvxfs.a(vx_machdep.o)
/usr/conf/lib/libvxfs.a(vx_message.o)
/usr/conf/lib/libvxfs.a(vx_mount.o)
/usr/conf/lib/libvxfs.a(vx_oltmount.o)
/usr/conf/lib/libvxfs.a(vx_rdwri.o)
/usr/conf/lib/libvxfs.a(vx_tran.o)
/usr/conf/lib/libvxfs.a(vx_vfsops.o)
/usr/conf/lib/libvxfs.a(vx_vnops.o)
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o)
/usr/conf/lib/libvxfs.a(vx_ausum.o)
/usr/conf/lib/libvxfs.a(vx_bio.o)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o)
/usr/conf/lib/libvxfs.a(vx_freeze.o)
/usr/conf/lib/libvxfs.a(vx_full.o)
/usr/conf/lib/libvxfs.a(vx_iflush.o)
/usr/conf/lib/libvxfs.a(vx_inode.o)
/usr/conf/lib/libvxfs.a(vx_kdmi.o)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
/usr/conf/lib/libvxfs.a(vx_lct.o)
/usr/conf/lib/libvxfs.a(vx_lwrite.o)
/usr/conf/lib/libvxfs.a(vx_machdep.o)
/usr/conf/lib/libvxfs.a(vx_message.o)
/usr/conf/lib/libvxfs.a(vx_mount.o)
/usr/conf/lib/libvxfs.a(vx_oltmount.o)
/usr/conf/lib/libvxfs.a(vx_rdwri.o)
/usr/conf/lib/libvxfs.a(vx_tran.o)
/usr/conf/lib/libvxfs.a(vx_vfsops.o)
/usr/conf/lib/libvxfs.a(vx_vnops.o)
what(1) Output:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o):
vx_acl.c $Date: 2002/05/16 14:11:52 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_27121)
/usr/conf/lib/libvxfs.a(vx_ausum.o):
vx_ausum.c $Date: 2002/04/19 05:55:51 $Revision: r11
.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_bio.o):
vx_bio.c $Date: 2002/09/03 23:16:21 $Revision: r11.1
1/3 PATCH_11.11 (PHKL_27830)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o):
vx_bitmaps.c $Date: 2002/04/19 05:56:53 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_freeze.o):
vx_freeze.c $Date: 2002/04/19 05:57:23 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_full.o):
vx_full.c $Date: 2002/04/19 05:58:26 $Revision: r11.
11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_iflush.o):
vx_iflush.c $Date: 2001/08/27 08:06:20 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_inode.o):
vx_inode.c $Date: 2002/04/19 05:58:56 $Revision: r11
.11/5 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_kdmi.o):
vx_kdmi.c $Date: 2001/08/27 08:06:20 $Revision: r11.
11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o):
vx_kdmi_machdep.c $Date: 2001/08/27 08:06:20 $Revisi
on: r11.11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_lct.o):
vx_lct.c $Date: 2002/04/19 05:59:25 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_lwrite.o):
vx_lwrite.c $Date: 2002/04/19 05:59:56 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_machdep.o):
vx_machdep.c $Date: 2002/04/19 06:00:28 $Revision: r
11.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_message.o):
vx_message.c $Date: 2002/04/19 06:01:28 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_mount.o):
vx_mount.c $Date: 2002/04/19 06:02:00 $Revision: r11
.11/4 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_oltmount.o):
vx_oltmount.c $Date: 2002/04/19 06:02:33 $Revision:
r11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_rdwri.o):
vx_rdwri.c $Date: 2002/03/12 09:00:57 $Revision: r11
.11/4 PATCH_11.11 (PHKL_26230)
/usr/conf/lib/libvxfs.a(vx_tran.o):
vx_tran.c $Date: 2002/04/19 06:03:34 $Revision: r11.
11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vfsops.o):
vx_vfsops.c $Date: 2002/04/19 06:04:51 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vnops.o):
vx_vnops.c $Date: 2002/07/22 08:08:47 $Revision: r11
.11/4 PATCH_11.11 (PHKL_27554)
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libvxfs.a(vx_acl.o):
vx_acl.c $Date: 2002/05/16 14:11:52 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_27121)
/usr/conf/lib/libvxfs.a(vx_ausum.o):
vx_ausum.c $Date: 2002/04/19 05:55:51 $Revision: r11
.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_bio.o):
vx_bio.c $Date: 2002/09/03 23:16:21 $Revision: r11.1
1/3 PATCH_11.11 (PHKL_27830)
/usr/conf/lib/libvxfs.a(vx_bitmaps.o):
vx_bitmaps.c $Date: 2002/04/19 05:56:53 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_freeze.o):
vx_freeze.c $Date: 2002/04/19 05:57:23 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_full.o):
vx_full.c $Date: 2002/04/19 05:58:26 $Revision: r11.
11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_iflush.o):
vx_iflush.c $Date: 2001/08/27 08:06:20 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_inode.o):
vx_inode.c $Date: 2002/04/19 05:58:56 $Revision: r11
.11/5 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_kdmi.o):
vx_kdmi.c $Date: 2001/08/27 08:06:20 $Revision: r11.
11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o):
vx_kdmi_machdep.c $Date: 2001/08/27 08:06:20 $Revisi
on: r11.11/1 PATCH_11.11 (PHKL_25022)
/usr/conf/lib/libvxfs.a(vx_lct.o):
vx_lct.c $Date: 2002/04/19 05:59:25 $Revision: r11.1
1/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_lwrite.o):
vx_lwrite.c $Date: 2002/04/19 05:59:56 $Revision: r1
1.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_machdep.o):
vx_machdep.c $Date: 2002/04/19 06:00:28 $Revision: r
11.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_message.o):
vx_message.c $Date: 2002/04/19 06:01:28 $Revision: r
11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_mount.o):
vx_mount.c $Date: 2002/04/19 06:02:00 $Revision: r11
.11/4 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_oltmount.o):
vx_oltmount.c $Date: 2002/04/19 06:02:33 $Revision:
r11.11/2 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_rdwri.o):
vx_rdwri.c $Date: 2002/03/12 09:00:57 $Revision: r11
.11/4 PATCH_11.11 (PHKL_26230)
/usr/conf/lib/libvxfs.a(vx_tran.o):
vx_tran.c $Date: 2002/04/19 06:03:34 $Revision: r11.
11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vfsops.o):
vx_vfsops.c $Date: 2002/04/19 06:04:51 $Revision: r1
1.11/3 PATCH_11.11 (PHKL_25885)
/usr/conf/lib/libvxfs.a(vx_vnops.o):
vx_vnops.c $Date: 2002/07/22 08:08:47 $Revision: r11
.11/4 PATCH_11.11 (PHKL_27554)
cksum(1) Output:
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_32,v=HP:
3216430162 9504 /usr/conf/lib/libvxfs.a(vx_acl.o)
1784073030 10884 /usr/conf/lib/libvxfs.a(vx_ausum.o)
3392788103 15396 /usr/conf/lib/libvxfs.a(vx_bio.o)
3520053438 12728 /usr/conf/lib/libvxfs.a(vx_bitmaps.o)
2690520352 12376 /usr/conf/lib/libvxfs.a(vx_freeze.o)
2799065042 18128 /usr/conf/lib/libvxfs.a(vx_full.o)
2665133960 33576 /usr/conf/lib/libvxfs.a(vx_iflush.o)
323221505 49836 /usr/conf/lib/libvxfs.a(vx_inode.o)
3250051741 24496 /usr/conf/lib/libvxfs.a(vx_kdmi.o)
2522834320 7240 /usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
4009177794 8480 /usr/conf/lib/libvxfs.a(vx_lct.o)
4121613688 17592 /usr/conf/lib/libvxfs.a(vx_lwrite.o)
1481605065 28572 /usr/conf/lib/libvxfs.a(vx_machdep.o)
3752135938 8180 /usr/conf/lib/libvxfs.a(vx_message.o)
1087813011 31320 /usr/conf/lib/libvxfs.a(vx_mount.o)
1294799996 32180 /usr/conf/lib/libvxfs.a(vx_oltmount.o)
2281410209 41836 /usr/conf/lib/libvxfs.a(vx_rdwri.o)
270591386 23276 /usr/conf/lib/libvxfs.a(vx_tran.o)
979291995 14052 /usr/conf/lib/libvxfs.a(vx_vfsops.o)
735331197 40072 /usr/conf/lib/libvxfs.a(vx_vnops.o)
JFS.VXFS-BASE-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
1981697599 18496 /usr/conf/lib/libvxfs.a(vx_acl.o)
1045982338 24576 /usr/conf/lib/libvxfs.a(vx_ausum.o)
6308320 35992 /usr/conf/lib/libvxfs.a(vx_bio.o)
1687228884 30904 /usr/conf/lib/libvxfs.a(vx_bitmaps.o)
1118841624 30664 /usr/conf/lib/libvxfs.a(vx_freeze.o)
1871455838 33336 /usr/conf/lib/libvxfs.a(vx_full.o)
3305413657 81864 /usr/conf/lib/libvxfs.a(vx_iflush.o)
743682268 117144 /usr/conf/lib/libvxfs.a(vx_inode.o)
3696787517 50720 /usr/conf/lib/libvxfs.a(vx_kdmi.o)
24230761 12712 /usr/conf/lib/libvxfs.a(vx_kdmi_machdep.o)
2225834659 19240 /usr/conf/lib/libvxfs.a(vx_lct.o)
527288551 29984 /usr/conf/lib/libvxfs.a(vx_lwrite.o)
1354466836 75336 /usr/conf/lib/libvxfs.a(vx_machdep.o)
4076061111 12784 /usr/conf/lib/libvxfs.a(vx_message.o)
4218106221 63904 /usr/conf/lib/libvxfs.a(vx_mount.o)
1154391494 54632 /usr/conf/lib/libvxfs.a(vx_oltmount.o)
4138374309 68136 /usr/conf/lib/libvxfs.a(vx_rdwri.o)
552446673 46080 /usr/conf/lib/libvxfs.a(vx_tran.o)
961939630 30376 /usr/conf/lib/libvxfs.a(vx_vfsops.o)
3620222898 82304 /usr/conf/lib/libvxfs.a(vx_vnops.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies:
PHKL_25885: PHCO_26252 is needed to use logiosize=4096.
Supersedes:
PHKL_27554 PHKL_27121 PHKL_26230 PHKL_25885 PHKL_25463 PHKL_25360
PHKL_25022 PHKL_23374 PHKL_23241 PHKL_23240
Equivalent Patches: None
Patch Package Size: 1420 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_27830
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27830.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27830. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_27830.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_27830.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27830.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_27830------------------------------------------
Document ID: PHKL_27778
Date Loaded: 20020919
Title: s700_800 11.11 V-Class EPIC error handler patch
Patch Name: PHKL_27778
Patch Description: s700_800 11.11 V-Class EPIC error handler patch
Creation Date: 02/09/04
Post Date: 02/09/19
Hardware Platforms - OS Releases:
s700: 11.11
s800: 11.11
Products: N/A
Filesets:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical: No
Category Tags:
defect_repair general_release
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27778
Symptoms:
PHKL_27778:
( SR:8606268193 CR:JAGae32432 )
V-class EPIC Error Handler reports wrong device and driver
Defect Description:
PHKL_27778:
( SR:8606268193 CR:JAGae32432 )
V-class EPIC Error Handler reports wrong device and driver
Resolution:
Detect the initial device that caused TARGET ABORT error
Enhancement:
No
SR:
8606268193
Patch Files:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpci.a(epic_errors.o)
what(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
/usr/conf/lib/libpci.a(epic_errors.o):
epic_errors.c $Date: 2002/08/26 08:22:27 $Revision:
r11.11/1 PATCH_11.11 (PHKL_27778)
cksum(1) Output:
OS-Core.CORE2-KRN,fr=B.11.11,fa=HP-UX_B.11.11_64,v=HP:
1848675262 24056 /usr/conf/lib/libpci.a(epic_errors.o)
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies:
9000/800
V-class
Other Dependencies: None
Supersedes: None
Equivalent Patches: None
Patch Package Size: 40 KBytes
Installation Instructions:
Please review all instructions and the Hewlett-Packard
SupportLine User Guide or your Hewlett-Packard support terms
and conditions for precautions, scope of license,
restrictions, and, limitation of liability and warranties,
before installing this patch.
------------------------------------------------------------
1. Back up your system before installing a patch.
2. Login as root.
3. Copy the patch to the /tmp directory.
4. Move to the /tmp directory and unshar the patch:
cd /tmp
sh PHKL_27778
5. Run swinstall to install the patch:
swinstall -x autoreboot=true -x patch_match_target=true \
-s /tmp/PHKL_27778.depot
By default swinstall will archive the original software in
/var/adm/sw/save/PHKL_27778. If you do not wish to retain a
copy of the original software, include the patch_save_files
option in the swinstall command above:
-x patch_save_files=false
WARNING: If patch_save_files is false when a patch is installed,
the patch cannot be deinstalled. Please be careful
when using this feature.
For future reference, the contents of the PHKL_27778.text file is
available in the product readme:
swlist -l product -a readme -d /tmp/PHKL_27778.depot
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_27778.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHKL_27778------------------------------------------
Document ID: PHKL_27759
Date Loaded: 20020919
Title: s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,AIO,T600,FS,Hang
Patch Name: PHKL_27759
Patch Description: s700_800 11.00 Probe,IDDS,PM,VM,PA-8700,AIO,T600,FS,Hang
Creation Date: 02/09/12
Post Date: 02/09/19
Hardware Platforms - OS Releases:
s700: 11.00
s800: 11.00
Products: N/A
Filesets:
OS-Core.CORE-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
ProgSupport.C-INC,fr=B.11.00,fa=HP-UX_B.11.00_32/64,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_32,v=HP
OS-Core.CORE2-KRN,fr=B.11.00,fa=HP-UX_B.11.00_64,v=HP
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_27759: PANIC
PHKL_27157: ABORT CORRUPTION
PHKL_26800: HANG
Hang - Filesystem or Process Hang
PHKL_25906: PANIC
PHKL_25525: HANG
PHKL_25210: PANIC CORRUPTION
PHKL_25188: PANIC
PHKL_25164: PANIC
PHKL_24612: ABORT
PHKL_24457: PANIC
PHKL_24273: PANIC
The system panics when r_refcnt overflows
PHKL_24116: OTHER
Hung, Unkillable Process
PHKL_24015: PANIC
PHKL_23857: CORRUPTION
PHKL_23813: PANIC
PHKL_23812: HANG
PHKL_23406: OTHER
Hung, Unkillable Process
PHKL_23183: OTHER
A program that uses probe instruction will cause
signal handler to be removed. It will cause a
non-access reference to an invalid virtual memory
address causing SIGSEGV handler to be removed.
So, the application's signal handler is not
invoked and it does not know what to do.
PHKL_22493: PANIC
PHKL_21775: HANG
PHKL_21507: PANIC
PHKL_20439: PANIC MEMORY_LEAK
PHKL_22744: PANIC
PHKL_22549: PANIC
PHKL_22380: PANIC HANG
PHKL_22126: PANIC
PHKL_21781: PANIC CORRUPTION
PHKL_21624: HANG
PHKL_21600: PANIC
PHKL_20647: HANG
PHKL_20449: PANIC
PHKL_20223: PANIC
PHKL_21354: PANIC
PHKL_20335: CORRUPTION
PHKL_20222: MEMORY_LEAK
PHKL_20017: OTHER
Causing degradation in I/O performance of the
system.
PHKL_19314: HANG
PHKL_19201: HANG
PHKL_20836: PANIC
PHKL_20515: PANIC
Category Tags:
defect_repair hardware_enablement enhancement
general_release critical panic halts_system corruption
memory_leak
Path Name: /hp-ux_patches/s700_800/11.X/PHKL_27759
Symptoms:
PHKL_27759:
( SR:8606268349 CR:JAGae32588 )
When the tunable maxswapchunks is manually set to a value
higher than 16384, the system may panic with a stack trace
similar to:
mp_b_sema_sleep: blocking on owned semaphore
panic+0x14
_mp_b_sema_sleep+0x88
hash_insert+0x144
addtocache+0x50
swapchunk+0x1ec
devswap_pageout+0x1c0
stealpages+0x6c
vhand+0x2a8
main+0xa04
$vstart+0x48
$locore+0x94
PHKL_27364:
( SR:8606256133 CR:JAGae20448 )
In a multi-threaded process, if one thread is doing raw
or character device I/O, other threads in the process
may fail to make forward progress until the I/O completes.
PHKL_27238:
( SR:8606237263 CR:JAGae06308 )
Requests for an exclusive mapping of a file in the 3rd
quadrant fail for all executables with a private 3rd
quadrant. Such executables are usually obtained through
a chatr command with the parameter "+q3p enabled".
PHKL_27157:
( SR:8606244346 CR:JAGae10833 )
A 32 bit process with the 3rd quadrant private (obtained
with the command chattr +q3 enable) can obtain an incorrect
address when requesting a large (~1 GB) mapping with the
mmap(2) call.
Observed symptoms are :
-process aborted because of a memory fault
(signals SIGBUS or SIGSEGV).
-corruption of the memory for the calling process,
including files that are mapped in memory by the process.
System memory and memory from other processes are not
impacted.
PHKL_26800:
( SR:8606241742 CR:JAGae09000 )
Processes may hang uninterruptibly during filesystem access.
The type of filesystem is irrelevant - the hang may occur on
any block filesystem access. Once this process hang occurs,
no other processes will be able to access the file system.
PHKL_25906:
( SR:8606226665 CR:JAGad95728 )
On systems with large pages, the kernel can panic
during the remapping of buffers from kernel to user (or
vice versa). The panic stack trace may be similar to
one of the following :
panic+0x14
hdl_remap_bp+0x130
nfs_strat_map+0x84
nfs_strategy+0x3ac
nfs3_strategy+0x18
...
copyin+0xac
uiomove+0x3dc
rw3vp+0x29c
nfs3_write+0xf8
nfs3_rdwr+0xd8
vno_rw+0xb0
write+0x28c
syscall+0x550
syscallrtn+0x0
or possibly
panic+0x14
report_trap_or_int_and_panic+0x4c
trap+0xa08
call_trap+0x38
div2I+0x15c
hdl_remap_bp+0x29c
...
nfs_biodone+0x3c
async_daemon+0x38c
coerce_scall_args+0x9c
syscall+0x1c8
syscallrtn+0x0
PHKL_25525:
( SR:8606186963 CR:JAGad56173 )
On systems using NFS in loopback mode, there exists the
possibility of the system hanging due to a deadlock
between NFS daemons and inode locks held at the filesystem
(VxFS) level.
PHKL_25210:
( SR:8606216082 CR:JAGad85253 )
During normal operation, the system may experience a
"freevas: vas cnt 0, but still pointing to pregions"
panic. The panic stack trace may be similar to:
panic+0x14
freevas+0x140
freeproc+0x204
wait1+0x21c
waitpid+0x34
syscall+0x1c8
$syscallrtn+0x0
( SR:8606188767 CR:JAGad57983 )
When mmap is used with both the MAP_ANONYMOUS and MAP_GLOBAL
flags, addresses allocated are in the 3rd quadrant instead
of being in the 4th quadrant (shared quadrant) as requested
by the MAP_GLOBAL flag.
PHKL_25188:
( SR:8606194618 CR:JAGad63826 )
On K-Class and slower systems, Service Guard may TOC the
system when a process that uses more than a gigabyte of
memory exits. The stack trace of the TOC may look similar
to the following:
pdc_call+0x174
hversion_pdc_call+0xa4
diag2_ioctl+0x170c
spec_ioctl+0xac
vno_ioctl+0x90
ioctl+0x1e4
syscall+0x394
syscallinit+0x54c
or
pdc_call+0x198
pa_generic_psm_pdc_rtc+0x34
psi_rtc+0xb4
checkclock+0x24
invoke_callouts_for_self+0xc0
sw_service+0xb0
mp_ext_interrupt+0x150
ihandler+0x904
splnopreempt+0x8
idle+0x504
swidle+0x20
( SR:8606137149 CR:JAGad06267 )
The system panics with a data memory protection fault when
mmap(2) is used. The stack trace would look similar to the
following:
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0x4b8
nokgdb+0x8
b_sema_enqueue+0x38
<... various other entries ...>
hdl_changerange+0x238
hdl_mprotect+0x150
smmap_hole_anonymous+0x26c
smmap_common+0x3bc
smmap+0x1c0
syscall+0x9fc
$syscallrtn+0x0
PHKL_25164:
( SR:8606204721 CR:JAGad73900 )
A HPMC may occur on T600 (9000/893) systems when cache flush
code is executing. A stack trace may looks similar to the
following:
fdc_one_page_2_0+0x180
fdcache_conditionally+0x90
pdd_large_page2_0+0x1f0
pddpage+0x2d4
hdl_deletetrans+0xbc
do_deltransc+0x118
for_val2+0xb4
foreach_chunk+0x3c
hdl_detach+0x210
detachreg+0x80
kissofdeath+0x64
freethread+0x14c
thread_deallocate+0x94
thread_free+0x94
wait1+0x244
waitpid+0x38
syscall+0x200
syscallinit+0x54c
PHKL_24971:
( SR:8606195331 CR:JAGad64535 )
Doing memory management activities on a large memory segment
which was registered using asynchronous I/O driver, would
take higher number of CPU cycles.
PHKL_24826:
( SR: 8606185728 CR: JAGad54930 )
Narrow mode (32bit) HP-UX 11.00 programs cannot mmap64() any
part of a large file beyond the first 2GB.
PHKL_24612:
( SR: 8606198933 CR: JAGad68122 )
Random process core dumps.
PHKL_24457:
( SR: 8606180059, CR: JAGad49281 )
When using the asyncio driver, applications may exhibit slow
startup time.
( SR: 8606179580, CR: JAGad48804 )
A system panic occurs on process termination, if the process
had registered private memory segment with asyncio driver.
The stack trace will appear as follows:
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0xd9c
nokgdb+0x8
asyncdsk_close+0x94
call_open_close+0x1f8
closed+0xb0
spec_close+0x54
vn_close+0x48
vno_close+0x20
closef+0x64
exit+0x1108
psig+0x244
syscall+0x810
$syscallrtn+0x0
( SR: 8606195629, CR: JAGad64833 )
Slow application startup when using asyncio driver
( SR: 8606199485, CR: JAGad68671 )
On systems experiencing low memory conditions, applications
registering memory segments with asyncio driver may get
"Not owner" (EPERM) error.
PHKL_24273:
( SR:8606199847 CR:JAGad69033 )
A user creates a 64-bit program which mmaps a file
65536 times, then exists. It caused data page fault
in freereg() when referencing the region whose
r_refcnt overflowed since it's already freed and
its fields are not valid any more.
Stack trace looks like:
panic+0x14
report_trap_or_int_and_panic+0x84
trap+0xd9c
nokgdb+0x8
hdl_vfault+0x50
vfault+0xf8
trap+0x2a0
nokgdb+0x8
PHKL_24116:
( SR: 8606192498 DTS: JAGad61711 )
When the debugger is killed or sent a signal when trying to
attach to a process, that process will be left in a hung
state.
PHKL_24015:
( SR: 8606192072 DTS: JAGad61280 )
When using memory windows and shared memory (IPC_SHARE32)
between 32 and 64bit processes, the system may panic with
an "hdl_pfault: invalid DBD for intransit page" panic. The
stack trace may look like:
panic+0x14
hdl_pfault+0x638
pfault+0x104
trap+0x724
thandler+0xd20
PHKL_23857:
( SR: 8606178349 DTS: JAGad47576 )
Data corruption can occur when Hyperfabric networking
interface or async I/O driver is being used in the system.
PHKL_23813:
( SR: 8606188675 DTS: JAGad57891 )
When booting 11.00 on a PA-8700 system, the system panics
with the following message :
panic: set_machine_parameters_64: Unidentified cpu type
returned from PDC_MODEL
Panic stack trace:
PC-Offset Stack Trace (read down, top of stack is 1st):
panic+0x54
set_machine_parameters_64+0x1f8
rm_setmachineparams_64+0x40
DoCalllist+0x50
RDB_patch_int_trap+0xb0
End Of Stack
WARNING: Space ID hashing is disabled
PHKL_23812:
(SR: 8606183443 CR: JAGad52656)
A multi-threaded process hangs and cannot be killed. This
process will have been repeatedly mmap()ing parts of the
same file, while at the same time reading or writing to it
with the read(), write(), readv(), or writev() system calls
from a different thread. That file must also be on a JFS
file system.
The Netscape Messaging Server's smtpd process is the only
application we've seen do the particular combination of
operations required to get into this state.
PHKL_23628:
(SR: 8606146888 CR: JAGad16231)
If the process core file's size limit has been set to 0 in
setrlimit(), when the process aborts, the core processing
is incorrect.
PHKL_23406:
(SR: 8606103740 CR: JAGab70789)
(SR: 8606159451 CR: JAGad28779)
A multi-threaded process being executed over NFS can become
hung and unkillable while performing either a fork, core,
setrlimit, SIGSTOP, or debugger operations.
PHKL_23183:
(SR: 8606169539 CR: JAGad38814)
An application trying to do a PROBE instruction
results in non-access reference to an invalid
virtual memory address that causes the SIGSEGV
handler to be removed.
This makes an application program's own
error-recovery useless and results in database
crashes.
PHKL_22843:
(SR: 8606162188 CR: JAGad31504)
The output of "ps -f" shows the name of the script being
runs instead of the name of the '#!' interpreter.
(SR: 8606168950 CR: JAGad38228)
When the user exec a script w/o providing the arguments,
the kernel does not exec the shell as it should be
expected to do.
For example,
execve("./t.sh", 0) will not work.
t.sh:
~~~
#!/bin/ksh
echo t.sh script executed OK.
PHKL_22493:
(SR: 8606141875 CR: JAGad11229)
When not running as root, adb will panic the system when
an attempt is made to debug a kernel-threaded application
in which the first thread is in a ZOMBIE state.
panic: Data page fault
stack trace for event 0
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
handle_ooc_requests+0x2bc
perform_trace_request+0x260
ttrace1+0x13c
ptrace+0x78
syscall+0x480
$syscallrtn+0x0
PHKL_22032:
(SR: 8606146888 CR: JAGad16231)
Once-setuid/setgid processes could create corefiles or be
attached to with a debugger.
(SR: 8606146889 CR: JAGad16232)
IDDS generated incorrect records in certain cases
PHKL_21775:
Some processes (eg . created by Shared LVM) never get
reaped leading to proc table being filled and leading
to a system hang.
PHKL_21507:
( SR: 8606113684 CR: JAGac07198 )
system panics when doing crfree
panic: crfree: freeing free credential struct
Stack trace for crash event was :
q4> trace event 0
stack trace for event 0
crash event was a panic
panic+0x14
crfree+0xc4
kthread_shared_objects_update+0x30
syscall+0x594
$syscallrtn+0x0
PHKL_21358:
( SR: 8606132621 CR: JAGad01770 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_21350:
( SR: 8606132613 CR: JAGad01762 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_20439:
( SR: 8606109770 DTS: JAGaa45170 )
While running an MPI-based program, the system panics with a
"Data page fault" or other memory-related fault.
PHKL_20226:
( SR: 8606107525 DTS: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_21535:
( SR: 8606100830 CR: JAGab39185 )
Application core files do not include the process' attached
shared memory segments.
PHKL_21357:
( SR: 8606132620 CR: JAGad01769 )
The Praesidium IDS/9000 product requires this patch in order
to run. This patch has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_22744:
( SR: 8606161365 CR: JAGad30681 )
A system may experience a data page fault panic with the
following stack trace:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xdb8
nokgdb+0x8
thread_pcb_reinit+0x30
thread_alloc+0xe8
thread_create+0x2ac
_lwp_create+0xdc
syscall+0x480
$syscallrtn+0x0
PHKL_22549:
( SR: 8606128066 DTS: JAGab24436 )
Data page fault when trying to flush buffers
which have already been invalidated:
bwrite+0x44
bxwrite+0x44
syncip_flush_cache+01x1dc
vx_flushdev+0x14
vx_fsync+0x248
spec_fsync+0x254.
PHKL_22440:
( SR: 8606154274 CR: JAGad23592 )
When trying to attach to a process that has been swapped
out, both the tracing process and traced process hang and
remain in an unkillable state.
PHKL_22380:
(SR: 8606130240 DTS: JAGac95111)
Kernel paniced with data memory protection fault. This
could happen when using direct I/O on JFS version 3.3
or in other situations.
(SR:8606139945 DTS: JAGad09268)
MP System hang under heavy I/O load.
PHKL_22126:
( SR: 8606155209 DTS: JAGad24526 )
This patch is a replacement for the recalled patch
PHKL_21624 which addressed a system hang caused by memory
scrubber operating on shared memory segment used by the
async I/O driver. The following problems were introduced by
PHKL_21624 and are resolved by this patch.
1. System panic when both Hyperfabric networking interface
and async I/O driver are used on the same system with
PHKL_21624 installed.
2. Applications fail when trying to register shared
segments with async I/O driver. On failure errno is set to
EPERM.
( SR: 8606143996 DTS: JAGad13329 )
Excessive delay in database connect time for database user
processes.
PHKL_21781:
(SR: 8606137220 DTS: JAGad06338)
when a user application makes a large number (over 65535)
of mprotect(2) calls, it fails with ENOSPC - No space left
on device.
(SR: 8606136222 DTS: JAGad05348)
When sendfile_max is configured to be > 0, and when using
ftp or rcp to transfer data, we encounter a spinlock
deadlock panic in sendfile_hold().
A stack trace will look similar to:
panic
spin_deadlock_failure
deadlock_check
sl_pre_check
spinlock
sendfile_hold
sosendfile
sendfile
syscall
PHKL_21624:
(SR: 8606124290 DTS: JAGac39673)
Memory scrubber (memlogd) causes system hang while scrubbing
pages locked by async driver. The async driver is typically
used by database applications.
( SR: CR: JAGab16247 )
HP-UX does not support an interface that allows a driver to
lock user space memory on behalf of a user process in such
a way that prevents the user process from unlocking the
memory. Such a mechanism is required to enable DMA to user
space memory by the operating system (a driver).
PHKL_21600:
(SR: 8606134430 DTS: JAGad03565)
When using mmap with a negative offset or an offset greater
than 2^43, the system panics.
PHKL_20647:
(SR: 8606107024 DTS: JAGab76631)
System hang in b_sema_get_queue() when doing an munmap().
PHKL_20449:
(SR: 8606106816 DTS: JAGab76230)
Incorrect implementation of mmap(2) can cause system panics.
PHKL_20223:
( SR: 8606103245 DTS: JAGab69733)
The system will panic with the following message:
panic: Returning ID that is already free.
( SR: 8606107525 DTS: JAGab77768)
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_21532:
( SR: 8606131990 CR: JAGad01139 )
Approximately every 22 minutes, the system, or one cpu of a
multi-processor system, appears to hang for several minutes.
Then the problem goes away. This primarily affects larger
memory systems.
PHKL_21354:
( SR: 8606132598 CR: JAGad01747 )
After PHKL_21003 is installed on a V2500 or V2600 with at
least 24 CPUs and at least 24 GB of memory, the system fails
to boot. One symptom that has been observed is the
following message displayed during the boot process:
Error found :
- mem_toc zero error encountered.
( SR: 8606132617 CR: JAGad01766 )
The Praesidium IDS/9000 product requires this patch in order
to run. This change has no impact on systems without the
Praesidium IDS/9000 product installed and enabled.
PHKL_21024:
( SR: 8606112164 DTS: JAGab84450 )
Enhancement: Performance changes for corner case in RTSCHED
scheduling. This patch has no impact on most systems.
PHKL_21003:
( SR: 8606112473 CR: JAGab84822 )
V2500 with more than 24GB of memory and more than 24
processors takes a long time (>30min) to boot.
PHKL_20335:
( SR: 8606106466 DTS: JAGab75600)
Unlinked files within NFS filesystems sometimes leave behind
.nfsXXX files which are unremovable until after the system
is rebooted.
( SR: 8606107384 DTS: JAGab77587)
Panic or data corruption due to buffer cache buffers being
released multiple times.
( SR: 8606108724 DTS: JAGab78191)
Memory corruption after copying growing files over the
network multiple times.
PHKL_20222:
( SR: 8606107507 DTS: JAGab77743)
This patch adds support for the PA-8600 processor.
( SR: 8606107525 DTS: JAGab77768)
This patch is one of 8 patches necessary to add support for
the 3 Gb private address space feature.
PHKL_20102:
( SR: 8606106969 DTS: JAGaa45096 )
On systems with 5GB of memory or more, the system will
allocate memory for a static table that it does not use.
This affects 64-bit systems only.
PHKL_20017:
( SR: 8606104415 DTS: JAGab71916)
After installing PHKL_19314, I/O performance of the system
drops substantially.
( SR: 8606103778 CR: JAGab70853 )
64bit systems with large amount of memory (e.g. 32Gb) and
having large buffer cache (e.g. 8Gb) configured find the
syslog is flooded with the following error message:
vmunix : bufmap : rmap : ovflo, lost [xx..)(xx..]
PHKL_19314:
( SR: 4701426775 DTS: JAGab17440 )
On a system with a large number of processors (more than 14)
a hang can occur during boot and after displaying the
following messages:
Starting the STREAMS daemons-phase1
Checking root filesystem
log replay in progress
replay complete - marking super-block clean
Root check done
Create STCP device files
( SR: 8606101604 DTS: JAGab15954)
Attempting to resume from a breakpoint when running a
program under a debugger will cause the program to get a
segmentation violation. This has been seen on G-class
systems but it can occur on any system with block-tlb.
PHKL_19201:
SR: 8606100898 DTS: JAGab39707
A user sees a hang while using snapshot file systems.
Stack trace:
_swtch+0xd4
_sleep_one+0x538
vx_sleep_lock+0xd0
vx_snap_bpcopy+0xf4
vx_snap_copyblk+0x144
vx_snap_copy+0x50
vx_snap_strategy+0x280
vx_buf_strategy+0x24
bwrite+0xe0
getnewbuf+0x918
allocbuf1+0x234
brealloc1+0x5c
getblk1+0x2fc
vx_snap_getblk+0x2c
vx_snap_getblkbp+0x140
vx_snap_lookup+0x1c
vx_snap_bpcopy+0x110
vx_snap_copyblk+0x144
vx_snap_copy+0x50
vx_snap_strategy+0x280
vx_buf_strategy+0x24
bwrite+0xe0
getnewbuf+0x918
ogetblk+0x110
getblk1+0x290
vx_getblk+0x50
vx_bread+0x68
vx_iread+0x88
vx_real_iget+0x398
vx_iget+0x3c
vx_dirlook+0x23c
vx_lookup+0x120
locallookuppn+0xd4
lookuppn+0xf8
lookupname+0x40
vn_open+0x68
copen+0xd0
open+0x3c
syscall+0x480
$syscallrtn+0x0
PHKL_17038:
The system will trap 15 data page fault when tracing for
leaks without also tracing for corruption.
PHKL_20945:
( SR: 8606112164 DTS: JAGab84450 )
Enhancement: Performance changes for corner case in RTSCHED
scheduling. This patch has no impact on most systems.
PHKL_20995:
( SR: 8606127692 CR: JAGac78494 )
Programs using "memory windows" (started via setmemwindow)
will not be able to allocate more than 1 Gb of shared memory
(1 Gb total for all memory windows processes, i.e. this is
not a per process limit). This patch is a replacement for
PHKL_20227, which introduced the bug that this patch
fixes.
PHKL_20836:
( SR: 8606106781 CR: JAGab76169 )
Application issuing large amount of mmap calls to
map multiple virtual addresses to the same physical
page (using flags MAP_SHARED|MAP_FILE|MAP_FIXED)
may cause system panic with the follow stack trace:
panic: hdl_zero_page: page not mapped
panic+0x14
hdl_zero_page+0xc8
virtual_fault+0x418
vfault+0x118
trap+0x280
nokgdb+0x8
Trace on other processor shows:
panic+0x14
report_trap_or_int_and_panic+0x80
trap+0xde8
nokgdb+0x8
allocpfd_from_pond+0x134
allocate_page+0x68
lgpg_vfdfill+0x4c
virtual_fault+0xc3c
vfault+0x118
trap+0x280
nokgdb+0x8
PHKL_20227:
( SR: 8606107525 CR: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_20224:
( SR: 8606107525 CR: JAGab77768 )
This patch is one of 8 patches necessary to add support
for the 3 Gb private address space feature.
PHKL_20515:
(SR: 8606101315, CR: JAGab46368)
System hang while using async I/O module through database
applications with new large block I/O feature when system
is low on memory resources.
(SR: 8606100970, CR: JAGab39977)
Data pagefault during async I/O operations when an I/O is
being done to an unregistered (private) memory.
(SR:8606103126, CR: JAGab69473)
System hang can occur during async I/O operations when an
IO is being done to an unregistered (private) memory
segment designated by the user's IO buffer.
(SR: 8606102862, CR: JAGab68892)
Async driver can hang during async IO with requests larger
than MAXPHYS (allowing async I/O larger than MAXPHYS is a
new feature available in this patch, where MAXPHYS = 256KB).
(SR: 8606108814, CR: JAGab81517)
Async driver I/O completion notifications don't work when
used in conjunction with select(2) system call.
PHKL_20426:
When a multithreaded process does file I/O concurrently with
mmap() or munmap() on the same file, it can result in a
single process deadlock. This process is not killable.
Defect Description:
PHKL_27759:
( SR:8606268349 CR:JAGae32588 )
The internal swap table is sized on the value of the
maxswapchunks tunable. However, the maximum value of
the index used to access the swap table is 16384. If
SAM is used to build a kernel, the maximum value of
16384 for maxswapchunks is enforced, but if the system
file is edited and a new kernel built manually, there
were no checks on the size of maxswapchunks. If the
value was above 16384, the swap table would be sized
too large for the index and multiple virtual pages
could be allocated to the same swap block, resulting
in the panic.
Resolution:
We now check the value of maxswapchunks at boot time and
limit it to the maximum value of 16384.
PHKL_27364:
( SR:8606256133 CR:JAGae20448 )
The raw I/O routine was holding the process' virtual
address space (vas) lock for the duration of the I/O,
even though it was not needed for the normal case and
only rarely needed for an exception case. This effectively
blocked any other thread in the process which needed access
to the vas lock, such as for another I/O, thread creation,
mmap, thread exit, etc., for the duration of the I/O.
When the I/O was to a slow device, such as a tape drive,
this could be a considerable delay.
Resolution:
Eliminated use of the vas lock in the normal raw or
character device I/O path, retaining its usage only for
the rare exception case.
PHKL_27238:
( SR:8606237263 CR:JAGae06308 )
The parameter checking code in mmap incorrectly rejects
requests with the MAP_EXCLUSIVE flag, for the 3rd quadrant
regardless if this quadrant is private or not.
Resolution:
The mmap code has been modified to accept exclusive mappings
in the 3rd quadrant when it is private.
PHKL_27157:
( SR:8606244346 CR:JAGae10833 )
On 64 bit systems, calls to mmap(2) by 32 bit processes with
sizes in the range of 1 GB or greater cause the allocation
algorithm to allocate a segment in the 64 bit address space
instead of the 32 bit address space. The 64 bit address is
truncated to 32 bits on return to the 32 bit calling
process. The cause of this error is an incorrect boundaries
checking in the allocation algorithm. When using a
debugger, one can observe a 64 bit segment in the process
address space.
Resolution:
The allocation algorithm now checks boundary conditions
correctly, producing a correct memory address.
PHKL_26800:
( SR:8606241742 CR:JAGae09000 )
The problem is caused by a thread/process waiting on a
buffer that it incorrectly believes is still owned by
another process. The previous process failed to update the
internal data structure used to show that the buffer is no
longer in use. The new process sees this stale information,
goes to sleep believing that the buffer is still in use, and
never wakes up, which results in a filesystem hang. This
was seen with a process accessing a VxFS 3.3 filessytem with
Veritas NetBackup running. However, this defect is not
specific to any one filesystem; it applies to all block
filesystem access.
Resolution:
Changed the code to modify the internal data to indicate
the buffer is no longer in use before releasing the buffer
and doing the wakeup.
PHKL_25906:
( SR:8606226665 CR:JAGad95728 )
When the remapping of a large page based buffer occurs,
its boundaries are adjusted to match the large page.
The round up of the boundaries was incorrect causing the
kernel to fault during the remapping.
Resolution:
The adjustment of large pages aligned boundaries is
modified to ensure the correct remapping of large page
based buffers.
PHKL_25525:
( SR:8606186963 CR:JAGad56173 )
An NFS daemon (nfsd) grabs a directory inode lock and
then tries to acquire a free buffer from the buffer-cache.
For this new buffer, a reference release (vn_rele) must
first be performed for the old vnode associated with the
buffer. This vn_rele causes a .nfsXXX file removal to
occur. A second nfsd attempts to perform the file removal,
but in order to do so it must acquire the same directory
inode lock that the first nfsd is holding. This deadlock
ultimately effects other processes that start getting
blocked behind the directory inode until the system
gradually grinds to a halt.
Resolution:
The buffer-cache code will change to ensure that no invalid
NFS buffers remain in the cache with associated vnodes
thereby eliminating the potential of a locking deadlock
occurring.
PHKL_25210:
( SR:8606216082 CR:JAGad85253 )
The vas was corrupted due to unprotected modifications of
the vas reference count on a vfork.
Resolution:
Lock the vas during modification of the vas reference
count.
( SR:8606188767 CR:JAGad57983 )
The mmap system call does not take the MAP_GLOBAL flag into
account when used in combination with the MAP_ANONYMOUS
flag.
Resolution:
Check for the MAP_GLOBAL flag in mmap when the MAP_ANONYMOUS
flag is used, and allocate the address in the proper
quadrant (4th).
PHKL_25188:
( SR:8606194618 CR:JAGad63826 )
The problem is caused by an exiting process flooding the
bus with cache flush instructions. This in turn may cause
processes executing firmware code to wait until the
exiting process is finished before continuing. If the
Service Guard process is scheduled behind the process
executing the firmware code, the Service Guard process may
not have the chance to run for many seconds, causing it to
TOC the system when it does eventually run.
Resolution:
The exiting process now does its cache flushing less
aggressively and allows processes executing firmware code to
run at the same time. If such processes are allowed to run,
the Service Guard process scheduled after those processes
will be able to maintain contact with the other Service
Guard nodes in the cluster and it will not TOC the system.
( SR:8606137149 CR:JAGad06267 )
There is an invalid boundary check in the mmap(2) system
call that allows protections to be set outside a valid range
of pages. This causes a panic when subsequent mmap(2),
mprotect(2), or munmap(2) calls are made on the same range
of adresses.
Resolution:
The mmap(2) system call now correctly checks the boundaries
of the range of adresses before applying a mprotect
operation on them.
PHKL_25164:
( SR:8606204721 CR:JAGad73900 )
This defect is caused by JAVA chip arbitration bug. This
bug favors the sequential cache flush code over memory
access requests and outstanding I/O requests (from FWSCSI)
will time out and cause an HPMC.
Resolution:
The sequential cache flush code was modified to periodically
provide a time slot for the I/O requests to finish.
PHKL_24971:
( SR:8606195331 CR:JAGad64535 )
Upon removing the last process reference to a shared memory
segment on a memory unlock, the segment is demoted from
64MB pages to 4K pages. Any subsequent attempts to manage
this segment take considerable amount of time as the
number of page management structures has now been increased
by 16K times.
Resolution:
Do not demote the largepages on doing a memory unlock.
PHKL_24826:
( SR: 8606185728 CR: JAGad54930 )
The kernel code was limited by design to allow narrow
mode mmap64() to 2GB or less only.
Resolution:
The kernel was enhanced to remove this limitation. Narrow
mode mmap64() can now map up to 4GB.
PHKL_24612:
( SR: 8606198933 CR: JAGad68122 )
The VM subsystem was not correctly handling self-modifying
code pages that were not initially mapped with execute
access. There was a possibility that execute access could
be removed, leaving stale data in the instruction cache.
When the page was subsequently reused by another process,
it would fault on the stale instruction cache data.
Resolution:
If a page has execute access, retain the execute access
when adding a new translation. This ensures the data is
flushed from the instruction cache upon page deallocation.
PHKL_24457:
( SR: 8606180059, CR: JAGad49281 )
Before starting I/O's through the asyncio driver,
applications must register shared memory segments with the
driver. As part of the registration, the driver locks the
memory. If this operation needs to be done for a very
large memory segment, the locking may take a significant
amount of time, resulting in slow application startup.
Resolution:
The async driver now supports a new device file minor number
256. If an application uses the async device file with this
new minor number, the driver will defer locking the memory
until I/O's are issued. This avoids the overhead of memory
setup time and thus reduces the application startup time.
Note: This minor number should only be used on systems that
have enough physical memory so that paging is avoided.
Paging can cause serious performance degradation with this
new enhancement. On systems where paging is an issue, this
minor number should not be used.
( SR: 8606179580, CR: JAGad48804 )
When process that registered private memory with asyncio
driver terminates, the memory management subsystem cleans
the associated data structure. The asyncio driver tries to
dereference a pointer to one of these data structures that
has already been freed causing the system to panic.
Resolution:
The driver returns bad address (EFAULT) if any application
tries to register a private memory segment.
( SR: 8606195629, CR: JAGad64833 )
The asyncio driver checks for the user access rights
twice. This duplication of access rights check
contributes to slow application startup.
Resolution:
The redundant access rights check is removed.
( SR: 8606199485, CR: JAGad68671 )
The asyncio driver propagates the wrong error code to the
application when a memory locking function fails due to
low memory conditions.
Resolution
The appropriate error code is returned to the application.
PHKL_24273:
( SR:8606199847 CR:JAGad69033 )
The system panic's while trying to mmap() more than
the maximum allowed limit of pregions to a shared
region. (limited by r_refcnt, which is of type
ushort). This was caused by r_refcnt overflow which
caused it to reset. If a program mmap's more than
this limit, the counter r_refcnt overflow which
causes the system to panic.
Resolution:
The fix is to check for the overflow and return ENOMEM.
PHKL_24116:
( SR: 8606192498 DTS: JAGad61711 )
If the debugger is interrupted while trying to attach to a
single threaded process that is sleeping uninterruptibly,
it will return to the user without unsuspending the
debuggee so the debuggee's suspend count is not decremented
and the debuggee will be suspended forever.
Resolution:
ttrace_prepare_attach() now checks the return from the
sleep of the debugger. If the sleep returns an error, we
know that the debugger has been interrupted by someone
else other than the debuggee so we decrement the suspend
count of the debuggee.
PHKL_24015:
( SR: 8606192072 DTS: JAGad61280 )
A 64bit process cannot map into a private memory window -
it can only map into the global memory window of the
32bit virtual space. A 32bit process needing to share
with a 64bit process must either be mapped into the
global memory window or the object to be shared must
be marked IPC_GLOBAL. These rules were not being
enforced, resulting in incorrect space id assignment
for shared memory (IPC_SHARE32) allocated in a private
memory window.
Resolution:
Shared memory (IPC_SHARE32) allocated in a private memory
window is now remapped into the global memory window when
sharing with a 64bit process.
PHKL_23857:
( SR: 8606178349 DTS: JAGad47576 )
Kernel sub-systems such as Hyperfabric networking
interface and async I/O expect to be notified when a
translation for a page changes that they are using
for DMA. The virtual memory system uses the
cluster-interconnect flag to determine if such sub-systems
should be notified when the translation changes. If there
are two different kernel-locked ranges in the same
largepage, the unlocking of first locked range causes the
cluster-interconnect flag for that page to be cleared, even
though there is another locked range in the same page. This
could cause a DMA operation to occur on the wrong page,
resulting in data corruption, if sub-systems continued to
do DMA on that page.
Resolution:
A check is added to see if there are other kernel-locked
ranges in the same largepage before clearing the
cluster-interconnect flag.
PHKL_23813:
( SR: 8606188675 DTS: JAGad57891 )
11.00 does not recognize the PA-8700 processor.
Additionally, the PA-8700 processor is not IO-PDIR coherent.
Resolution:
This patch, PHKL_23813, is one of three 11.00 PA-8700
enablement patches. The other 11.00 PA-8700 enablement
patches are PHKL_23814 & PHKL_23815. To support 11.00 on
PA-8700, the following changes were made :
- Added code to recognize the PA-8700 processor.
- Added code to check if non-coherent IO-PDIR is set and
performed flushes and syncs whenever IO-PDIR is changed.
- Fixed inverted space hash mask to enable the PA-8700
processor.
PHKL_23812:
(SR: 8606183443 CR: JAGad52656)
This problem was caused by a lock ordering problem between
VM and JFS. JFS can call VM while holding an inode lock;
the routines called may require a vas lock. VM can call JFS
while holding a vas lock; the routines called may require an
inode lock. If we get unlucky, we hit the same vas/inode
lock combination from both directions, and the threads
deadlock. Because the vas lock potentially held by VM is a
per process resource, this situation can only be encountered
by a multithreaded process.
Resolution:
The fix is to have the VM routine drop the vas lock before
calling the file system code; fortunately, the VM routine
can safely drop and reacquire the lock around the call ...
it was mostly holding it to avoid dropping and reacquiring
it repeatedly in a loop.
PHKL_23628:
(SR: 8606146888 CR: JAGad16231)
If the process core file's size limit has been set to 0 in
setrlimit(), when the process aborts, the core processing
is incorrect.
Resolution:
If the process core file size limit has been set to zero,
don't create a core file.
PHKL_23406:
(SR: 8606103740 CR: JAGab70789)
(SR: 8606159451 CR: JAGad28779)
A thread acquires a lock and then sleeps interruptibly. The
interruptible sleep permits the thread to be stopped. Any
other thread attempting to acquire this lock will sleep
uninterruptably until the lock is available. This
uninterruptable thread is also unkillable. This introduces
a deadlock potential in multi-threaded processes: when a
thread holding the lock, a thread desiring the lock, and a
third thread doing one of fork, setrlimit, core, SIGSTOP, or
debugger optionations, all occur at the same time in the
same process, the deadlock is reached. The only way to
resolve the deadlock is to reboot the system.
This patch is part of a set of four patches (PHKL_23406,
PHKL_23407,PHKL_23408,PHKL_23409) that enable P_NOSTOP, a
new feature that prevents a process from being unkillable.
Each patch is independantly installable. Without all four
installed, P_NOSTOP will be unavailable.
In order to prevent the process executed over NFS from
becoming unkillable, NFS must use the P_NOSTOP feature. An
NFS patch using P_NOSTOP, PHNE_23249, will be released in
Spring of 2001.
Resolution:
If a thread acquires a lock and then sleeps interruptably,
it is not permitted to be stopped if P_NOSTOP is set. This
prevents this thread from becoming unkillable and prevents
the deadlock.
PHKL_23183:
(SR: 8606169539 CR: JAGad38814)
The check to unblock the signal handler was being done
too early inside grow(). This resulted in removal of the
signal handler specified by the application program.
Resolution:
The fix is to move the unblock signal out of grow() into
hdl_vfault() which then calls grow() at a later stage.
PHKL_22843:
(SR: 8606162188 CR: JAGad31504)
When an interpreter is invoked via a shell script, the
script name is mistakenly passed to the kernel as the first
argument (argv[0) instead of the interpreter name.
Resolution:
When an interpreter was being invoked via a shell script,
we passed the interpreter to the kernel as the first
argument instead of passing user's argv[0], which is
the script name.
(SR: 8606168950 CR: JAGad38228)
When user exec a shell script w/o supplying arguments
at all, the kernel failed to account for the extra
argument for the name of the script into the number
of arguments to be passed to the kernel. Also,
it failed to pass the interpreter to the kernel as
the first argument to be executed.
Resolution:
When user exec a shell script w/o supplying arguments
at all, the kernel bumps up argc by 1, to account for
the extra argument that we will be adding later via
via the function setup_shell_argv(). It also passes
the shell name to the kernel as the first argument,
instead of the script name.
PHKL_22493:
(SR: 8606141875 CR: JAGad11229)
When the debugged process initializes each thread's
data pointer, if the thread is in a ZOMBIE state,
that thead is not initialized, leaving the data
pointer NULL. Later, adb attempts to dereference
the NULL pointer, causing a data page fault panic.
Resolution:
Initialize the data pointer for all debugged threads,
including those in a ZOMBIE state.
PHKL_22032:
(SR: 8606146888 CR: JAGad16231)
If a setuid/setgid process completely dropped privileges,
it could create a core file on a subsequent error, and could
be attached to with a debugger.
(SR: 8606146889 CR: JAGad16232)
Some process management system calls generated incorrect
IDDS records.
Resolution:
(SR: 8606146888 CR: JAGad16231)
Remember that the process was once setuid/setgid, and
disallow corefiles and debugger attaches.
(SR: 8606146889 CR: JAGad16232)
Fix the generated records.
PHKL_21775:
Resolution :PM internal function prepare_to_reap_proc in
kern_exit.c changed to reap system processes correctly .
PHKL_21507:
( SR: 8606113684 CR: JAGac07198 )
Analysis of dump showed that we are attempting to free a
credential structure but credential refrence count
is already 0 indicating it was already freed.
Resolution:
Locking of credentials operations were protected by
sched_lock so that credential operations are done properly.
PHKL_21358:
( SR: 8606132621 CR: JAGad01770 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch enables the gathering of information from the
various uid and gid related system calls.
PHKL_21350:
( SR: 8606132613 CR: JAGad01762 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch enables the gathering of information from the
exec*() and exit() system calls.
PHKL_20439:
( SR: 8606109770 DTS: JAGaa45170 )
In the process to process memory copy routines, there were a
number of race conditions and memory leaks. These led to
system panics.
Resolution:
Made structural changes to locking logic to avoid these
race conditions and fixed the memory leaks.
PHKL_20226:
( SR: 8606107525 DTS: JAGab77768 )
This is one of 8 patches necessary to add support for the
3 Gb private address space feature. This feature allows a
process to have a private 3rd quadrant (normally the 3rd
quadrant, which is a 1 Gb range of address space from
0x80000000 to 0xC0000000, is used for shared objects). The
chatr command must be used to enable this feature for an
executable (chatr +q3p enable <a.out>). Note that this
feature is only enabled for 32 bit processes running on the
64 bit version of HP-UX.
The other 7 patches necessary to enable this feature are
PHKL_20222, PHKL_20223, PHKL_20224, PHKL_20225, PHKL_20227,
PHKL_20228 and PHKL_20229. Each patch may be installed
independently of the others - if enabling the 3 Gb private
address space feature is not desired. If fewer than all 8
patches are installed, the 3 Gb private address space
feature will not be enabled. The code in this patch that is
part of this feature will not have any impact on the system
until all 8 patches are installed.
Resolution:
A subset of the code to support the 3 Gb private address
space feature was added. When all 8 patches are installed
the following code changes to support this feature will
have been added:
1) Code to recognize the request for a private 3rd
quadrant (Q3) during exec() of an executable.
An executable that requests a private 3rd
quadrant will be referred to as a q3p process
below.
2) Code to prevent allocation of shared objects
in q3p processes.
3) Code to allow data to extend over the 2nd/3rd
quadrant boundary for q3p processes.
4) Code to put the stack for the primary thread
in the 3rd quadrant for q3p processes.
5) Code to map a shared library into the private
address space if there is no more room in the
4th shared quadrant for q3p processes.
PHKL_21535:
( SR: 8606100830 CR: JAGab39185 )
This patch corrects application core dump behavior by
allowing dumping of a process' attached shared memory
segments to the application core file. This patch has no
impact on the system unless shared memory dumping is
enabled. See the Special Installation Instructions section
for details on how to enable shared memory dumping after
installing this patch.
A word of caution:
After shared memory dumping is enabled, the new system-wide
core dump behavior for applications will be to include
attached shared memory segments to application core files.
This may not be the desired behavior if you have
applications that use large shared memory segments running
on the system. (eg database applications). If those
applications core dump, the core files will include their
attached shared memory segments. Thus, they can be very
large files. Do not enable shared memory dumping after
installing this patch if you do not want this behavior.
Resolution:
This patch enables shared memory dumping in the coredump
generation code when kernel global variables
core_addshmem_read and/or core_addshmem_write are set to 1.
If both of these variables are set to 0, their default
value, this patch has no impact on the system.
PHKL_21357:
( SR: 8606132620 CR: JAGad01769 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this patch has no impact on the system.
Resolution:
This patch enables the gathering of information from the
corefile generation code.
PHKL_22744:
( SR: 8606161365 CR: JAGad30681 )
A pregion lookup is done based on the thread id. Thread
id's are cached, so on systems with many threads configured
and running, the thread id may be stale, i.e. reused by
another thread. In this case, the wrong pregion is
returned.
Resolution:
Use the thread pregion pointer to access the pregion
instead of the thread id.
PHKL_22549:
( SR: 8606128066 DTS: JAGab24436 )
When syncing buffers for a particular device the routine
that scans the cache for dirty buffers was not checking
whether the buffers were valid. Those buffers that were
invalid would no longer have a vnode pointer associated
with them which in turn would cause a data page fault when
they were passed to bwrite().
Resolution:
The routine responsible for flushing buffers corresponding
to an individual inode will now ensure that only valid
buffers are attempted to be flushed.
PHKL_22440:
( SR: 8606154274 CR: JAGad23592 )
The kernel debug thread is responsible for receiving and
executing the debugger commands. This is a daemon thread
which is invisible to the user application and is not part
of the thread list of the proc stucuture. Hence while the
process is being swapped this thread is not put on the run
queue even if it were in run state. Since the debug thread
is not reactivated when the procces it is attached to is
swapped back in, both it and the attached process hang.
Resolution:
Explicitly start the debug thread (if it has been created)
when the process is swapped in.
PHKL_22380:
(SR: 8606130240 CR: JAGac95111)
The kernel driver creates an anonymous private mapping
with read-only protection and calls mprotect() to change
the access right to 'read-write'.
Before the dirver tries to write, it calls vaslockpages
to lock those pages down. vaslockpages did not set the
correct access right for the mprotected pages.
Resolution:
Changed kernel to set up the translation with corrent
access right.
(SR:8606139945 DTS: JAGad09268)
In the original design, when allocating/freeing a buffer,
it only does a sleep/wakeup on the list for the current
CPU. Processes sleeping from another CPU will not be
awakened. The result, seen in the dump of a hang, is
dozens of processes sleeping on an empty per-processor
queue.
Resolution:
The design has been changed as follows: When allocating
a buffer, first try to allocate from the cpu's own list,
if fail, allocate from global list, if still fail, steal
from each processor's list back to global list, then
try allocate from global list; if still fail, sleep on
global list. When freeing the buffer, if my cpu list's
number of free buffers is smaller than global list's,
free it to my list, else free it to global list, and
wakes up sleepers on the global list.
PHKL_22126:
( SR: 8606155209 DTS: JAGad24526 )
1. The problem was tied to the use of the global variables
used by legacy HyperFabric driver, the driver assumed that
they are kernel global function pointers owned by
HyperFabric and were initialized to NULL in the driver init
routine.
PHKL_21624 initializes (at compile time) the same function
pointers to the address of a new set of kernel funtions that
VM uses for calling all registered callback functions.
Resolution:
Replace the references to the global function pointers in VM
code with new symbol names, thus leaving the original
symbols initialized to NULL as the legacy HyperFabric driver
expects.
2. PHKL_21624 addressed a problem of system hang caused by
memory scrubber working on shared memory segments used by
the async I/O driver. To fix this problem, the change
required applications using async I/O driver to have MLOCK
privilege. This fact was not documented in PHKL_21624 and
caused application using async I/O driver to fail.
Resolution:
Applications that use the async I/O driver must belong to a
group having MLOCK privilege. Refer to the section
"Special Installation Instructions" for details on how to
check and set MLOCK privilege.
( SR: 8606143996 DTS: JAGad13329
During internal testing with PHKL_21624 using 8GB shared
memory segment and 300 user processes that were tyring
to connect to the database at the same time, we found that
the database user processes had an excessive database
connect delay. Each user process that connects to the
database registers memory with the async I/O driver which in
turn locks the memory so that if the address translation for
that memory is ever changed by VM, the async I/O driver
would be notified. To achieve this VM had to operate on each
4K page that backs-up the memory being locked. If there are
many users trying to register large memory segments almost
at the same time the registration process would take a long
time.
Resolution:
The VM code was modified to manage locking using superpages
rather than 4K pages.
PHKL_21781:
(SR: 8606137220 CR: JAGad06338)
The problem is due to the limitation of the protection
ranges for memory mapped regions. The counter for the
number of pregions that can be mprotected is defined as
a u_short. When an application uses a very large data
segment and makes more than 64K-1 mprotect(2) calls,
the system returns an ENOSPC.
Resolution:
Change the definition of mprotect range counters from
u_short to long.
(SR: 8606136222 CR: JAGad05348)
The major lock order for sendfile_lock was incorrect.
Resolution:
Correct the lock ordering for sendfile_lock.
PHKL_21624:
(SR: 8606124290 DTS: JAGac39673)
The following scenario would cause a deadlock (resulting in
a system hang): memlogd (using the dmem driver) was
scrubbing the 4kB physical pages of a superpage locked by
the async driver. Prior to scrubbing, dmem invalidated the
address translations for all the 4kB pages in the superpage.
Before dmem finished processing the superpage, it was
interrupted by an async I/O request. The I/O transaction
required accessing one of the 4kB pages in the superpage
being scrubbed by dmem. The interrupt handler would wait
for the page to be marked valid; dmem could not mark it
valid until the interrupt returned and it finished scrubbing
the superpage.
Resolution:
Callback registration support has been added to enable the
async driver to register a callback requirement against
memory it has locked. Whenever the address translation of a
locked page is to be invalidated, the callback feature is
invoked if the memory is registered as locked by async.
Thus, the async driver is able to prevent dmem from
scrubbing pages for which async I/Os are either active or
pending.
( SR: CR: JAGab16247 )
The mlock allows a user process to unlock memory locked by
the operating system. It does not allow for a persistant
lock of user space memory by the operating system.
Resolution:
A new interface was added to the VM subsystem to allow
persistant locking of user space memory by an operating
system driver in such a way that a user can not unlock it.
Both the persistant locking mechanism and the callback
registration support are required to support DMA to user
space by the operating system.
PHKL_21600:
(SR: 8606134430 DTS: JAGad03565)
No check for overflow when casting mmap offset from 64 bits
to 32 bits. And no check to prevent a negative value, from
user space.
Resolution:
After casting from 64 to 32 bits, the offset is tested
and if negative, mmap returns EINVAL.
PHKL_20647:
(SR: 8606107024 DTS: JAGab76631)
When calling munmap() to unmap an area that ends within a
superpage, the superpage lock was not properly released,
resulting in a system hang upon a subsequent attempt to lock
the superpage.
Resolution:
When calling munmap() to unmap an area that ends within a
superpage, demote the end points before attempting to lock
the superpage.
PHKL_20449:
(SR: 8606106816 DTS: JAGab76230)
The kernel behaves incorrectly during some mmap(2)
operations.
Resolution:
mmap(2) now returns an error if it can't honor the
request.
PHKL_20223:
( SR: 8606103245 DTS: JAGab69733)
This bug is caused by a race condition in the mmap(2) code
which was using a recursive algorithm to map all of the
file. A lock was being dropped and reacquired each time the
algorithm recursed.
Resolution:
The mmap bug was fixed by changing the algorithm so that is
no longer was recursive. This allowed the lock to be held
for the whole time.
( SR: 8606107525 DTS: JAGab77768)
This is one of 8 patches necessary to add support for the
3 Gb private address space feature. This feature allows a
process to have a private 3rd quadrant (normally the 3rd
quadrant, which is a 1 Gb range of address space from
0x80000000 to 0xC0000000, is used for shared objects). The
chatr command must be used to enable this feature for an
executable (chatr +q3p enable <a.out>). Note that this
feature is only enabled for 32 bit processes running on the
64 bit version of HP-UX.
The other 7 patches necessary to enable this feature are
PHKL_20222, PHKL_20224, PHKL_20225, PHKL_20226, PHKL_20227,
PHKL_20228 and PHKL_20229. Each patch may be installed
independently of the others - if enabling the 3 Gb private
address space feature is not desired. If fewer than all
8 patches are installed, the 3 Gb private address space
feature will not be enabled. The code in this patch that
is part of this feature will not have any impact on the
system until all 8 patches are installed.
Resolution:
A subset of the code to support the 3 Gb private address
space feature was added. When all 8 patches are installed
the following code changes to support this feature will
have been added:
1) Code to recognize the request for a private 3rd
quadrant (Q3) during exec() of an executable.
An executable that requests a private 3rd
quadrant will be referred to as a q3p process
below.
2) Code to prevent allocation of shared objects
in q3p processes.
3) Code to allow data to extend over the 2nd/3rd
quadrant boundary for q3p processes.
4) Code to put the stack for the primary thread
in the 3rd quadrant for q3p processes.
5) Code to map a shared library into the private
address space if there is no more room in the
4th shared quadrant for q3p processes.
PHKL_21532:
( SR: 8606131990 CR: JAGad01139 )
Approximately every 22 minutes, vhand monopolizes one cpu
for a long period of time. Every 22 minutes, vhand calls a
routine which tries to free up kernel memory. It tries to
free up each memory bucket for all cpus on the system each
time it is called.
As memory is freed up, chunks of memory are coalesced into
larger chunks of (contiguous) memory. Each 4k page freed is
added back into the superpage pool.
Another related problem is that the superpage pool chain
becomes long and fragmented (especially on large memory
systems), which implies inefficiency in managing the pool.
Resolution:
The routine called by vhand to free up kernel memory will
now work on one cpu at a time, and on only a few memory
buckets at a time. It will do less for each call, and be
called more often, spreading the workload out in time.
Use a better coalescing algorithm for the superpage pool
list.
PHKL_21354:
( SR: 8606132598 CR: JAGad01747 )
When mapping kernel pages to real memory, if the address
falls beyond 1GB and cannot be found in the 32bit sysmap, we
fail to check the return code and allocate it from the 64bit
sysmap.
Without PHKL_21003, which moved the 64bit sysmap to start at
1GB instead of 4GB to cover an undefined 3GB gap, this has
no effect since the address is not defined. However, when
the address is included in the 64bit sysmap and we do not
remove it properly when the virtual address is being used,
we end up using the same virtual address again because it is
still available in the sysmap. The init process fails when
the vhand daemon starts paging.
Resolution:
Allocate the address from the 64bit sysmap when it is not
found in the 32bit sysmap.
( SR: 8606132617 CR: JAGad01766 )
This patch is one of 16 patches (PHKL_21348-PHKL_21363)
required by the Praesidium IDS/9000 product. These patches
enable the collection and tracking of information from
various system calls. Unless all of the enabling patches
(or their successors) and the product are installed, and the
product is enabled, this change has no impact on the system.
Resolution:
This patch causes the IDS/9000 pseudo-driver to be
initialized at the right place during system boot.
PHKL_21024:
( SR: 8606112164 DTS: JAGab84450 )
This is an enhancement for a corner case in RTSCHED
scheduling.
Resolution:
Code added to fine tune RTSCHED thread scheduling code path.
PHKL_21003:
( SR: 8606112473 CR: JAGab84822 )
In 11.00, the 32bit sysmap contains pages from 0 to 1GB and
the 64bit sysmap contains pages from 4GB to 4TB, leaving a
3GB gap between them. Due to memory interleaving on V2500,
there may not be enough physical memory below 1GB to satisfy
the system initialization. Therefore, memory above 1GB is
used. During system boot, the init process will try to
allocate equivalently mapped virtual addresses from a sysmap
for physical pages between 1GB to 4GB. When it fails
because none of these pages can be found in either sysmap,
it loops through all pages sequentially until it exhausts
all the memory within the 1-4GB range. This may take a long
time depending on the number of physical pages in the range.
Resolution:
Extend 64bit sysmap to start from 1GB to cover the 3GB gap.
PHKL_20335:
( SR: 8606106466 DTS: JAGab75600)
The buffer cache was never releasing references it had on
NFS files which had the side-effect of never allowing these
files to be removed.
Resolution:
The buffer cache now ensures that it correctly releases all
holds on vnodes after data is removed from the cache. This
ensures that NFS files become inactive and are therefore are
removable.
( SR: 8606107384 DTS: JAGab77587)
The buffer cache has the potential to release buffers
multiple times, which could lead to system panics or memory
corruption.
Resolution:
The routine that was writing out dirty buffers then
releasing the buffer will now write and return thereby
ensuring that the buffer is released only once.
( SR: 8606108724 DTS: JAGab78191)
Files that grow in size and are copied over the network
multiple times -- via rcp or ftp commands -- during this
period may cause memory corruption to occur. This happens
because stale checksum data pointers within the buffer
header are reused after the buffer increases in size.
Resolution:
The buffer cache routine responsible for increasing the size
of buffers will now check whether a buffer contains a
pointer to checksum data -- which is used by the networking
code -- in which case it will free the data and clear the
pointer.
PHKL_20222:
( SR: 8606107507 DTS: JAGab77743)
This patch adds support for new machines that contain the
PA-8600 processor.
Resolution:
Code to support the PA-8600 processor was added.
( SR: 8606107525 DTS: JAGab77768)
This is one of 8 patches necessary to add support for the 3
Gb private address space feature. This feature allows a
process to have a private 3rd quadrant (normally the 3rd
quadrant, which is a 1 Gb range of address space from
0x80000000 to 0xC0000000, is used for shared objects). The
chatr command must be used to enable this feature for an
executable (chatr +q3p enable <a.out>). Note that this
feature is only enabled for 32 bit processes running on the
64 bit version of HP-UX.
The other 7 patches necessary to enable this feature are
PHKL_20223, PHKL_20224, PHKL_20225, PHKL_20226, PHKL_20227,
PHKL_20228 and PHKL_20229. Each patch may be installed
independently of the others - if enabling the 3 Gb private
address space feature is not desired. If fewer than all 8
patches are installed, the 3 Gb private address space
feature will not be enabled. The code in this patch that is
part of this feature will not have any impact on the system
until all 8 patches are installed.
Resolution:
A subset of the code to support the 3 Gb private address
space feature was added. When all 8 patches are installed
the following code changes to support this feature will have
been added:
1) Code to recognize the request for a private 3rd
quadrant (Q3) during exec() of an executable.
An executable that requests a private 3rd
quadrant will be referred to as a q3p process
below.
2) Code to prevent allocation of shared objects
in q3p processes.
3) Code to allow data to extend over the 2nd/3rd
quadrant boundary for q3p processes.
4) Code to put the stack for the primary thread
in the 3rd quadrant for q3p processes.
5) Code to map a shared library into the private
address space if there is no more room in the
4th shared quadrant for q3p processes.
PHKL_20102:
( SR: 8606106969 DTS: JAGaa45096 )
On systems with 5GB of memory or more, the system allocates
too much memory for the pdir hash table (32-224MB). This
additional memory is wasted.
Resolution:
Fixed boot time memory allocation algorithm to only allocate
memory that is actually used.
PHKL_20017:
( SR: 8606104415 DTS: JAGab71916)
The fix in PHKL_19314 for the "14-way boot hang" breaks the
interrupt distribution code. This results in all I/O
interrupts being assigned to the monarch CPU, causing I/O
performance degradation.
Resolution:
Add a new spu state SPU_INTR_ENABLED, so that pa_next_cpu
will designate a spu to be an interrupt handler if its
status is either SPU_INTR_ENABLED or SPU_ENABLED. Each
non-monarch CPU sets its state to be SPU_INTR_ENABLED at
the point where it used to set SPU_ENABLED.
( SR: 4701426775 DTS: JAGab17440 )
Historically on a 32bit system, the maximum size in one
quadrant is limited to 1Gb. To handle more than 1Gb of
buffer caches, we use two buffer cache resource maps, bufmap
and bufmap2. For 64bit systems, the maximum size of a
quadrant is not limited to 1Gb anymore and we don't need a
second bufmap to fulfill the buffer cache needs. Therefore,
bufmap2 is not used. However, on 11.00, we still initialize
two resource maps with the size of bufmap limited to 0.9Gb/2
entries regardless of whether we have a 32bit or a 64bit
system. So for 64bit systems with large memory and large
buffer cache defined the system can still run out of bufmap
entries if the virtual address space for the buffer cache
gets fragmented.
Resolution:
For 64bit systems, initialize bufmap to contain
phys_mem_pages/2 entries.
PHKL_19314:
( SR: 4701426775 DTS: JAGab17440 )
While the monarch processor is in MPCONFIG_PHASE2 during
boot and before it gets a chance to tell all non-monarch
processors to continue execution (set mp_sync_after_rendez
to CONTINUE_EXECUTION), a clock interrupt comes in. The
clock interrupt handler will erroneously attempt an
m_itmr_sync with all the processors (which are still waiting
to continue). This m_itmr_sync can take up to 13 msecs per
processor. When the number of processor is high enough,
which is 14 in this case, another clock interrupt arrives
before the current clock handler completes, causing the boot
to hang in an infinite continuous series of servicing clock
interrupts.
Resolution:
In the clock interrupt handling routine, we now make sure
that no m_itmr_sync is attempted by the monarch processor
until after the non-monarch processors are actually ready.
As for the non-monarch processors, in the non_monarch_init
routine, we now make sure that each non-monarch processor
does not signal the monarch processor that it is ready for
an m_itmr_sync until after the monarch sets
mp_sync_after_rendez to CONTINUE_EXECUTION.
( SR: 8606101604 DTS: JAGab15954)
The root cause seems to be a double mapping of the
break_page by both a block TLB entry and an ordinary one,
which causes undefined results in the hardware.
Resolution:
Code has been added to main so that during initialization it
looks at the machine being booted to see whether or not this
machine has a block-tlb. If the machine does not have one,
then the page in the kernel is used for the break-page. If
the machine has a block-tlb, then instead of using the page
in the kernel, a new page is allocated for the break-page.
PHKL_19201:
SR: 8606100898 DTS: JAGab39707
The system hang is caused by jfs snap code trying to lock
the same resource again when it already owns it. A buffer
that partially satisfies a request needs to be marked
invalid when it can't be grown to fit the request. This
will prevent another thread from getting a hit on it and
trying to grow it, which can cause a hang.
Resolution:
SR: 8606100898 DTS: JAGab39707
Mark buffers invalid when the buffer can't be grown to fit
the size of the request.
PHKL_17038:
An uninitialized variable may cause this data page fault
when tracing for memory leaks. The workaround is to also
trace for corruption which will initialize the variable.
The workaround isn't always feasible because tracing for
corruption uses a lot more memory in some environments while
tracing for leaks does not.
PHKL_20945:
( SR: 8606112164 DTS: JAGab84450 )
This is an enhancement for a corner case in RTSCHED
scheduling.
Resolution:
Code added to fine tune RTSCHED thread scheduling code path.
PHKL_20995:
( SR: 8606127692 CR: JAGac78494 )
Code that initialized the space maps for the second and
third quadrant for memory windows processes is not being
run. This means that a memory windows process cannot
allocate shared memory in the second (for SHMEM_MAGIC
processes) or third quadrant, leaving only the fourth
quadrant available, which is shared across all processes.
This defect is only present if all 8 of the Large Data
space patches are installed.
Resolution:
Code was changed to allow the space maps to be properly
initialized for all configured memory windows.
PHKL_20836:
( SR: 8606106781 CR: JAGab76169 )
HP-UX handles multiple virtual addresses mapping to the
same physical page by using virtual address aliasing.
Large number of overlapping exclusive mapping calls
(mmap with MAP_SHARED|MAP_FIXED|MAP_FILE) create excessive
number of virtual address aliases and can exhaust the alias
entries for physical pages. The exhaustion of alias entries
results in failed attempts to add a page translation.
Improper handling of the translation failure results in
corruption in the free memory list, thus causing an unmapped
page to be returned from the free memory pond.
Resolution:
Handle application requested overlapping exclusive mapping
without using aliases.
PHKL_20227:
( SR: 8606107525 CR: JAGab77768 )
This is one of 8 patches necessary to add support for the
3 Gb private address space feature. This feature allows a
process to have a private 3rd quadrant (normally the 3rd
quadrant, which is a 1 Gb range of address space from
&nbs