|
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
us-support.external.hp.com)Date: Sun Feb 18 2001 - 05:52:48 CST
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:
http://www.itresourcecenter.hp.com/
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:
http://www.itresourcecenter.hp.com/
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 10.X patch digest
Created: Sun Feb 18 3:05:03 PST 2001
Table of Contents:
Document ID Title
--------------- -----------
PHCO_22770 s700_800 10.01 cumulative cron/at/crontab patch
PHCO_22769 s700_800 10.10 cumulative cron/at/crontab patch
PHNE_22519 s700_800 10.20 2.40.00-2.40.02 ACC Base Software Patch
PHKL_23259 s800 10.20 SCSI cumulative patch
PHCO_23353 s700_800 10.24 (VVOS) ex(1),vi(1),expreserve(1) patch
PHNE_20748 s700_800 10.20 remote network commands cumulative patch
The documents are listed below.
-------------------------------------------------------------------------------
Document ID: PHCO_22770
Date Loaded: 20010216
Title: s700_800 10.01 cumulative cron/at/crontab patch
Patch Name: PHCO_22770
Patch Description: s700_800 10.01 cumulative cron/at/crontab patch
Creation Date: 01/02/10
Post Date: 01/02/16
Hardware Platforms - OS Releases:
s700: 10.01
s800: 10.01
Products: N/A
Filesets:
OS-Core.CMDS-MIN OS-Core.CMIN-ENG-A-MAN
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHCO_22770
Symptoms:
PHCO_22770:
1.crontab(1) incorrect functionality.
2.at(1) incorrect argument parsing.
3.Patches for cron(1M) should stop cron and start the
new cron.
PHCO_17550:
at(1) does not accept input of "00" or "0" for year for
all locales.
PHCO_16953:
1. On trusted systems, cron(1) has slower performance due
to calling getspwent() when getspwnam() should have
been used.
2. at(1) schedules jobs incorrectly relative to
28 February of non-leap years.
3. at(1) does not recognize year 00 (2000). When year
is input as 00, at(1) exits with the error message -
"bad date specification"
PHCO_15228:
Year displayed in two digits
PHCO_14058:
1. With libc patch installed, at dumps core.
2. at is not able to correctly schedule jobs for
Feb 29 2000
PHCO_10735:
Cron used to dump core and die when jobs submitted
with at -m were killed.
PHCO_10112:
The following symptoms correspond to the descriptions
in the defect descriptions field for PHCO_10112:
1. option -t now deal with year 2000 input correctly.
2. year limit has been increased from 2030 to 2037.
PHCO_7997:
1. at(1) cannot schedule job using weekdays in the last
week of the month.
2. cron does not mail stdout and stderr on trusted systems.
3. '.' not present in default PATH
PHCO_6862:
1. Cron dumps core intermittently.
2. Cron has a hard-coded limit of MAXRUN (40) child
processes which can be running simultaneously. Now
the limit has been increased to 100.
PHCO_6286:
Cron is going into a loop using all available cpu several
times a day. This happens intermittently when the system
is heavily loaded.
Defect Description:
PHCO_22770:
1. crontab(1) incorrect functionality.
Resolution:
Code is modified to take care of this issue.
2. at(1) incorrect argument parsing.
Resolution:
The code is modified to take care of this.
3. The cron(1M) patches do not stop the old cron daemon
and re-start the new cron daemon.
Resolution:
The cron(1M) patch scripts now stop the old cron daemon
and restart the new cron daemon after patch installation.
PHCO_17550:
at(1) treats year input of 00 or 0 as incorrect when
locale is set to one which defines D_T_FMT (date-time)
string to have year in fields other than the third.
For eg. japanese locale defines the date string to
be of format yy/mm/dd. With locale set to japanese,
an attempt to schedule a job using at(1) for a date
00/12/20 or 0/12/20 fails.
Resolution:
at(1) assumed that the year field can be only in the
third field of the date string. This assumption has been
removed. Also, the function which returned error if the
date string had 0 or 00 in the first or second fields
has been changed not to check and return error for such
a condition. Now, at(1) accepts input of 0 or 00 for year
in any field of the date string, as specified by D_T_FMT
string for the locale.
PHCO_16953:
1. On trusted systems, cron(1) called getspwent() which
performs a linear search in the passwd database, instead
of getspwnam() which performs a keyed search.
2. Jobs scheduled after 28 Feb are scheduled
erratically by at(1). The following shows the
incorrect behaviour of at(1).
# date 0227112099
Sat Feb 27 11:20:00 GMT 1999
# at now + 2 day
warning: commands will be executed using /usr/bin/sh
job 920287223.a at Mon Mar 1 11:20:23 1999
# at now + 3 day
warning: commands will be executed using /usr/bin/sh
job 920287243.a at Mon Mar 1 11:20:43 1999
In the above example, job is scheduled for March 1st
for both the inputs "now + 2 day" and "now + 3 day".
For the input "now + 3 day", at(1) should have
scheduled the job for March 2nd 1999.
The source code has been changed to fix the defect.
After the fix, at(1) correctly schedules jobs
relative to Feb, 28th. In the above example, for
input "now + 3 day", at(1) schedules the job for
March 2nd.
3. at(1) treats year input of 00 as incorrect. Following
shows how at(1) behaves with 00 as input year.
# at 12:00 1 Jan 00
bad date specification
The command has been changed to accept 00 as year
2000.
After the fix, at(1) treats year input of 00 as
year 2000 and does not show any error messages.
PHCO_15228:
Year displayed in two digits.
PHCO_14058:
The following defects are fixed in this patch:
1.With libc patch PHCO_12009 installed, at on 10.01 dumps
core.
2.When using at to schedule a job 29 Feb 2000, the job
actually gets scheduled for 1 Mar 2000.
PHCO_10735:
Cron used to dump core and die when jobs submitted
with at -m were killed.
PHCO_10112:
The following symptoms correspond to the descriptions
in the defect descriptions field for PHCO_10112:
1. option -t now deal with year 2000 input correctly.
2. year limit has been increased from 2030 to 2037.
PHCO_7997:
1. at(1) cannot schedule job using weekdays in the last
week of the month.
2. cron does not mail stdout and stderr on trusted
systems.
3. '.' not present in default PATH
PHCO_6862:
1. Cron dumps core intermittently.
2. Cron has a hard-coded limit of MAXRUN (40) child
processes which can be running simultaneously. Now
the limit has been increased to 100.
PHCO_6286:
Cron is going into a loop using all available cpu several
times a day. This happens intermittently when the system
is heavily loaded.
SR:
8606165710 8606158467 5003451278 4701416891 1653274167
1653269746 1653266239 1653241117 1653215038 4701347153
Patch Files:
/usr/lib/nls/msg/C/at.cat
/usr/lib/nls/msg/C/cron.cat
/usr/lib/nls/msg/C/crontab.cat
/usr/sbin/cron
/usr/bin/at
/usr/bin/crontab
/usr/share/man/man1.Z/at.1
/usr/share/man/man1.Z/batch.1
what(1) Output:
/usr/lib/nls/msg/C/at.cat:
None
/usr/lib/nls/msg/C/cron.cat:
None
/usr/lib/nls/msg/C/crontab.cat:
None
/usr/sbin/cron:
$Revision: 74.5.3.19 $
PATCH/10_01 PHCO_7997 $Revision: 74.2.1.8 $
PATCH_10_01: hpux_rel.o cron.o funcs.o 01/02/10
/usr/bin/at:
$Revision: 74.5.3.19 $
$Revision: 74.2.1.4 $
$Revision: 74.2.1.7 $
PATCH_10_01: hpux_rel.o at.o pdt.o ptime.o pdate.o f
uncs.o permit.o 01/02/10
/usr/bin/crontab:
$Revision: 74.5.3.19 $
PATCH_10_01: hpux_rel.o crontab.o permit.o funcs.o 0
1/02/10
/usr/share/man/man1.Z/at.1:
None
/usr/share/man/man1.Z/batch.1:
None
cksum(1) Output:
2031680443 3232 /usr/lib/nls/msg/C/at.cat
4002162402 2532 /usr/lib/nls/msg/C/cron.cat
4098515531 1035 /usr/lib/nls/msg/C/crontab.cat
3181343877 41102 /usr/sbin/cron
3448415927 45190 /usr/bin/at
2645454798 20560 /usr/bin/crontab
2773564955 8834 /usr/share/man/man1.Z/at.1
2773564955 8834 /usr/share/man/man1.Z/batch.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_6286 PHCO_6862 PHCO_7997 PHCO_10112 PHCO_10735 PHCO_14058
PHCO_15228 PHCO_16953 PHCO_17550
Equivalent Patches:
PHCO_22767:
s700: 11.00
s800: 11.00
PHCO_22768:
s700: 10.20
s800: 10.20
PHCO_22769:
s700: 10.10
s800: 10.10
Patch Package Size: 190 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_22770
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHCO_22770.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHCO_22770. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHCO_22770.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_22770.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
None.
-----End of Document ID: PHCO_22770------------------------------------------
Document ID: PHCO_22769
Date Loaded: 20010216
Title: s700_800 10.10 cumulative cron/at/crontab patch
Patch Name: PHCO_22769
Patch Description: s700_800 10.10 cumulative cron/at/crontab patch
Creation Date: 01/02/12
Post Date: 01/02/16
Hardware Platforms - OS Releases:
s700: 10.10
s800: 10.10
Products: N/A
Filesets:
OS-Core.CMDS-MIN OS-Core.CMIN-ENG-A-MAN
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHCO_22769
Symptoms:
PHCO_22769:
1.crontab(1) incorrect functionality.
2.at(1) incorrect argument parsing.
3.Patches for cron(1M) should stop cron and
start the new cron.
PHCO_19637:
1. at now + [n] months ignores leap year.
2. crontab(1) -e creates crontab job files
with incorrect permissions.
3. at(1) manpage needs to be modified.
PHCO_18060:
The cron(1M) and at(1) binaries in the previous patch
PHCO_17551 fail to execute in trusted mode. These
binaries have been linked with the archive version of
libsec instead of the shared version of the library.
PHCO_17551:
at(1) does not accept input of "00" or "0" for year for
all locales.
PHCO_16863:
1. On trusted systems, cron(1) has slower performance due
to calling getspwent() when getspwnam() should have
been used.
2. Cron from patch PHCO_15429 does not run at(1) and
batch(1) jobs.
3. at(1) schedules jobs incorrectly relative to
28 February of non-leap years.
4. at(1) does not recognize year 00 (2000). When year
is input as 00, at(1) exits with the error message -
"bad date specification"
PHCO_15429:
On trusted systems, /etc/passwd is inherited as stdin
by processes spawned by cron.
PHCO_15229:
Year displayed in two digits.
PHCO_14474:
1. at non able to schedule job for Feb 29 2000 correctly.
2. at creates an invalid file in /var/spool/cron when
given a non-existant job file with the -f option.'
PHCO_10736:
Cron used to dump core and die when jobs submitted
with at -m were killed.
PHCO_10120:
The following symptoms correspond to the descriptions
in the defect descriptions field for PHCO_10123:
1. option -t now deal with year 2000 input correctly.
2. year limit has been increased from 2030 to 2037.
PHCO_8276:
1. at(1) records incorrect audit id on trusted systems
PHCO_7996:
1. Cron does not mail stdout and stderr to user on a
trusted system.
2. '.' not present in the default PATH
PHCO_7835:
at(1) cannot schedule job using weekdays in the last
week of the month.
PHCO_7031:
1. Cron dumps core intermittently.
2. Cron has a hard-coded limit of MAXRUN (40) child
processes which can be running simultaneously. Now
the limit has been increased to 100.
Defect Description:
PHCO_22769:
1. crontab(1) incorrect functionality.
Resolution:
Code is modified to take care of this issue.
2. at(1) incorrect argument parsing.
Resolution:
The code is modified to take care of this.
3.The cron(1M) patches do not stop the old cron daemon
and re-start the new cron daemon.
Resolution:
The cron(1M) patch scripts now stop the old cron daemon
and restart the new cron daemon after patch installation.
PHCO_19637:
1. Setting the system date such that the day is any day
after 28th and executing the at(1) command to schedule
the job for the month of February in a leap year,
schedules the jobs incorrectly. The following
shows the incorrect behaviour of at(1).
# date 1229084495
date: do you really want to run time backwards?[yes/no]yes
Fri Dec 29 08:44:00 EST 1995
# at now + 2 month
warning: commands will be executed using /usr/bin/sh
job 825687848.a at Fri Mar 1 08:44:08 1996
at(1) should have scheduled the job for Feb 29.
Instead it is scheduling the job for Mar 1.
2. crontab when used with -e creates the job files
with read permission for all.
3. The manpage of at(1) needs to be more clear
regarding the ambiguity of dates.
Resolution:
1. Checking for the leap year before scheduling the
job, solves the problem.
2. The crontab command was relying on a macro for
permissions on the job file. This macro was incorrect.
This has been set right now. Now, crontab(1) creates
job files with read permission only for the owner.
3. Necessary changes are made to the at(1) manpage to
solve this problem.
PHCO_18060:
cron(1M) and at(1) binaries in the previous patch
PHCO_17551 do not work in trusted mode. These binaries
are expected to be linked with the shared version of
library libsec, but have been incorrectly linked with
the archive version of the library.
Resolution:
The binaries have now been correctly linked with the
shared libsec library and successfully execute in
trusted mode.
PHCO_17551:
at(1) treats year input of 00 or 0 as incorrect when
locale is set to one which defines D_T_FMT (date-time)
string to have year in fields other than the third.
For eg. japanese locale defines the date string to
be of format yy/mm/dd. With locale set to japanese,
an attempt to schedule a job using at(1) for a date
00/12/20 or 0/12/20 fails.
Resolution:
at(1) assumed that the year field can be only in the
third field of the date string. This assumption has been
removed. Also, the function which returned error if the
date string had 0 or 00 in the first or second fields
has been changed not to check and return error for such
a condition. Now, at(1) accepts input of 0 or 00 for year
in any field of the date string, as specified by D_T_FMT
string for the locale.
PHCO_16863:
1. On trusted systems, cron(1) called getspwent() which
performs a linear search in the passwd database, instead
of getspwnam() which performs a keyed search.
2. After installing PHCO_15429, jobs submitted from
at(1) are never actually run, although they are
removed from the /var/spool/cron/atjobs queue.
3. Jobs scheduled after 28 Feb are scheduled
erratically by at(1). The following shows the
incorrect behaviour of at(1).
# date 0227112099
Sat Feb 27 11:20:00 GMT 1999
# at now + 2 day
warning: commands will be executed using /usr/bin/sh
job 920287223.a at Mon Mar 1 11:20:23 1999
# at now + 3 day
warning: commands will be executed using /usr/bin/sh
job 920287243.a at Mon Mar 1 11:20:43 1999
In the above example, job is scheduled for March 1st
for both the inputs "now + 2 day" and "now + 3 day".
For the input "now + 3 day", at(1) should have
scheduled the job for March 2nd 1999.
The source code has been changed to fix the defect.
After the fix, at(1) correctly schedules jobs
relative to Feb, 28th. In the above example, for
input "now + 3 day", at(1) schedules the job for
March 2nd.
4. at(1) treats year input of 00 as incorrect. Following
shows how at(1) behaves with 00 as input year.
# at 12:00 1 Jan 00
bad date specification
The command has been changed to accept 00 as year
2000.
After the fix, at(1) treats year input of 00 as
year 2000 and does not show any error messages.
PHCO_15429:
On trusted systems, crontab jobs spawned by cron
gets /etc/passwd file on their stdin.
PHCO_15229:
Year displayed in two digits.
PHCO_14474:
1. Job submitted for Feb 29, 2000 was actually scheduled
for Mar 1, 2000.
2. At fails to clean up the file created under
/var/spool/cron when invoked with -f option and
non-existant job file.
PHCO_10736:
Cron used to dump core and die when jobs submitted
with at -m were killed.
PHCO_10120:
1. option -t now deal with year 2000 input correctly.
2. year limit has been increased from 2030 to 2037.
PHCO_8276:
1. At records incorrect audit id on a trusted system
PHCO_7996:
1. Cron does not mail stdout and stderr to user on a
trusted system.
2. '.' not present in the default PATH
PHCO_7835:
at(1) cannot schedule job using weekdays in the last
week of the month.
PHCO_7031:
1. Cron dumps core intermittently.
2. Cron has a hard-coded limit of MAXRUN (40) child
processes which can be running simultaneously. Now
the limit has been increased to 100.
SR:
8606165710 8606158467 5003451278 1653312975 5003459313
1653293407 5003456673 4701416891 1653274167 5003425777
5003426254 1653269746 1653266239 1653241117 4701347153
4701334763 4701303453 5003239277 1653160630 5003298612
5003325241 4701328179 5003417006
Patch Files:
/usr/lib/nls/msg/C/at.cat
/usr/lib/nls/msg/C/cron.cat
/usr/lib/nls/msg/C/crontab.cat
/usr/sbin/cron
/usr/bin/at
/usr/bin/crontab
/usr/share/man/man1.Z/at.1
/usr/share/man/man1.Z/batch.1
what(1) Output:
/usr/lib/nls/msg/C/at.cat:
None
/usr/lib/nls/msg/C/cron.cat:
None
/usr/lib/nls/msg/C/crontab.cat:
None
/usr/sbin/cron:
PATCH/10_10 PHCO_8276 $Revision: 76.2.1.28 $
PATCH_10_10: hpux_rel.o cron.o funcs.o 01/02/12
/usr/bin/at:
PATCH/10_10 PHCO_8276 $Revision: 76.2.1.28 $
$Revision: 76.2.1.6.1.2 $
$Revision: 76.2.1.6 $
PATCH_10_10: hpux_rel.o at.o pdt.o ptime.o pdate.o f
uncs.o permit.o 01/02/12
/usr/bin/crontab:
PATCH/10_10 PHCO_8276 $Revision: 76.2.1.28 $
PATCH_10_10: hpux_rel.o crontab.o permit.o funcs.o 0
1/02/12
/usr/share/man/man1.Z/at.1:
None
/usr/share/man/man1.Z/batch.1:
None
cksum(1) Output:
2031680443 3232 /usr/lib/nls/msg/C/at.cat
4002162402 2532 /usr/lib/nls/msg/C/cron.cat
4098515531 1035 /usr/lib/nls/msg/C/crontab.cat
3135308544 40960 /usr/sbin/cron
852579591 45056 /usr/bin/at
2723636416 24576 /usr/bin/crontab
3331946115 9011 /usr/share/man/man1.Z/at.1
3331946115 9011 /usr/share/man/man1.Z/batch.1
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_7031 PHCO_7835 PHCO_7996 PHCO_8276 PHCO_10120 PHCO_10736
PHCO_14474 PHCO_15229 PHCO_15429 PHCO_16863 PHCO_17551 PHCO_18060
PHCO_19637
Equivalent Patches:
PHCO_22767:
s700: 11.00
s800: 11.00
PHCO_22768:
s700: 10.20
s800: 10.20
PHCO_22770:
s700: 10.01
s800: 10.01
Patch Package Size: 190 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_22769
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHCO_22769.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHCO_22769. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHCO_22769.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_22769.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_22769------------------------------------------
Document ID: PHNE_22519
Date Loaded: 20010215
Title: s700_800 10.20 2.40.00-2.40.02 ACC Base Software Patch
Patch Name: PHNE_22519
Patch Description: s700_800 10.20 2.40.00-2.40.02 ACC Base Software Patch
Creation Date: 01/01/10
Post Date: 01/02/15
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products:
Z7299A_APZ B.02.40.00; Z7299A_APZ B.02.40.01;
Z7299A_APZ B.02.40.02; Z7301A_APZ B.02.40.00;
Z7301A_APZ B.02.40.01; Z7301A_APZ B.02.40.02;
Z7401A_APZ B.02.40.00; Z7401A_APZ B.02.40.01;
Z7401A_APZ B.02.40.02; Z7404AA_APZ B.02.40.00;
Z7404AA_APZ B.02.40.01; Z7404AA_APZ B.02.40.02;
Z7422AA_APZ B.02.40.00; Z7422AA_APZ B.02.40.01;
Z7422AA_APZ B.02.40.02;
Filesets:
ACC.ACC-KRN,B.02.40.00,B.02.40.01,B.02.40.02
ACC.ACC-RUN,B.02.40.00,B.02.40.01,B.02.40.02
ACC.ACC-PRG,B.02.40.00,B.02.40.01,B.02.40.02
ACC.ACC-FW,B.02.40.00,B.02.40.01,B.02.40.02
ACC.ACC-MAN,B.02.40.00,B.02.40.01,B.02.40.02
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHNE_22519: PANIC
PHNE_18716: PANIC
PHNE_17877: OTHER
Bad FixMajor script. Reboot error.
PHNE_16615: OTHER
DMA timeout.
PHNE_15350: PANIC
Path Name: /hp-ux_patches/s700_800/10.X/PHNE_22519
Symptoms:
PHNE_22519:
SR None / CR JAGab66302:
Enhance zmasterd to accept .answ file on cold start.
SR 8606112534 / CR JAGab84883:
If the timezone is MET-1METDST and START_ZCOM is set to
1 in /etc/rc.config.d/acc, ACC software is started
automatically upon system startup. This results in a
boot startup record being generated in
/var/opt/acc/log/thu.tlog regardless of the actual day
causing loss of data in /var/opt/acc/log/thu.tlog.
SR 8606112735 / CR JAGab87447:
x25init hangs when trying to bring up a link on z7330a
and z7300a cards during attempts to enable them. The
following trace segments from /var/adm/netll.LOG00 are
generated when the problem occurs:
Network NS_LS_AXIN Warning 3004, pid [ICS]
AXIN: Unrecognizable unsolicited event
arrived. Event ignored.
L2 ZLU = 1, L3 ZLU = 2, Msg type = 6,
Req Code = 9, Status = 5.
Network NS_LS_AXIN Warning 3004, pid [ICS]
AXIN: Unrecognizable unsolicited event
arrived. Event ignored.
L2 ZLU = 1, L3 ZLU = 3, Msg type = 6,
Req Code = 9, Status = 5.
(i.e. TM_NOPORT=5 )
They indicate that the firmware is not responding to
"enable" and "activate" parameters.
SR 8606125003 / CR JAGac40395:
This defect affects only 4-port E1/T1 ACC. When using
packet sizes lesser than 256, an incoming level 2 frame
of 263 octets is accepted by the level 2 protocol,
instead of being rejected with a "Frame Reject".
SR 8606128460 / CR JAGac84425:
The ACC firmware will generate a fatal error if a zero
length message is sent to some protocols (e.g.
HDLC.FRAME).
SR 8606128633 / CR JAGac86180:
In the zmntr TT and PT displays, the X.25 link terminal
error counter is always zero on the 4-port E1/T1 ACC
cards.
SR 8606131450 / CR JAGad00600:
"zmasterd deact znode" does not kill the znode daemon.
SR 8606133312 / CR JAGad02457:
Interface tunable "tsize" should be a multiple of 8,
minimum 8.
SR 8606133865 / CR JAGad03005:
With "idle pattern" processing enabled (i.e,
transmission of correct idle patterns on unused
channels), a loopback cable between two ports can be
disconnected and reconnected. After reconnection the
link should come up. However the link does not come
up.
SR 8606144270 / CR JAGad13610:
zqmve() gives error when moving messages between
program ZLUs.
SR 8606147407 / CR JAGad16750:
The zconfig.3x man-page was not delivered with the
patches PHNE_18716. Because of this, the old
zconfig.3x man-page did not have enough information to
support the ZcDSC_SET_TIMESLOTS(11) and
ZcDSC_SET_SUBC_SPECS (12) actions for zconfig. In the
new zconfig.3x information has been provided about how
to use zconfig for ZcDSC_SET_TIMESLOTS(11 and
ZcDSC_SET_SUBC_SPECS (12) actions.
SR 8606152257 / CR JAGad21596:
ZTERM wrongly reports request code 11
(ZCOM_MRQCODE_DEL) as "port configuration" for zport
return status (by x25stat API). The correct request
code should be 14 (ZCOM_MRQCODE_PORT).
SR 8606161688 / CR JAGad31008:
MPU activity field in the zmntr mx command shows
incorrect value.
SR 8606170918 / CR JAGad40182:
System panic due to Data Page Fault.
SR 8606171991 / CR JAGad41254:
System panic due to spinlock deadlock.
PHNE_18716:
DTS TPO0h02823
The fault handling routines in the firmware do not
decode the fault record that the CPU writes to the
stack.
DTS TPO0h02806
The zmasterd man page does not describe the "kill" option.
DTS TPO0h02738
This bug causes a "firmware error 5" type card crash
for the Z7330A and a "DMA timeout" for the Z7300A card.
It occurs at random and is statistically more likely
to occur, the greater the message rate. A high rate of
short messages on relatively few channels is more
likely to cause the problem than long messages on
many channels.
DTS TPO0h02674
SAM does not display a description of the ACC kernel tunable
parameters or subsystems.
DTS TPO0h02813
Confusing message logged by ttgen for an invalid port mode
DTS TPO0h02786
This defect is a follow up to defect TPO0h02762.
That defect addressed problems experienced when the
4-channel E1/T1 cards were loaded up in such a way that
the Munich chip receive descriptors would overrun.
This could be made to happen more readily by using a very
small buffer size (32 bytes) with large frames.
The symptom was usually that the receive channel would hang
so no more frames could be received, until the subchannel
was re-enabled.
The changes made for TPO0h02762 fixed these problems
except in a rare case, when it is still possible
for the receive channel to hang.
DTS TPO0h02765
netfmt fails after the r2.40.01 ISDN/ACC product is
installed
DTS TPO0h02783
TTGEN does not allow an E1/T1 port to be configured in
"Loopback" mode unless the Frame mode is set to TRANS.
DTS TPO0h02610
Add Q4 support for the 10.X release.
DTS TPO0h01522
The x.25 firmware was failing to transmit a level 3 RR
on a PVC when activated. Deactivating a PVC did result
in a level 3 RNR being sent.
DTS TPO0h01780
The LAPB and LAPD protocols were not behaving correctly
in relation to retransmission of the REJect frame. Only
one REJect frame would be transmitted, despite never
receiving an in-sequence I-frame which clears the reject
condition. The standards state that that a REJect frame
should be retransmitted every T1 interval until the
condition clears.
DTS TPO0h02173
On LAPB/LAPD connection establishment, groups of DM
frames are sentbetween groups of SABM/SABME frames -
which is incorrect. DM frames should not be sent during
this connection establishment state.
DTS TPO0h02175
LAPB/LAPD terminals are not handling the "busy condition"
properly. If one side of a link is inactive (sent RNR -
Receiver Not Ready), the other side should poll every T1
until the remote end activates.
DTS TPO0h02242
DMA timeout errors occur in running ISDN/X.25.
DTS TPO0h02245
The pmon utility does not clean up its dynamically created
terminals on exiting.
DTS TPO0h02255
The ACC X.25 firmware occasionally fails in creating a large
number of X.25 virtual circuits in a short period of time.
This problem was discovered in executing a stress test that
attempts to establish 1024 VCs. The driver sometimes
detected that write completion messages arrived out
of sequence.
DTS TPO0h02273
An x.25 PVC cannot be enabled after being
explicitly disabled.This problem only occurs on the
4 port cards (I960 based)
DTS TPO0h02438
When an exception occurs on an ACC card, a card reset
is sometimes required before a firmware dump is taken.
It has been found that some valuable data in the dump
file gets corrupted, making the analysis of the
firmware dump file much harder.
DTS TPO0h02620
The axin driver sometimes detects error -43
(timeout of level 2 disable request) in the nettl log,
while attempting to shutdown an X.25 link.
DTS TPO0h02775
The lbtest() library function, which is called by
ZMNTR to perform the port loopback test on E1/T1
ports, can cause a core dump.
DTS TPO0h02774
When an E1/T1 port is re-configured, while other
ports are in use, it is possible for a "Backplane
DMA timeout" to occur.
DTS TPO0h02762
With small buffers configured and large frames, it is
possible to overrun the available receive and transmit
descriptors used by the Munich chips. For example, with a
buffer size of 32 bytes, a received frame larger than 588
bytes, or a transmitted frame larger than 1584 bytes cannot
be handled. The level-1 protocol does not handle these
cases cleanly, and can stop receiving or transmitting frames
correctly.
DTS TPO0h02331
When using zconfig() to dynamically configure ports on
E1/T1 ACC cards, there is no check for invalid
timeslot and subchannel configurations.
DTS TPO0h02681
The 60008 version of the 4-ch PCI card cannot synchronise
correctly in E1 mode. The PMON output indicates occasional
"Slip" errors which correspond to data errors on the line.
DTS TPO0h01918
The selftest on the Z7300A 4 port ACC cards can
very occsasionally not complete, leading to a
timeout.
DTS TPO0h02063
The port configuration done via zconfig() should be able
to configure a timeslots or subchannels without affecting
the operation of the rest of the port.
This feature was never completed in the original
implementation.
DTS TPO0h02239
The 4 port ACC is not able to detect an error condition when
the ACC transmit side has been disconnted, but the recive
side remains intact. It does not act on a received RAI
signal.
DTS TPO0h02423
TTGEN does not report an error when inappropriate
framing or encoding options are used for an E1 or
T1 port configuration.
DTS TPO0h02446
TTGEN fails to catch re-defined subchannels.
For example :
subchannel 3 mapped to timeslot 3
subchannel 4 mapped to timeslot 4
subchannel 3 mapped to timeslots 8-31
DTS TPO0h02477
Subchannel quota tables can be corrupted leading
to an incorrectly reported "buffer shortage".
DTS TPO0h02676
The transmitted T1 signal waveform for the
T1 RJ45 100ohm mode is not within the T1
specification.
DTS TPO0h02414
A customer would like to be able to congigure the
frame protocol buffer transmit timer in the same
way timers are configured in HDLC-LAPB.
A problem exists at baud rates of 1200 and below.
A full buffer of data (238 bytes) will be cut
short when the 1 second transmit timeout expires.
DTS TPO0h02504
With the baud rate incorrectly configured as 64,000
while the actual line speed is 9600, transmitted
frames can be cut short and joined together.
DTS TPO0h02723
It is possible for an E1/T1 line to go down within
one second of a received RAI or loss of frame sync.
The FALC protocol module is supposed to ensure that
the line is DOWN for 3 to 4 seconds before the other
layers are informed.
DTS TPO0h02246
DTS TPO0h02246With the PMON utility in use, the ZMNTR
loopback test cannot be run on any E1/T1 port.
SR 4701323840 / DTS TPO0h00545
The customer has noted a problem when having large network
events causing the zcom log file to grow very quickly and
filling up the file system. This causes problems for the
rest of the application and the customer would like a
solution that would prevent the zcom log from taking out
the file system.
SR None / DTS TPO0h01209:
port mode validation is incorrect in ttgen
SR 5003380527 / DT TPO0h01523:
When the operating system is configured incorrectly, there
is not enough msg buffers (reported by HP-UX with dmesg
error: Can't allocate message buffer.). When this happens
zmasterd cold & kill does not behave properly because it
can't get msg buffer in msgsnd().
SR None / DTS TPO0h01629:
Traces won't work if the core dump is not in the default
directory.
(/var/adm/crash)
DTS: TPO0h02037 SR: 5003415463
Utility zmlog reads zcom log buffer from the LDM.
But occasionally the read return length is not
consistent with the "log buffer length" kept in
the returned log buffer. This usually happens when
there is a lot of messages being logged in a short
time, e.g. during system startup with a large number
of X.25 circuit. But it did happen in a small
configuration. When this happens, zmlog prints an
error message in the ZCOM error log file and ignores
the whole log buffer.
SR:None / DTS TPO0h02107:
It is found during code inspection/review that the zx25*()
APIs do not have prototypes defined. All the other ZCOM
APIs have such prototypes defined in zcomcall.h
TPO0h02189:
zset_rcvr() allows shared receivers to be set without
limit. But zget_shrcvr_list() silently imposes a limit
of 64 shared retrieves (ZcMAX_SHARED_RCVRS) that can
be retrieved. So a program can keep setting shared
receivers, but cannot retrieve the whole list.
SR: 5003427252 / DTS TPO0h02222:
When BX.25 code is compiled with zcomsys.h, compiler gives
error about the TRUE/FALSE definitions.
SR: 5003427245 / DTS TPO0h02228:
ACC does not comeup on reboot even when configured right.
TPO0h02238:
zconfig terminal delete deletes mux terminal but
returns error
TPO0h02263:
When using the X.25 protocol in the Z7300A and Z7330A
4-port ACC cards, if expeditied data (interrupt packets)
are sent, the virtual circuit will be reset with
disgnostic code of 145 three minutes after the
interrupt packet is transmitted.
TPO0h02280:
On the Z7330A and Z7300A 4-port ACC cards, a subchannel
can occasionally stop receiving frames on one port.
This would be indicated at the protocol level by
timeouts and excessive retry errors. The subchannel
can only be recovered by re-initializing the port.
TPO0h02292:
In TTGEN, the port and subchannel checks for T1 and E1
ports are of no difference. This is not correct and
causes illegal configuration passed down to the mux.
TPO0h02389:
On the Z7300A and Z7330A 4-port ACC cards,
under high message loads with large messages,
an occasional single byte of user message
data can be corrupted.
TPO0h02421:
TPO0h02425:
When running ZTERM, the primary ZLU and the open ZLU
(OP command) shows "$$$$" as the ZLU number. E.g.
% zterm
19:15:54 ZCOM Interactive command utility
19:15:54 Primary ZLU is $$$$
ZTERM>
ZTERM> op
19:15:58 ZLU #$$$$ opened with name AUX0235
ZTERM> op
19:16:03 ZLU #$$$$ opened with name AUX1235
ZTERM>
DTS: TPO0h02428 SR: 4701408526
wsio_map() error shows up in dmesg system log when
mapping EISA driver buffer.
TPO0h02486:
Hardware failured detected errors logged which is followed
by an ACC card reset.
TPO0h02617:
Card reset due to heartbeat timeout or messages being
logged indicating "Write completion length mismatch"
SR: 1653296699 / DTS TPO0h02624:
The zmntr message counter values are displayed as "$$$$$$$"
when the counter value exceeds 7 decimal digits.
TPO0h02669:
During extreme card activity (especially inbound data) PCI
systems, the system may panic with the following cause:
Non-access data TLB miss (on the ICS)
The panic stack trace produced by Q4 is:
crash event was a panic
panic+0x14
report_trap_or_int_and_panic+0x4c
interrupt+0x1ec
$ihndlr_rtn+0x0
nacc1_start_dma+0x394
nacc1_do_next_task+0x105c
nacc1_int_event+0xc58
nacc1_isr+0x20
dino_isr+0x128
inttr_emulate_save_fpu+0x100
idle+0x49c
swidle_exit+0x0
TPO0h02685:
Method required to repetitively run ACC card selftest
for diagnostic purposes.
TPO0h02712:
During ZCOM subsystem startup, the following error messages
are placed into the ZCOM log file:
zcom 00206 Card 0 Port 4 configuration failed with error 3.
zcom 00206 Card 0 Port 5 configuration failed with error 1.
The messages are logged infinitely with the port number
being incremented by one for each message logged.This ZCOM
log file quickly grows to fill the entire disk.
TPO0h02759:
Each time a "zmasterd stop" is issued, one or two additional
zombie processes are left that do not disappear until a
"zmasterd kill" is issued.
PHNE_17877:
TPO0h02485:
As your system is coming up during reboot, the ACC FixMajor
script reports mknod errors.
PHNE_16615:
SR 5003437947
For NIO 8-port ACC cards, DMA timeout was occurring
during ZCOM/ACC subsystem startup in HP K class systems
(and potentially any T series) with 2 or more ACC cards
installed. The problem is faster to reproduce if 2 ACC
cards have failing ports and/or the ACC cards are not
numbered consecutively (0, 1, 2, etc.) in the user's ACC
.answ file.
PHNE_15350:
TPO0h01894:
Loopback test on Z7330A and Z7300A cards may sometimes fail.
TPO0h01645:
ZMNTR loopback command does not report errors for wrong
options used.
TPO0h01493:
ZTERM on-line help is incomplete.
SR 4701391862 / DTS TPO0h01966
No current method to determine hardware revision
SR 5003417972/ DTS TPO0h2086
System panics when zx25l2stat_rcvr() called rapidly from
remote node.
DTS TPO0h01934
Timeout on $RSET cannot be distinguished from hard reset
timeout
DTS TPO0h01483 (Same as DTS TPO0h01934)
AMADEUS - zmasterd may be returning before card is
completely up or down
TPO0h01179:
Under high message loads on the Z7300A and Z7330A
4 port E1/T1 cards, the central processor utilisation
is higher than expected.
DTS TPO0h02076
Year 2000 - ROM timestamp will show 1900 after 2000
DTS TPO0h02097
Year 2000 - zterm timestamp incorrect after 1999
PHNE_13990:
DTS TPO0h01661
DAM runs heartbeat timer on an "unusable" card
DTS TPO0h01285
For HP-UX 10.0 and later, all driver major numbers
are dynamically assigned. When the ACC software
is installed, its devices are created with the correct
major numbers. However, if other products
containing kernel driver components are removed and/or
new kernel driver components are installed, the HP-UX
system can sometimes change the ACC's major numbers
without its knowledge. The results in the ACC device
files now pointing to non-existent or the wrong
(non-ACC) drivers. The ACC utilities are then no longer
able to access the ACC kernel components in the expected
way (the results of the access is random).
DTS TPO0h01643
zmon message 00111 (Last backplane command) has bad
info for 4 port card
DTS TPO0h01285
The ZCOM subsystem will fail to startup typically
with an immediate error return, but sometimes with
random symptoms.
DTS TPO0h01822
DMA timeouts on 4 port card
DTS TPO0h01913
During a card restart, the following message is
logged for a ZLU:
zcom 00207 ZLU 3 Set terminal parameters failed
with error: Protocol not loaded.
After the card restart processing completes, all
ZLUs mentioned by the above message will be
unusable (hung).
DTS TPO0h01914
Request issued to a ZLU hangs and is never processed.
That is,it is queued in the data structures but
never sent to the card.
Defect Description:
PHNE_22519:
SR: None CR: JAGab66302
zmasterd should be enhanced to accept ".answ" or
".tmem" file as argument on cold start, that is, either
of the examples mentioned below should be valid.
( example: zmasterd cold loopback.answ
zmasterd cold loopback.tmem )
o If argument is ".answ" file, then zmasterd should
- Run ttgen by itself for the mentioned ".answ"
file to generate a ".tmem" file.
- Cold start from the generated ".tmem" file.
o If the argument is ".tmem" file, then
- Cold start from ".tmem" file.
Resolution: This involves making changes in zmon such
that it can accept a ".answ" file for cold start, and
run ttgen internally.
SR: 8606112534 CR: JAGab84883
The boot startup record allways gets generated in
/var/opt/acc/log/thu.tlog because, the "System boot"
message is timestamped using the kernel "time" variable
before the variable is completely initialized. It
occurs in the nacc_ldm kernel module.
Resolution: The solution implemented is to timestamp
the "System boot" message when it arrives in the user
space zmlog process.
SR: 8606112735 CR: JAGab87447
A "Set Terminal Parameters" request followed by
"Enable" and "Activate" requests in a single $DATA
backplane request are not handled correctly by the
firmware. The specific cause is, the firmware checks
that terminals are assigned to ports before all the
requests in a single $DATA request have been processed.
Resolution: The problem is solved by performing the
firmware check for terminals being assigned to ports
after all previous requests in the backplane
transaction have been processed.
SR: 8606125003 CR: JAGac40395
The level 2 maximum frame size was incorrectly set to
264 octets for packet sizes lesser than 256.
Resolution: The correct value is now configured by the
ACC firmware.
SR: 8606128460 CR: JAGac84425
When no buffer offset is used by the protocol, the
backplane handling did not allocate a buffer, but
assumed one was available.
Resolution: A buffer is now allocated for all zero
length messages.
SR: 8606128633 CR: JAGac86180
The processing to update the error counter was missing
in the ACC X.25 firmware on the 4-port E1/T1 ACC cards.
Resolution: The processing has been added to update
the terminal error counter whenever the X.25 statistics
are uploaded.
SR: 8606131450 CR: JAGad00600
During testing cycle, zmasterd deact znode, left znode
still running, whereas zmasterd deact zmlog, will
remove zmlog from the run state. The problem was
occuring because the znode daemon was ignoring the
SIGTERM signal.
Resolution: Code has been modified so that the znode
daemon no longer ignores the SIGTERM signal.
SR: 8606133312 CR: JAGad02457
The interface tunable parameter "tsize" for the E1/T1
cards has inadequate editing in ttgen and checking in
the firmware. If a value of 1 is specified it is
accepted by ttgen and the firmware causing a firmware
failure. The minimum allowable value is 8 bytes. This
would allow the header only, with no timers. The
actual value must be a multiple of 8 bytes. Each timer
entry occupies 8 bytes, in addition to the header.
Resolution: The fix is to modify "ttgen.c" so that
"tsize" is a multiple of 8, minimum 8.
SR: 8606133865 CR: JAGad03005
The FALC hardware has trouble re-syncing with the
signal in T1 mode after the idle pattern has been
previously invoked.
Resolution: If the idle pattern is re-enabled when the
line goes down then the FALC has no trouble re-syncing
as soon as there is a T1 signal present.
SR: 8606144270 CR: JAGad13610
When the 'MV' command in ZTERM is used, it gives the
error; "Error on ZQMVE: Different nodes not allowed"
when moving a message from a program ZLU to another
program ZLU. Both are local ZLUs. The error message
is seen because there was not enough memory to move the
message from a program ZLU to another program ZLU.
Resoultion: The fix is to implement a sleep-wait
mechanism until resources are available and only when
the resource is available the move is done.
SR: 8606147407 CR: JAGad16750
When trying to combine two subchannels using zconfig,
with the action set to ZcDSC_SET_TIMESLOTS in
zconfig(3x), an error number -25 (Illegal buffer Len)
was obtained.
Resolution: The zconfig.3x man page has been modified
to provide information about how to use zconfig for
actions ZcDSC_SET_TIMESLOTS and ZcDSC_SET_SUBC_SPECS.
SR: 8606152257 CR: JAGad21596
While doing QIP API047 test, in an erronous ZTERM PT
command (ZPORT configuration), the return status was
incorrectly reported. E.g. ZPORT status 11 is
reported as "Invalid subchannel number (which is the
status for terminal configuration request). ZPORT
status 11 should be "Mode/baud rate incompatibility".
Resolution: zterm used an incorrect request code in
calling x25stat(). This has been rectified.
SR: 8606161688 CR: JAGad31008
The zmntr utitlity can be used to check the status of
an ACC MUX. The command "zmntr mx" also shows the
utilization of the processor on the ACC MUX. With the
development of the TRAU/GPRS protocol the customer is
running some tests, especially load tests. But the MPU
acitivty with the use of the TRAU/GPRS prorotcol stays
always at 0%. The problem was occuring because the
$STAT message in the DAM was given lower priority
compared to messages in Express Queue, High Priority
Queue and Low Priority queue. Because of this, the
Status always got updated after processing messages in
the queues. Hence the % activity always showed 0%
because the CPU already finished processing messages
and is now idle.
Resolution: Code changes have been done such that the
$STAT message is given the highest priority than the
messages in the Express Queue, High Priority, and Low
Priority Queue.
SR: 8606170918 CR: JAGad40182
The system panic was because the address generated by
Zc1_dma_A_save_buflet_data to access the IO PDIR entry
was going out of the IO PDIR table. The code was
incorrectly doing an bitwise OR with 0x80000000. This
caused the overrun of the IO PDIR table.
Resolution: The bitwise OR with 0x80000000 has been
removed.
SR: 8606171991 CR: JAGad41254
splx() calls were not handled correctly. SPL for the
processor was not lowered.
Resolution: splx() calls that were not done properly
in the code are now done. Without these changes, the
system could panic with spinlock deadlock message.
PHNE_18716:
DTS TPO0h02823
The fault handling routines have been enhanced to
decode the fault record on the stack and placed in
global storage. Also the G and R registers are
saved (and the first 2 G registers are no longer
corrupted).
DTS TPO0h02806
The zmasterd man page has been update to include the
"kill" option of this utility.
DTS TPO0h02738
The problem is caused by some unprotected critical
code. With high message load, there is more chance
that the unprotected code will be interrupted and
re-executed by the interrupt process, which causes
queue corruption.
DTS TPO0h02674
The SAM description files have never been created for the
ACC products. This patch now includes appropriate ACC
files for SAM.
DTS TPO0h02813
When a port mode value is specified in the TTGEN
configuration that is not supported by the card type,
the error message logged is unclear or confusing. The
message text has been modified to indicate the port
mode value is invalid for the card type.
DTS TPO0h02786
This problem occurs when a very high receive
descriptor load is immediately followed by two background
crxio() processes.
This leads to the receive descriptor with the HOLD bit set
to remain the HELD descriptor. This prevents the Munich
from receiving any further frames until the subchannel
is disabled and enabled again.
With a normal configuration this problem is possible but
very unlikely to occur.
DTS TPO0h02765
After the r2.40.01 ISDN/ACC product is installed,
the /etc/nettlgen.conf file will contain the
ISDN_ACC_USR record to refer to the libTELfmt.sl
shared library. netfmt fails when it refers to
the libTELfmt.sl which is not built properly.
DTS TPO0h02783
The error checking for invalid port configurations failed
to account for a port mode setting of LBACK. That is,
TTGEN was validating that when the port mode was
configured for E1, that E1 frame modes were used and
that when the port mode was T1, that T1 frame modes
were used. This caused the frame mode check to fail
an E1 or T1 specific frame mode was selected and the
port mode was set to LBACK (because LBACK is neither
T1 or E1). The code has been modified to allow all
frame modes when the port mode is LBACK.
DTS TPO0h02610
There is a commitment to provide Q4 support for the
ACC B.02.39 and B.02.40 releases.
DTS TPO0h01522
Mishandling of the rrch flag was found in the firmware code.
The handling of the flag has been corrected.
DTS TPO0h01780
The HDLCABM state machine was not designed to handle
REJect frame retransmission. Extensive changes have
been made to the HDLCABM state machine to handle REJect
frame retransmission.
DTS TPO0h02172
HDLC firmware was ignoring this condition.The HDLC firmware
has been corrected.
DTS TPO0h02173
Bad state change on N2/N200 timer expiration. The finite
state machine (FSM) has been corrected.
DTS TPO0h02175
Incorrect behaviour coded into the HDLCABM state machine.
The state machine has been corrected.
DTS TPO0h02242
An X.25 status request transaction is sent to the card while
the terminal is being deleted. The stat request is queued
on the terminal's queue, but not through the normal
mechanism which pushes the backplane code onto the message
stack. This mechanism did not check if the terminal is
deleted. When a new terminal (with same terminal#) is
created some time later, the stat request is sitting on its
queue. It is then processed by the protocol layers and a
stack underflow occurs, producing a CPU fault. The code has
been changed to include the verification that the terminal
is not deleted, which prevents the stat request transactions
from being queued.
DTS TPO0h02245
The pmon utility doesn't delete the receiver for the dynamic
reconfiguration events using the zevent_rc. The cleanup
code has been added to the exit routine.
DTS TPO0h02255
The X.25 firmware was using an 8-bit sequence counter to
ensure in-sequence delivery of write completion messages
back to the host. The result is that the firmware could not
handle more than 256 outstanding transmitted packets at once
Since these particular request messages arrive on the card
via the express queue, no flow-control mechanism is in place
. More than 256 sent requests to the card resulted in out of
sequence write completions. The X.25 firmware sequence
counter has been extended to 16 bits. This increases the
maximum outstanding requests to 65536 messages.
DTS TPO0h02273
Mishandling of the cclr flag was found in the
firmware code.The handling of the flag has been
corrected.
DTS TPO0h02438
The firmware selftest (of the Munich chips)
overwrites an area of memory that is used to store
data during firmware execution. This Munich
selftest is executed as part of the card reset.
Since the self-test code is contained in the ROM
has been reorganised to avoid the areas used by
the Munich self-test.
DTS TPO0h02620
The x25 firmware incorrectly processes the
disable request if there were outstanding uncompleted
control write requests, because of pending level 2
control packets to be transmitted.
The x25 firmware processing of the disable request
has been corrected.
DTS TPO0h02775
There is a switch() statement in lbtest.c which
has it's logic wrong!
There is an almost identical problem in the almost
identical code in pmon.c which, although it has not
yet caused a problem, is also fixed.
DTS TPO0h02774
The problem occurs when the process_port.c module
performs a hardware reset of the Munich and Falc
chips on the port - using a library function
port_reset(). As part of this reset the register
0xC0000004 is written with bit 3 set (DHOLD bit).
This is intended to prevent ALL Munich chips accessing
the system bus during the hardware reset. What happens
is that if there is Munich activity on the system bus
when the DHOLD bit is set, then only a few more Munich
cycles occur and then the system bus is permanently
stopped.
The port configuration can only cause this problem if
at least one other port is in operation.
The Munich chips are now given a 'soft' reset when the
port is re-configured. The hadware reset is not used
at all.
DTS TPO0h02762
The boundary case where the Munich receive
channel goes through the whole descriptor
chain before any are freed up, is not
handled. Additionally there is no provision
to handle frames larger than can be contained
in the available set of receive descriptors.
On the transmit side, frames which are too
large to be processed with the available
transmit descriptors, can be left queued
forever, causing the transmit channel to hang.
The new version of frame.c can now handle any
size received frame, regardless of the
configured buffer size.
On the transmit side, frames which could be
transmitted when TDs are freed up later are
left queued. Frames which can never be
transmitted because they contain more buffers
than there are transmit descriptors available
are flushed with the IO_LONG_MSG status code.
The maximum size transmit frame can be
calculated with the formula:
F = (B-16) * 99
Where B is the configured buffer size and F
is the maximum transmit frame size.
DTS TPO0h02331
This defect follows on from TPO0h02292, which
addresses error detection in ttgen of unusable
timeslots for T1.
This defect is to include an error check in the
4-port firmware $PORT command to reject invalid
configurations when using dynamic configurations.
For the general port configuration (ZcDSC_ALL_PARMS)
the firmware now prevents timeslot 0 being assigned
to any subchannel except subchannel 0 (must be allowed
for the default - unconfigured - case). The firmware
prevents timeslots 25 to 31 being assigned to any
subchannel except subchannel zero in T1 mode.
For timeslot configuration requests, the firmware does
not allow timeslot zero to be configured, or timeslots
25 to 31 in T1 mode.
DTS TPO0h02681
The FALC-LH has many changes in this area , and
the new "loop-timed" mode is now necessary for
E1 to operate correctly. The description of the
"looped-timed" proessing in the FALC-LH documentation
matches precisely what we require for "EXT clock"
operation.
In the changes originally made for the 60008 card,
Loop-timed was included as an extra clock mode.
For this defect, the loop-timed clock option will
be removed, and "Loop-timed" mode enabled on the
FALC-LH whenever "EXT clock" is configured.
DTS TPO0h01918
The Munich communications controller can be
requesting the i960 bus access, just as it is
reset at the end of the selftest. This condition
prevents further processing by the i960
microsprocessor, until the i960 is reset.
The workaround to the problem is to implement
a reset retry mechanism in zmon, to retry the
selftest if it fails to complete.
DTS TPO0h02063
The ZcDSC_SET_TIMESLOTS and ZcDSC_SET_SUBC_SPECS $PORT
actions are now implemented as specified in the original
E1/T1 card ERS. The LDM, DAM and firmware all had to
be changed.
When the ZcDSC_SET_TIMESLOTS and ZcDSC_SET_SUBC_SPECS
$PORT actions are requested the LDM was checking the
length of the supplied subchannel/timeslot buffer
incorrectly. The LDM now checks that the buffer length
is equal to "sizeof(subchbuf_def)".
On completion of these requests the DAM has to update
the subchannel and timeslot configurations which have
been modified. This is now implemented.
The firmware module backplane.c has been modified to check
the appropriate subchannels for any enabled terminals
when a ZcDSC_SET_TIMESLOTS or ZcDSC_SET_SUBC_SPECS action
is requested. ie. When configuring a timeslot, the current
subchannel and new requested subchannel (may be the same
one) must both be checked for any enabled terminals, and
when configuring a subchannel, that subchannel must be
checked for any enabled terminals. If any terminals are
enabled a new status code (PT_SC_ENB) is reported.
The man page for zconfig.3x has been updated to explain
the use of the ZcDSC_SET_TIMESLOTS and
ZcDSC_SET_SUBC_SPECS actions.
DTS TPO0h02239
The HDLC.FRAME protocol now puts the line down
if RAI is received continuously for 3-4 seconds
(as well as when frame sync is lost).
DTS TPO0h02423
For E1 the options are:
Framing
DF
CRCMF
Encoding
HDB3
AMI
For T1 the options are:
Framing
F4
SF
ESF
F72
Encoding
B8ZS
AMI
These are not interchangeable.
These checks are now in place.
DTS TPO0h02446
TTGEN now reports an error in this case.
DTS TPO0h02477
The mqfreeput() library function, when freeing a
message composed of a queue of message headers
(rather than buffers), makes the assumption that
all of the component messages will have originated
from the same subchannel as the first message, and
adjusts the subchannel quota table of the first
message header in the queue accordingly.
This assumption is not always correct and can lead
to the subchannel quota tables being corrupted.
This does not affect any of the existing protocols,
since there is never a case where messages
originating from different subchannels are queued
on the same message header.
In the new firmware, as each message is freed from
the message header queue, the quota pointed to by
the freed message is updated.
DTS TPO0h02676
The FALC waveform shaping parameters for the
T1 RJ45 100ohm case are not right. New parameters
are now implemented.
DTS TPO0h02414
The transmit timeout is fixed at 1 second which
is not enough to allow the complete transmission
of a full buffer (238 bytes) at 1200 baud or less.
DTS TPO0h02504
This is due to an enhancement that was made for
defect TPO0h02414. The transmit timeout used at
level-1 was shortened for baud rates as high as
64000.
Because incorrect baud rate configurations can
lead to this problem, part of the changes made
for TPO0h02414 have now been backed out.
The minimum timeout used is now 1 second which
will allow for typical incorrect configurations.
DTS TPO0h02723
The "downcounter" used to count the number of one
second events at which the state of the line has
changed does NOT get reset whenever the line
is found UP in the UP state or DOWN in the DOWN state.
This means the "second" count keeps accumulating
until the line state changes. So if the line was
found down 4 times since the port was started up then
the next time the line is found to be down, the line
will be marked DOWN immediately. The state is still
checked only once each second so glitches are unlikely
to bring the line down. However the line may go
down within one second of the "Remote alarm" signal
occuring in this case. This would only be noticed
on a line with a lot of errors or one which has been
running for a long time.
The "downcounter" is now reset each time the line
is found to be UP.
DTS TPO0h02246
Because PMON creates a monitoring terminal on
each E1/T1 port and enables it, ZMNTR cannot
re-configure these ports.
The answer is for ZMNTR to disable the PMON
terminal on a port while it runs the loopback
test on that port. The PMON terminal can then be
re-enabled.
TPO0h00545
This is an enhancement. A new mechanism is introduced.
When the current log file (binary or text) gets to a max
size, it is renamed with ".old" suffix(e.g. mon.tlog.old).
A new empty log file is created as the current log file.
If messages continue to come in before the end of day and
the new log file hits the max again, it will be renamed
again and OVERWRITE the previous ".old" file. This will
result in losing messages. But the TOTAL size used by
1-day's log file is limited to TWICE the maximum file
size.
The default maximum size of a log file is set at 1Gb (text
or binary log). Practically it means no limit, and is for
backward compatibility. This maximum log file size can be
set by the new zmlog options -B and -T. Note that the
zmasterd list file "/opt/acc/cfg/zmasterd_list" needs to
be modified manually to use the -T and -B options to set
the maximum log file size to non-default values.
TPO0h01209
ttgen did not take into account the entire set of ACC
boards.
TPO0h01523
Currently, zmasterd & zmon use msg queue (msgrcv/ msgsnd)
to communicate the command: zmasterd to zmasterd daemon
and response: zmon daemon to zmasterd daemon. The
msgsnd() call used is a "Send-With-Wait" call. When
there is not enough msg buffer in the system, the
caller will be suspended until msg buffer is available.
In this case of bad kernel config, it will be forever.
Both zmasterd&zmon are changed to do a loop of msgsnd()
With-No-Wait. The loop is of 15 seconds (5 retries with
3-second sleep interval). If system is out of msg buffer
for 15 seconds, both of them will detect the error:
Resource temporarily unavailable. This error will be
logged to zcomlog and to console. And zmasterd & zmon
is able to continue its processing.
TPO0h01629
There was no option to specify a different path for the
core dump directory. We have added the -f option that
allows an user to specify the full path of the core dump.
TPO0h02037
It is suspected that it is caused by contention
in the driver, e.g. when multiple pieces of driver
codes is trying to log messages and hitting some
unprotected criticial sections.
TPO0h02107
It was missed out when the zx25*() functions were first
introduced to ZCOM.
Function prototypes are added to "zcomcall.h", which is
intended to be included when user wants to have prototype
checking.
TPO0h02189
A simple check is added to the LDM driver to limit the
number of shared receivers to ZcMAX_SHARED_RCVRS (64).
A new error ZERCVRFULL (-18) is returned when trying to
add more receivers. The new error is added to zcomsys.h
and zerrmsg.txt. zevent_rcvr, zset_rcvr man pages are
also updated.
TPO0h02222
In zcomsys.h, the TRUE/FALSE definitions uses type casting
to zc_boolean. Somehow, in some BX.25 application source,
this crashes with other defintions of TRUE/FALSE.
TPO0h02228
The /sbin/rc2.d and /sbin/rc1.d links are not set up for
the base product.
TPO0h02238
The zconfig delete request is processed as far as the
(destructive) zcntl delete request (which succeeds and
make the terminal unavailable), but fails to complete
the request by fully deleting the host terminal structures
because of the queued message.
TPO0h02263
The internal timer for the interrupt confirmation
packet was not being stopped when the interrupt
confirmation was received. The code has been corrected.
TPO0h02280
A subchannel can be unexpectedly initialized as a result
of an incorrect command to the Munich HDLC controller.
The condition no longer causes the subchannel to be
intialized.
TPO0h02292
The appropriate checks are added to ttgen:
For T1 port:
valid subchannel numbers: 0..31
valid timeslot numbers: 1..24
For E1 port:
valid subchannel numbers: 0..31
valid timeslot numbers: 1..31
TPO0h02389
When a large number of received messages are transferred
in a single backplane transaction, the last byte of user
data in a dma transfer can be corrupted. The code has
been corrected to ensure the data is correctly set up
before the dma transfer is initiated.
TPO0h02421
This is a long known problem in ZTERM when ZLU number is
larger than 9999. ZTERM uses a 4-char buffer to convert
the number to ASCII characters and its conversion routine
uses $$$$ to indicate overflow. In TTGEN answerfile, if
"Terminal-ZLU" is defined as 10000, ZCOM will use 10001
and onwards for program ZLUs. In this case, when ZTERM
opens its primary ZLU, it'll get 10001, which will cause
the conversion routine to overflow.
The whole ZTERM program is checked for 4-digit conversion.
If overflow can occur, it is changed to 5-digit conversion.
Most of them are the ZLU numbers. Some LTT and PTT
numbers are also fixed.
TPO0h02425
Here is a case where a msg was sent down to the card
and the Write completion is yet to arrive. Meanwhile
the Terminal is deleted that causes the Express, Hi
and low priority queues to be flushed.
On the arrival of Write completion we try to match
and get to the msg we sent to the card and since the
queues are flushed as part of deleting the TERM it does
not find it. So results in panic.
TPO0h02428
The problem is analyzed to be that we are not ZERO-ing
the data structures used for eisa_dma_setup() .
TPO0h02486
This problem was caused by an interrupt collision between
the NIO Lo-Quix chip on the ACC card and the HP-UX host.
That is, the card sent up an external interrupt at the
exact same time the host told the card to turn-off
interrupts and to start a DMA operation. This resulted
in the Lo-Quix chip being unable to complete the DMA
request which eventually times out. The nacc1 and nacc0
drivers was modified to detect this condition and to
sequence events to avoid the problem.
TPO0h02617
The nacc drivers were being entered re-entrantly by the
interrupt handler and/or user space request. This could
result in a variety of symptoms or which two are listed.
This was caused by timing windows in the code that could
allow a second thread of execution in a multi-processor
environment to reenter driver routines that do not allows
this. The driver code was modified to eliminate
the timing windows.
TPO0h02624
This symptom is as designed and indicates and out-of-range
number. That is, there is insufficient room to display
the number.
TPO0h02669
When the driver receives an external interrup performing
the byte swap. If the number of pending events exceeded
127, a *very* large negative number results which is used
to program the next DMA operation which then cause the
indicated panic.
TPO0h02685
An enhancement is provided to run the ACC card selftest
repetitively using a new command SF. Please consult
the SF command help interactively for further information.
From the zdbi960 prompt type: "? sf"
TPO0h02712
This problem occured due to an incorrectly coded IF
statement which allowed the RESTART processing to continue
past the end of the number of ports allowed on the E1/T1
card and also not retrieving the next port to be processing
in the completion function. This caused the driver to
continue issuing $PORT request for MAXINT number of ports.
All $PORT request past port #3 would fail with an error
message thus filling up the disk with zmlog error messages.
The 4-port E1/T1 driver code has been corrected.
TPO0h02759
After the "zmasterd stop" command completed, zmasterd was
not receiving its children's termination signal causing
them to be left hanging around in the system until the
master copy of zmasterd terminated. The code has been
modified to issue a waitpid() to terminate all children
after the "stop" command is executed.
PHNE_17877:
TPO0h02485:
An incorrect newer version of FixMajor was included
with the previous patch.
PHNE_16615:
SR 5003437947
The system part of the firmware was not verifying
whether the LO-QUIX chip (responsible for managing
backplane transactions) on the ACC card was ready
before requesting another I/O operation.
PHNE_15350:
TPO0h01894:
The relays used to connect the network and loopback lines
on the E1/T1 cards take a finite time to switch.
The loopback test can sometimes be too fast for the relays
and the test can fail.
TPO0h01645:
The only options accepted now are "i" "e" or "2". The
first bad option character is reported to the user.
TPO0h01493:
The ZTERM on-line help file has been updated.
SR 4701391862 / DTS TPO0h01966
Enhancement to detect hardware revisions of ACC cards.
A standard interface has been defined to identify hardware
revisions of all ACC cards. The 'mx' command of zmntr has
been enhanced to include the display of the hardware
revision.
DTS TPO0h01934
The ZCOM startup does not wait for all the card
to startup. If a device failed to startup, the
zmasterd utility returns without knowing if the card
startup retry is successful.
SR 5003417972/ DTS TPO0h2086
Panic was due to ZCOM memory corruption. One of the Znode
kernel routine was calling a ZCON routine with a missing
argument. This caused the ZCOM memory to be corrupted.
TPO0h01179:
The multi-message protocol used to transfer messages
to and from the card is under-utilised, resulting
in more driver activity than is necessary.
This is an enhancement to introduce a delay in the data
transfers to and from the ACC cards, to allow better
advantage to be taken of the multi-message protocol.
The default delay is 5 milliseconds, allowing significant
reduction in cpu utilisation, whilst having a minimal
increase in message latency. The default value is strongly
recommended.To configure the delay, use the keyword
"datadelay <value_in_ms>" in the interface definiton
section of the ttgen .answ file.To override the delay, use
"datadelay 0".
TPO0h02076
When zmon initializes an ACC card, it uploads the ROM ID
information from the card. One of the fields is the ROM
timestamp in YYMMDD.hhmm ASCII format. zmon extracts the
digits and convert the timestamp to HPUX time and save it
in IFT. The two-digit year value is passed to mktime(),
which expects a year value since 1900. In Year 2000, a
ROM timestamp with year "00" will be shown as 1900.
The timestamp conversion in zmon is modified to check
whether the 2-digit year is less than 70. If so, it adds
100 to the year number before calling mktime() to convert
the time. This supports year 1970 to 2037. Year 1970 is
chosen because it is the base year of HPUX time. Year
2037 is when the 32-bit time overflow.
DTS TPO0h02097
When zterm is employed, timestamp as well as activity will
be reported.The call numerictime, currently returns a
timestamp in the form YYMMDD.HHMMSS.In Year 2000, the
timestamp is returned in the form YYYYMMDD.HHMMSS.The code,
has been modified to accomodate for both scenarios.
PHNE_13990:
DTS TPO0h01661
Heart beat timeouts on unusable card
DTS TPO0h01913
This problem occurs when a ZLU has been dynamically
created but has not yet been configured with a zcntl
request to set the terminal paramters and the card
is restarted (either through a firmware failure or
user initiated action). Part of the restart processing
is to issue a set terminal parameters request on every
ZLU that is defined. In this case, the terminal
parameter data is all NULLs (since the user has not
configured it yet) which results in the firmware failure
the request with a "protocol not loaded"
error. Note that part of ther terminal parameter data
is which protocol to use.
TPO0h01914
The application is dynamically creating a ZLU on a
subchannel or port that has not been defined or
configured. The dynamic configuration code is not
checking for this condition.
SR:
4701323840 5003380527 5003415463 5003427245 4701408526
1653296699 5003427252 4701381277 4701391862 5003417972
5003437947 8606112534 8606112735 8606125003 8606128460
8606128633 8606131450 8606133312 8606133865 8606144270
8606147407 8606152257 8606161692 8606170918 8606171991
Patch Files:
/usr/conf/master.d/nacc
/opt/acc/share/man/man1.Z/zmasterd.1
/usr/sam/lib/kc/paramsACC.tx
/usr/sam/lib/kc/subsysACC.tx
/usr/sam/lib/kc/driversACC.tx
/opt/acc/TEL/lib/libTELfmt.sl
/opt/acc/protocol/testprot.zrel
/usr/conf/lib/libnacc1_niosyms.o
/usr/conf/lib/libnacc1_pcisyms.o
/usr/conf/lib/libnacc_eisasyms.o
/usr/conf/lib/libnacc_niosyms.o
/usr/conf/lib/libzcomsyms.o
/opt/acc/msg/default.txt
/opt/acc/bin/pmon
/opt/acc/sys/wmux4.zrel
/opt/acc/bin/zdbi960
/opt/acc/msg/def.zdbi960.txt
/opt/acc/share/man/man3.Z/zevent_rcvr.3x
/opt/acc/share/man/man3.Z/zset_rcvr.3x
/opt/acc/share/man/man3.Z/zconfig.3x
/opt/acc/msg/zerrmsg.txt
/opt/acc/bin/zmasterd
/opt/acc/bin/nacc1_stats
/opt/acc/bin/nacc1_trc
/opt/acc/bin/nacc_trc
/opt/acc/include/zcom/zcomcall.h
/opt/acc/bin/zmlog
/opt/acc/msg/def.zmlog.txt
/sbin/init.d/acc
/etc/rc.config.d/acc
/opt/acc/lbin/FixMajor.awk
/opt/acc/z7350a/loopback.zabs
/opt/acc/z7350a/loopback.zmap
/opt/acc/protocol/level1.zrel
/opt/acc/msg/def.zcom.txt
/opt/acc/lbin/FixMajor
/opt/acc/bin/zmon
/opt/acc/msg/def.zmon.txt
/opt/acc/bin/znode
/opt/acc/bin/zmntr
/usr/conf/lib/libnacc_nio.a
/usr/conf/lib/libnacc_pci.a
/usr/conf/lib/libzcom.a
/opt/acc/z7400a/loopback.zabs
/opt/acc/z7400a/loopback.zmap
/opt/acc/sys/z7350_fw.zrel
/opt/acc/sys/z7400_fw.zrel
/opt/acc/z7300a/download.zabs
/opt/acc/z7330a/download.zabs
/opt/acc/bin/ttgen
/opt/acc/bin/zscan
/opt/acc/msg/def.ttgen.txt
/opt/acc/msg/def.zscan.txt
/opt/acc/msg/zterm.hlp
/opt/acc/include/zcom/zcomsys.h
/usr/conf/acc/zcomsys.h
/opt/acc/bin/zterm
/opt/acc/sys/wmux3.zrel
/opt/acc/sys/wmux1.zrel
/opt/acc/z7200a/loopback.zabs
/opt/acc/z7200a/loopback.zmap
what(1) Output:
/usr/conf/master.d/nacc:
None
/opt/acc/share/man/man1.Z/zmasterd.1:
None
/usr/sam/lib/kc/paramsACC.tx:
None
/usr/sam/lib/kc/subsysACC.tx:
None
/usr/sam/lib/kc/driversACC.tx:
None
/opt/acc/TEL/lib/libTELfmt.sl:
None
/opt/acc/protocol/testprot.zrel:
ZCOM Port Diagnostic Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 te
stpro
/usr/conf/lib/libnacc1_niosyms.o:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
nacc1_niosyms.o
/usr/conf/lib/libnacc1_pcisyms.o:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
nacc1_pcisyms.o
/usr/conf/lib/libnacc_eisasyms.o:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
nacc_eisasyms.o
/usr/conf/lib/libnacc_niosyms.o:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
nacc_niosyms.o
/usr/conf/lib/libzcomsyms.o:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
zcomsyms.o
/opt/acc/msg/default.txt:
$Header: default.txt/main/4 11/20/96 15:33:26 $
/opt/acc/bin/pmon:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 pmo
n
/opt/acc/sys/wmux4.zrel:
ZCOM System Software (WMUX4)
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 wm
ux4.z
FTXBEGIN. Do nothing if disabled
FTXBEGIN. Force processing if timer not running.
FTXBEGIN. Disable Tx Interrupts
FTIMR. Disable Tx Interrupts
/opt/acc/bin/zdbi960:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 zdb
i960
/opt/acc/msg/def.zdbi960.txt:
$Header: def.zdbi960.txt/main/r2.40/2 03/30/99 21
:08:43 $
/opt/acc/share/man/man3.Z/zevent_rcvr.3x:
None
/opt/acc/share/man/man3.Z/zset_rcvr.3x:
None
/opt/acc/share/man/man3.Z/zconfig.3x:
None
/opt/acc/msg/zerrmsg.txt:
$Header: zerrmsg.txt/main/r2.40/1 05/28/99 12:51:
35 $Rev: /main/r2.40/1 $
/opt/acc/include/zcom/zcomcall.h:
$Header: zcomcall.h/main/r2.40/1 05/26/98 21:15:5
5 $Rev: /main/r2.40/1 $
/opt/acc/bin/nacc1_trc:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 nac
c1_trc
/opt/acc/bin/nacc_trc:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 nac
c_trc
/opt/acc/bin/zmasterd:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 zma
sterd
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 lib
Zmd_c.a
/opt/acc/bin/nacc1_stats:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 nac
c1_stats
/opt/acc/bin/zmlog:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 zml
og
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
Zmd_c.a
/opt/acc/msg/def.zmlog.txt:
$Header: def.zmlog.txt/main/r2.40/1 05/25/99 13:2
0:14 $Rev: /main/r2.40/1 $
/sbin/init.d/acc:
$Revision: 72.11 $
/etc/rc.config.d/acc:
None
/opt/acc/lbin/FixMajor.awk:
None
/opt/acc/z7350a/loopback.zabs:
ZCOM System Firmware (ROM) Rev 01.T5
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 z7
350_r
ZCOM Z7350A System Software
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 z7
350_f
CPU clock 32MHz
ZCOM LEVEL1 Protocol
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 le
vel1.
ZCOM Monitor Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 mo
nitor
ZCOM Port Diagnostic Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 te
stpro
ZCOM Protocol Module Entry Point Table
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 pm
entta
/opt/acc/z7350a/loopback.zmap:
ZCOM System Firmware (ROM) Rev 01.T5
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 z
7350_
ZCOM Z7350A System Software
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 z
7350_
CPU clock 32MHz
ZCOM LEVEL1 Protocol
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 l
evel1
ZCOM Monitor Module
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 m
onito
ZCOM Port Diagnostic Module
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 t
estpr
ZCOM Protocol Module Entry Point Table
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 p
mentt
/opt/acc/protocol/level1.zrel:
ZCOM LEVEL1 Protocol
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 l
evel1
/opt/acc/msg/def.zcom.txt:
$Header: def.zcom.txt/main/r2.40/1 02/06/98 08:11
:58 $Rev: /main/r2.40/1 $
/opt/acc/lbin/FixMajor:
None
/opt/acc/bin/zmon:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 zmo
n
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
Zmd_c.a
/opt/acc/msg/def.zmon.txt:
$Header: def.zmon.txt/main/r2.40/2 11/03/00 13:21
:19 $Rev: /main/r2.40/2 $
/opt/acc/bin/zmntr:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 zmn
tr
/opt/acc/bin/znode:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 zno
de
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
Zmd_c.a
/usr/conf/lib/libnacc_nio.a:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
nacc.a
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 $He
ader: Zc_dma_A.c/main/17 09/16/97 17:10:0
0 $
/usr/conf/lib/libnacc_pci.a:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
nacc.a
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 $He
ader: Zc_dma_A.c/main/17 09/16/97 17:10:0
0 $
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
eacc.a
/usr/conf/lib/libzcom.a:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 lib
zcom.a
/opt/acc/z7400a/loopback.zabs:
ZCOM System Firmware (ROM) Rev 01.B5
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 z7
400_r
ZCOM Z7400A System Software
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 z7
400_f
FTXBEGIN. Do nothing if disabled
FTXBEGIN. Force processing if timer not running.
FTXBEGIN. Disable Tx Interrupts
FTIMR. Disable Tx Interrupts
ZCOM LEVEL1 Protocol
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 le
vel1.
ZCOM Monitor Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 mo
nitor
ZCOM Port Diagnostic Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 te
stpro
ZCOM Protocol Module Entry Point Table
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 pm
entta
/opt/acc/z7400a/loopback.zmap:
ZCOM System Firmware (ROM) Rev 01.B5
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 z
7400_
ZCOM Z7400A System Software
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 z
7400_
ZCOM LEVEL1 Protocol
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 l
evel1
ZCOM Monitor Module
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 m
onito
ZCOM Port Diagnostic Module
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 t
estpr
ZCOM Protocol Module Entry Point Table
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 p
mentt
/opt/acc/sys/z7350_fw.zrel:
ZCOM Z7350A System Software
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_18716 z7
350_f
CPU clock 32MHz
/opt/acc/sys/z7400_fw.zrel:
ZCOM Z7400A System Software
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 z7
400_f
FTXBEGIN. Do nothing if disabled
FTXBEGIN. Force processing if timer not running.
FTXBEGIN. Disable Tx Interrupts
FTIMR. Disable Tx Interrupts
/opt/acc/z7300a/download.zabs:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 ACC
Base F/W
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 LAP
-B Protocol F/W
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 LAP
-D Protocol F/W
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 X.2
5 Protocol F/W
/opt/acc/z7330a/download.zabs:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 ACC
Base F/W
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 LAP
-B Protocol F/W
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 LAP
-D Protocol F/W
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 X.2
5 Protocol F/W
/opt/acc/bin/ttgen:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 ttg
en
/opt/acc/bin/zscan:
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 zs
can
/opt/acc/msg/def.ttgen.txt:
$Header: def.ttgen.txt/main/r2.40/9 11/03/00 13:2
1:17 $Rev: /main/r2.40/9 $
/opt/acc/msg/def.zscan.txt:
$Header: def.zscan.txt/main/r2.40/1 03/04/98 17:0
7:26 $Rev: /main/r2.40/1 $
/opt/acc/msg/zterm.hlp:
$Header: zterm.hlp/main/r2.40/1 02/22/98 17:21:10
$Rev: /main/r2.40/1 $
/opt/acc/include/zcom/zcomsys.h:
$Header: zcomsys.h/main/r2.40/9 05/28/99 12:41:07
$
/usr/conf/acc/zcomsys.h:
$Header: zcomsys.h/main/r2.40/9 05/28/99 12:41:07
$
/opt/acc/bin/zterm:
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 zte
rm
/opt/acc/sys/wmux3.zrel:
ZCOM System Software (WMUX3)
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 w
mux3.
CPU clock 16MHz
/opt/acc/sys/wmux1.zrel:
ZCOM System Software (WMUX1)
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 w
mux1.
/opt/acc/z7200a/loopback.zabs:
ZCOM System Firmware (ROM) Rev 04.B 921106.1200
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 z7
200_s
ZCOM System Software (WMUX1)
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 wm
ux1.z
ZCOM System Software (WMUX3)
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 wm
ux3.z
CPU clock 16MHz
ZCOM System Software (WMUX4)
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 wm
ux4.z
FTXBEGIN. Do nothing if disabled
FTXBEGIN. Force processing if timer not running.
FTXBEGIN. Disable Tx Interrupts
FTIMR. Disable Tx Interrupts
ZCOM LEVEL1 Protocol
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 le
vel1.
ZCOM Monitor Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 mo
nitor
ZCOM Port Diagnostic Module
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 te
stpro
ZCOM Protocol Module Entry Point Table
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 pm
entta
ZCOM System Entry Point Table
ACC Rel B.02.40-B.2.40.02 for B.10.20 PHNE_22519 um
uxent
/opt/acc/z7200a/loopback.zmap:
ZCOM System Firmware (ROM) Rev 04.B 921106.1200
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 z
7200_
ZCOM System Software (WMUX1)
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 w
mux1.
ZCOM System Software (WMUX3)
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 w
mux3.
CPU clock 16MHz
ZCOM System Software (WMUX4)
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 w
mux4.
ZCOM LEVEL1 Protocol
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 l
evel1
ZCOM Monitor Module
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 m
onito
ZCOM Port Diagnostic Module
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 t
estpr
ZCOM Protocol Module Entry Point Table
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 p
mentt
ZCOM System Entry Point Table
ACC Rel B.02.40/B.02.40.01 for B.10.20 PHNE_16615 u
muxen
cksum(1) Output:
950671173 3976 /usr/conf/master.d/nacc
2276587332 2172 /opt/acc/share/man/man1.Z/zmasterd.1
4113486100 525 /usr/sam/lib/kc/paramsACC.tx
2303197461 295 /usr/sam/lib/kc/subsysACC.tx
1413496282 369 /usr/sam/lib/kc/driversACC.tx
2853717544 28731 /opt/acc/TEL/lib/libTELfmt.sl
2381368008 9336 /opt/acc/protocol/testprot.zrel
1244230868 173068 /usr/conf/lib/libnacc1_niosyms.o
2376563470 180760 /usr/conf/lib/libnacc1_pcisyms.o
2272368330 185940 /usr/conf/lib/libnacc_eisasyms.o
1922974547 171400 /usr/conf/lib/libnacc_niosyms.o
962887946 198820 /usr/conf/lib/libzcomsyms.o
2805633415 1256 /opt/acc/msg/default.txt
2348793103 32906 /opt/acc/bin/pmon
422297368 11482 /opt/acc/sys/wmux4.zrel
2390466435 123221 /opt/acc/bin/zdbi960
545910662 29945 /opt/acc/msg/def.zdbi960.txt
3634397512 3817 /opt/acc/share/man/man3.Z/zevent_rcvr.3x
4284640607 3448 /opt/acc/share/man/man3.Z/zset_rcvr.3x
4038427538 49123 /opt/acc/share/man/man3.Z/zconfig.3x
4086019893 4973 /opt/acc/msg/zerrmsg.txt
3756164227 5910 /opt/acc/include/zcom/zcomcall.h
3500346884 36927 /opt/acc/bin/nacc1_trc
3531369535 32831 /opt/acc/bin/nacc_trc
1329615096 32959 /opt/acc/bin/zmasterd
3820956845 20540 /opt/acc/bin/nacc1_stats
3876052922 24722 /opt/acc/bin/zmlog
776025718 2507 /opt/acc/msg/def.zmlog.txt
589639145 1997 /sbin/init.d/acc
2974354459 1116 /etc/rc.config.d/acc
993209107 191 /opt/acc/lbin/FixMajor.awk
3227614873 17044 /opt/acc/z7350a/loopback.zabs
376299850 2635 /opt/acc/z7350a/loopback.zmap
1329747964 8822 /opt/acc/protocol/level1.zrel
1860434810 6333 /opt/acc/msg/def.zcom.txt
2836329911 3761 /opt/acc/lbin/FixMajor
635763304 70241 /opt/acc/bin/zmon
3387430513 10455 /opt/acc/msg/def.zmon.txt
4099417872 160281 /opt/acc/bin/zmntr
968574347 45339 /opt/acc/bin/znode
2868950979 139852 /usr/conf/lib/libnacc_nio.a
1213515243 203608 /usr/conf/lib/libnacc_pci.a
1993447761 217244 /usr/conf/lib/libzcom.a
1949203782 18218 /opt/acc/z7400a/loopback.zabs
203754437 2570 /opt/acc/z7400a/loopback.zmap
2511310876 39326 /opt/acc/sys/z7350_fw.zrel
3508289665 42176 /opt/acc/sys/z7400_fw.zrel
3441120834 53476 /opt/acc/bin/ttgen
2205947814 57488 /opt/acc/bin/zscan
3207781022 33588 /opt/acc/msg/def.ttgen.txt
1056236874 15394 /opt/acc/msg/def.zscan.txt
3196247555 26740 /opt/acc/msg/zterm.hlp
1375215920 104504 /opt/acc/include/zcom/zcomsys.h
1375215920 104504 /usr/conf/acc/zcomsys.h
3701919438 139668 /opt/acc/bin/zterm
2538203156 27430 /opt/acc/sys/wmux3.zrel
1093109792 3042 /opt/acc/sys/wmux1.zrel
1553828708 18146 /opt/acc/z7200a/loopback.zabs
1879443941 3558 /opt/acc/z7200a/loopback.zmap
3603843962 2000954 /opt/acc/z7300a/download.zabs
1547469401 2153972 /opt/acc/z7330a/download.zabs
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_13990 PHNE_15350 PHNE_16615 PHNE_17877 PHNE_18716
Equivalent Patches: None
Patch Package Size: 7090 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 PHNE_22519
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHNE_22519.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHNE_22519. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHNE_22519.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_22519.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
Fixing a problem related to incorrect port mode
validation in ttgen, required adding new checking to
the ttgen program to verify the correctness of the port
modes in the ".answ" file. So some port mode and card
type combinations which you may have used up to now may
not be valid anymore. The following table shows the
allowable combinations:
Name Value 8 port 2 port 4 port
RS232 0 Good Good Bad
V35 1 Bad Good Bad
RS449 2 Bad Good Bad
V36 3 Bad Good Bad
RS422 4 Good Good Bad
E1DB9 5 Bad Bad Good
E1BNC 6 Bad Bad Good
T1RJ45 7 Bad Bad Good
LBACK 8 Good Good Good
E1RJ45 9 Bad Bad Good
T1DB9 10 Bad Bad Good
T1BNC 11 Bad Bad Good
X21 12 Good Good Bad
Refer to the latest Utilities documentation for information
on what is supported by the ttgen program.
-----End of Document ID: PHNE_22519------------------------------------------
Document ID: PHKL_23259
Date Loaded: 20010214
Title: s800 10.20 SCSI cumulative patch
Patch Name: PHKL_23259
Patch Description: s800 10.20 SCSI cumulative patch
Creation Date: 01/02/02
Post Date: 01/02/14
Hardware Platforms - OS Releases:
s800: 10.20
Products: N/A
Filesets:
OS-Core.CORE-KRN OS-Core.KERN-RUN ProgSupport.C-INC
Automatic Reboot?: Yes
Status: General Release
Critical:
Yes
PHKL_23259: PANIC HANG MEMORY_LEAK OTHER
The robotics LUN on a LVD/SE DDS4 Autoloader is not
discovered by ioscan when the autoloader is attached
to a HSC SE bus.
PHKL_22690: HANG
PHKL_22224: PANIC OTHER
ioscan fails to detect luns following a gap in the
lun numbering.
PHKL_21085: PANIC HANG
PHKL_20687: HANG
PHKL_19615: OTHER
ioscan output is affected.
LVM primary paths become unavailable.
ServiceGuard Tocs node.
PHKL_19131: PANIC
PHKL_19098: PANIC
PHKL_18959: HANG
PHKL_18391: HANG
PHKL_16927: PANIC
PHKL_17468: HANG
PHKL_16862: HANG
Path Name: /hp-ux_patches/s800/10.X/PHKL_23259
Symptoms:
PHKL_23259:
(SR: 8606130943 CR: JAGad00101)
There is no persistent tunable to manage the queue depth
for all the SCSI tagged devices on a system; therefore
queue depth changes are lost after reboots. (The queue
depth gives the number of maximum concurrent I/O's
allowed to the same device.)
The same scsi queue depth can be set for all tagged devices
but not on a per device basis.
(SR: 8606166545 CR: JAGad35832)
On a K-class or T-class machine with the HP-PB boards using
the scsi3 driver, some processes may hang and SCSI abort
messages will be found in the syslog file.
(SR: 8606166632 CR: JAGad35919)
The system reports unexpected I/O errors when the SCSI bus
resets during heavy I/O. The /var/adm/syslog/syslog.log
reports "SCSI: Request Timeout; Abort Tag...."
(SR: 8606166635 CR: JAGad35922)
A process may hang waiting for an I/O to complete, or there
may be a memory leak in the 512 byte bucket on 32bit kernels
and 1024 byte bucket on 64bit kernels. This may occur on any
kind of machine during regular use of the system.
(SR: 8606166643 CR: JAGad35930)
The sctl device driver was not designed to run on multiple
processors at the same time (i.e. MP safe). As a
consequence, all processes using the sctl device driver
will all run on the same processor in a multi-processor
system. CPU load distribution will be uneven and may lead,
in the worst cases, to severe degradation of performance.
(SR: 8606166656 CR: JAGad35943)
A data page fault panic from c720_timer may occur when the
system is running out of memory. SCSI aborts are likely to
be found in the syslog file. This panic may be seen on any
system experiencing memory pressure. The stack trace will
show:
c720_timer+0x6e4
invoke_callouts_for_self+0x238
sw_service+0x108
mp_ext_interrupt+0x394
ivti_patch_to_nop3+0x0
idle+0x3c4
swidle_exit+0x0
(SR: 8606166696 CR: JAGad35983)
Data page fault panic in LspToScratch(). This panic may
occur during regular use of the c720 driver. The stack
trace will end with:
LspToScratch+0x8
c720_isrSelect+0x38
c720_isrGuts+0x84c
c720_timer+0x668
invoke_callouts_for_self+0xc0
sw_service+0xb0
mp_ext_interrupt+0x144
(SR: 8606166733 CR: JAGad36020)
An "incomplete" field in an internal structure keeps track
of the number of I/O requests pending for a specific lun.
This field is not updated correctly. This could give false
information if HP support asks, during an investigation,
for the value of the field.
(SR: 8606166737 CR: JAGad36024)
The robotics LUN on a LVD/SE DDS4 Autoloader is not
discovered by ioscan when the autoloader is attached to
a HSC SE bus. The drive LUN is discovered and is attached
to stape correctly, but the robotics controller LUN doesn't
even come up as unclaimed.
(SR: 8606168866 CR: JAGad38144)
Disk I/O hangs even when LVM PV-Link is configured.
The system could report a "DIAGNOSTIC SYSTEM WARNING".
The on-line diagnostic log would show an I/O Error.
PHKL_18191:
When an odd-length record is read from a tape device that
supports wide transfer mode, an Unexpected Bus Free error
is incorrectly reported.
PHKL_22690:
(SR: 8606164094 CR: JAGad33395)
LVM requests to a Volume Group may hang instead of
switching to alternate link under certain disk failure
conditions.
PHKL_22224:
( SR: 8606136160 CR: JAGad05289 )
The QUEUE FULL handling has caused performance problems at
customer sites. Performance degradation will be seen during
accesses to a disk after a QUEUE FULL condition has been
received from the disk.
QUEUE FULL conditions (a transient I/O error) are logged
in syslog and can occur with any SCSI device on any HP-UX
platform.
( SR: 8606100450 CR: JAGab31847 )
ioscan will not discover devices (LUNs) that follow a
non-existent LUN on a given target. Ie. ioscan will only
currently find existent LUNs that are in sequential order
starting from LUN 0. Therefore, such "non-contiguous" LUNs
will not be seen by ioscan and will not be accessible to the
system. This behaviour had been seen with a EMC disk array,
but may exist with other devices.
( SR: 8606146079 CR: JAGad15415 )
A data page fault can occur due to a NULL pointer not
correctly checked. Although no specific stack trace can
be expected, ONE out of the five following functions
should appear near the top of the stack trace to suspect
that this specific problem has been hit:
c720_isrSelect()
c720_isrDataDone()
c720_isrExtMsgLenIn()
c720_isrWdtrRespRcvd()
c720_isrSdtrRespRcvd()
PHKL_21863:
( SR: 8606142756 CR: JAGad12108 )
Any wide SCSI devices attached to the built-in narrow
single-ended SCSI bus using a 50 pin to 68 pin cable will
not function properly. The description shown by ioscan
for the built-in narrow single-ended SCSI bus will
incorrectly show the bus as "Wide".
PHKL_21085:
( SR: 5003462986 CR: JAGab17250 )
A system with 2 ALT 8-series DLT (Quantum 4000) on the same
card showed the following panic:
panic: (display==0xb800, flags==0x0) Data page fault 1111
The stack trace was:
scsi_start+0x18
scsi_retry+0xd8
invoke_callouts+0x160
softclock+0x38
sw_service+0x154
mp_ext_interrupt+0x2a0
$RDB_int_patch+0x58
mpn_splx_free_lock_ul4_brn_target+0x4
net_callout+0x90
netisr_netisr+0x1bc
netisr_daemon+0x68
( SR: 8606114227 CR: JAGac23205 )
Pvlink switch does not occur if getting repeated bus resets
Has been seen on two system configurations with a shared
bus which is getting reset regularly.
The I/Os never time out and there is no switch to the
alternate link.
( SR: 8606105826 CR: JAGab74163 )
System experienced Spinlock Deadlock panic.
The panic string is:
panic: (display==0xb800, flags==0x0) Spinlock deadlock!
The stack shows the following:
panic+0x10
too_much_time+0x238
wait_for_lock_spinner+0x2f4
wait_for_lock_4way+0x2c
mpn_splx_retry+0x24
resume_cleanup+0x16c
resume+0x280
_swtch+0x138
real_sleep+0x234
_sleep+0x14
unhashdaemon+0xa4
main+0x59c
( SR: 8606127843 CR: JAGac78644 )
The SCSI retry policy introduced with PHKL_17467/8
is causing a problem. This policy ensured that an
INQUIRY command would be sent to the device after
a disk becomes nonresponsive.
The problem is that when the disk becomes responsive
again, the inquiry will return the old data instead of
the current information.
( SR: 8606132417 CR: JAGad01566 )
The SCSI log messages don't give the hardware path. To
decode the device, we must translate the 'dev:' field.
PHKL_20687:
( SR: 8606105212 CR: JAGab73159 )
SCSI hardware failure causes system hang with multiple
processes waiting for I/O return. LVM expects either
an I/O error or an EPOWERF (timeout) to continue.
Multiple console messages are generated which read:
SCSI: Third party detected bus hang --
lbolt: xxxxxxxx, bus: x
PHKL_19615:
DTS# JAGab70055 SR# 8606103392
The command "ioscan -kfn" displays erroneous output
with the patch PHKL_19131. A fast wide differential
disk may be incorrectly reported as narrow single-
ended under description column in the ioscan output.
DTS# JAGab71209 SR# 8606103998
Suppose a diskarray is hooked up via Fibre Channel with the
primary paths through mux1 and the alternate paths through
mux2. If mux1 is powerfailed, LVM fails over to the
alternate paths, but when mux1 is powered back up, the
primary paths are still unavailable.
DTS# JAGab41088 SR# 8606101027
ServiceGuard package TOCs node because cluster lock ioctls
take too long to complete.
PHKL_19131:
DTS#: JAGaa42584 SR#: 1653281824
System panic with "scsi unrecovered deferred error"
DTS#: JAGaa44446 SR#: 8606101359
command-mode might stop working at any arbitrary time with
respect to the application and device trying to use it.
DTS#: JAGaa08513 SR#: 8606101473
While doing an Inquiry command to request Unit Serial Number
Page, one extra byte is transfered. There are no real
symptoms associated with this problem.
PHKL_19098:
System panics (Date Page Fault) in scsi_start_bus_locked()
PHKL_18959:
LVM hangs due to I/O requests never being returned by the
IO subsystem. The message "Device violation of Contingent
Allegiance" is issued to syslog.
PHKL_18391:
( SR: 1653300004 DTS: JAGaa47696, dup of JAGaa11155 )
Slow PVlink failover after installing PHKL_17468.
Diskinfo reports back on an unavailable disk.
( SR: 1653300970 DTS: JAGab11365 )
( SR: 1653290395 DTS: JAGaa47016 )
A faulty disk can prevent LVM mirroring from working.
PHKL_16927:
( SR: 5003434118 DTS: JAGaa23967 )
System panics (Data Page Fault) in scsi_destroy_scb
( SR: 5003429654 DTS: JAGaa40369 )
System panics in c720_invalid_req_done
( SR: 4701407890 DTS: JAGaa23080 )
Unexpected Disconnect Messages when using pass through
driver
PHKL_17468:
I/O failover hang on Fiber Channel PV_link.
PHKL_16862:
I/O failover hang on Fiber Channel PV_link.
Defect Description:
PHKL_23259:
(SR: 8606130943 CR: JAGad00101)
The current architecture allows the queue depth to be set
by ioctl(). The value is not retained across reboots.
There is no mechanism available to set the scsi queue
depth tunable on a particular device.
Resolution:
The driver code was enhanced to provide the two following
features:
The tag queue depth will now be controlled by a tunable
value (scsi_max_qdepth) which will not be lost after
reboots.
A new ioctl interface is provided for setting the scsi
queue depth tunable for a particular device. However,
this change takes effect on subsequent device opens.
The scsictl command is used to set the scsi queue depth
tunable on a device. The queue depth defaults to the
value of the global tunable "scsi_queue_depth" unless
overridden by the scsictl command.
(SR: 8606166545 CR: JAGad35832)
During a regular use of a system, a request can be aborted.
When the abort is issued, if the controller returns an
error, the expected behavior is to resend the original
request. The active request needs to be initialized before
processing the I/O. In the current design, the request is
left untouched and therefore is not retried.
Resolution:
The active request that returned with an error is assigned
to NULL and is placed back on the request queue so that it
can be correctly resent.
(SR: 8606166632 CR: JAGad35919)
The kernel did improper clean up in an abort condition.
A SCSI script MOVE instruction is patched in the cmd_setup
procedure in case of an abort to an INT instruction. The
instruction is not restored to MOVE in the cleanup of
Abort.
Resolution:
The MOVE instruction is restored in the c720_cleanup_ABORT
procedure. This ensures that c720_start finds the command
bytes.
(SR: 8606166635 CR: JAGad35922)
A buffer structure can get lost during heavy use of the
SCSI driver. Scsi_sp_start() does a dequeue of a buffer
from lp->special_scb_q queue and then tries to allocate a
SCSI control block (SCB). If the SCB allocation fails, the
routine simply returns and the buffer is not enqueued back.
This causes scsi_iowait() to wait forever, and the process
will hang. This also causes the buffer to be lost,
resulting in a memory leak.
Resolution:
The fix is to enqueue the buffer back to the head of the
queue if the SCB memory allocation fails in
scsi_sp_start().
(SR: 8606166643 CR: JAGad35930)
The sctl device driver's original design was not MP safe.
If an application makes heavy use of the driver, the code
is forced to execute on the same CPU. All processes using
the driver will accumulate on the same processor.
Resolution:
The necessary code to make the driver MP safe has been
added into the driver.
(SR: 8606166656 CR: JAGad35943)
Memory was not available for error handling. The system
paniced because the kernel failed to preallocate memory
for its sense data. Due to this failure a piece of
code which sets the owner of the bus is skipped.
Resolution:
The fix is to do a dma setup during the opening of the bus.
The sense buffer is preallocated to ensure there is memory
available for the autosense.
(SR: 8606166696 CR: JAGad35983)
Some c720 driver information can be lost while trying to
recover from a non-responding device.
Resolution:
The c720_chip_hang() call may reset the value of lbp->owner
to NULL in some cases. If the lbp->owner is used after the
call it causes a panic. To avoid this panic, we cache this
information before calling the function.
(SR: 8606166733 CR: JAGad36020)
The "incomplete" field is not decremented properly and
may have incorrect information.
Resolution:
The "incomplete" field is correctly updated.
(SR: 8606166737 CR: JAGad36024)
The scsi_is_multilun() is hardcoded with various tape
devices, the list for which does not include this
particular device.
Resolution:
DDS4 autochangers are taken into account in the code
managing multilun devices.
(SR: 8606168866 CR: JAGad38144)
LVM requests were retried indefinitely when an invalid
driver-internal status was returned.
Resolution:
The LVM requests are not retried indefinitely when an
invalid driver-internal status is returned, instead
an error is returned to LVM after retrying in the
SCSI layer for the maximum number of attempts.
PHKL_18191:
The HP-PB FW SCSI Adapter expected a specific sequence of
interactions by the driver when handling this event.
Resolution:
Change the sequence of interactions to that expected by
the card.
PHKL_22690:
(SR: 8606164094 CR: JAGad33395)
When a powerfail condition occurs, the LVM requests are
queued to the Powerfail queue and the lvmkd deamon will
attempt to test the links by sending a SCSI_INQUIRY request
to each link. If a device returns SCTL_INCOMPLETE, the scsi
code will retry the SCSI_INQUIRY every 2 seconds until the
inquiry is successful. If the inquiry is never successful,
the scsi driver will never return to the lvmkd; the
powerfail recovery will hang rather than timing out and
switching to the alternate link. Analyzing the dump will
show the lvmkd with the following stack trace:
_swtch+0x138 real_sleep+0x234 _sleep+0x14
scsi_sleep+0x34 scsi_iowait+0x54 scsi_cmdx+0x20c
scsi_cmd+0x3c scsi_init_inquiry_data+0xe4
scsi_ioctl+0x1024 sdisk_ioctl+0x28
lv_check_dev_accessability+0x134 lv_bufio+0x23c
lv_test_a_link+0x8c lv_check_pf_pvs+0x3a0
lvmkd_daemon+0xd4 lvmkd_fork+0xa0 lvmkd_init+0x1c
main+0x870 $vstart+0x34 $locore+0x74
Resolution:
On SCSI_INQUIRY done through the sdisk_ioctl path where
the device returns SCTL_INCOMPLETE, the inquiry request
will be retried every 2 seconds, with a maximum of
5 retries. If the inquiry request is not completed after
5 retries, an error is returned to LVM.
PHKL_22224:
( SR: 8606136160 CR: JAGad05289 )
A QUEUE FULL condition is an error reported by a SCSI
device which indicates that the device has reached the
limit of the number of I/Os that it can process
concurrently and that the rejected I/O request must be
retried later. The defect that caused a performance
problem was that we effectively turned the queue
depth down to 1 and never raised it back again.
Resolution:
After a QUEUE FULL, we'll wait for any outstanding I/Os
to complete and gradually increase the queue depth back
up to the previous max queue depth in such a way as to
minimize the likelihood of another immediate QUEUE FULL
condition.
( SR: 8606100450 CR: JAGab31847 )
The ioscan algorithm comes from old SCSI-2 design
paradigms which are no longer valid. In the old paradigm
we only scanned each target until we found an invalid
LUN, which caused us to miss seeing certain LUNs in
the newer SCSI device paradigms.
Resolution:
A redesign of scsi_probe() has been done which allows
ioscan to discover all existing devices. There are not
expected to be any increased ioscan times.
( SR: 8606146079 CR: JAGad15415 )
We did not check the value of a pointer before
dereferencing it. When the pointer was NULL the system
paniced. The pointer can be NULL for a variety of
corner-case reasons in the operation of the driver,
and thus checking for NULL should have been done and
was not.
Resolution:
We now check the value of the pointer before dereferencing
it. If NULL, we dump the contents of the SCSI I/O card
registers to the syslog and continue processing.
PHKL_21863:
( SR: 8606142756 CR: JAGad12108 )
The built-in narrow single-ended SCSI bus on workstation
models J5600 and C3600 is incorrectly setup as a wide bus.
Resolution:
The model numbers J5600 and C3600 were added to conditionals
in the c720_init() and c720_pci_attach() routines.
PHKL_21085:
( SR: 5003462986 CR: JAGab17250 )
The panic occurs because the requested target pointer had
been freed and the lun structure is no longer valid.
The scsi_retry() walks through the per-bus retry
queue. During its work, only the per bus lock is held.
For the restart of I/O, scsi_start() is used which needs
to hold the bus lock (for ordering reasons) which is so
released. But during the time that the bus lock is released
the state can change.
Resolution:
Instead of requeuing directly to the tag_q, scsi_retry()
queues the timed-out requests to a temporary queue.
This prevents them from being processed and started until
the bus lock is re-acquiered at which point the requests
are requeued from the temporary queue to the tag_q.
( SR: 8606114227 CR: JAGac23205 )
The hang is due to infinite retry at the scsi layer without
being passed to LVM to try to allow the timeout and switch
the link
Resolution:
The fix was to change the callback routine from sd_retry()
to sd_retry_check(), which checks the B_PFTIMEOUT flag and
calls sd_nonresponse() if it is set instead of calling
sd_retry().
( SR: 8606105826 CR: JAGab74163 )
The spinlock deadlock occurred because one processor owns
the SPL lock which some other processor wants. The problem
is due to a bus lock given instead of the lun lock wanted.
The real problem is that the lun and bus locks were
locked in a different order in two places of the code.
Resolution:
The locks were correctly reordered in sd_dump_queue().
( SR: 8606127843 CR: JAGac78644 )
The inquiry data are buffered and the inquiry command was
sent directly to the disk only under special circumstances
causing invalid data to be returned.
Resolution:
The inquiry command is always sent to the disk to get
current data.
( SR: 8606132417 CR: JAGad01566 )
Change the scsi_dmesg_log_io function so that the hardware
path is visible without decoding the 'dev:' field
Resolution:
Use the translation functions to add the hardware path
to the logged information.
PHKL_20687:
( SR: 8606105212 CR: JAGab73159 )
SCSI driver detects hardware failure and resets the bus.
However, the reset operation cannot resolve the bus hang
and the reset interrupt never occurs. Without a bus reset
timeout, the processes hang waiting for I/O's queued for
the bus.
Resolution:
Added code to timeout unsuccessful bus reset, abort the
I/O and return an EPOWERF to the upper layer.
PHKL_19615:
DTS# JAGab70055 SR#: 8606103392
PHKL_19131 affects disk representation in ioscan output.
This problem happens due to A class system firmware
returning 4 words of info in response to a GET_INITIATOR PDC
call instead of 6 words and the 5th and 6th words are zeroed
out. Driver misinterpreted these zero values for the 5th
and 6th words and assumed that the firmware wanted it to
configure the SCSI card as Narrow Single Ended card.
Resolution:
The driver now expects 4 or 6 bytes from a call to
GET_INITIATOR depending on the type of the machine.
This has fixed the problem.
DTS#JAGab71209 8606103998
The root cause of the problem is bit collision between
definition of the flags L_EPOWERF and L_DEFERRED_ERROR.
Resolution:
As a resolution the flag L_DEFERRED_ERROR is redefined
with a different value.
DTS# JAGab41088 SR# 8606101027
ServiceGuard TOCs node because cluster lock ioctls take
too long. This occurs with 10.20 of HP-UX and 10.10 of
ServiceGuard.
The root cause of the problem is that the sdisk driver
responds with cached data when an SIOC_INQUIRY ioctl is
issued for an open device. This defeats LVM's attempt to
determine if the either the device or the path to it have
failed before issuing IO requests to acquire the cluster
lock. When the IO request is subsequently issued, the
improved error handling recently reintroduced to the sdisk
driver now results in several retries being attempted before
the error is reported back to LVM. This does not allow LVM
sufficient time to switch to the mirror disk or alternate
path and successfully complete the operation before
ServiceGuard TOCs the machine.
Resolution:
The resolution to this problem is to make all
SCSI inquiries go out to the device rather than
read the data cached in memory.
PHKL_19131:
DTS#: JAGaa42584 SR#: 1653281824
If immediate reporting is enabled and a deferred error
occurs, the system will panic with "scsi unrecovered
deferred error".
Resolution:
The new deferred error check/handling method is to block
all IO requests for the disk, when a deferred error occurs,
until the device is closed and reopened.
DTS#: JAGaa44446 SR#: 8606101359
scsi_ctl replaces the cdevsw table entries for d_read and
d_write when the lun is not in command-mode for performance
improvements. The problem is that the cdevsw table is a
global resource and is not owned by a lun and command-mode
might stop working at any arbitrary time.
Resolution:
Removed that code.
DTS#: JAGaa08513 SR#: 8606101473
the FC data length exceeds the maximum SCSI transfer length
by 1 byte while performing an Unit Serial Number Page.
Resolution:
Reduce the size of the scsi serial structure by 1.
PHKL_19098:
When sd_open() fails in scsi_lun_open, we goto recover_lck1
which falls through to recover_lp. recover_lp sets lp->ddsw
to NULL but fails to set lp->scb_q_nonempty to NULL. This
causes a data page fault panic in scsi_start_bus_locked().
This might occur when an open() fails on a busy device.
Resolution:
Set lp->scb_q_nonempty to NULL in label recover_lp in
scsi_lun_open().
PHKL_18959:
When the message is issued (typically caused by a bus
RESET during contingent allegiance condition (CAC)), the
corresponding I/O request is then lost and never returned
to the requestor, eventually causing a system hang.
Resolution:
When a bus RESET happens during a CAC, the c720 driver now
insures that all currently active I/O requests are posted
as incomplete and scheduled to be retried.
PHKL_18391:
( SR: 1653300004 DTS: JAGaa47696, dup of JAGaa11155 )
Slow PVlink failover or diskinfo reporting good disk status
on an unavailable disk is due to the SCSI INQUIRY command
returning cached data instead of sending the command down to
the device."
Resolution:
We now ensure an INQUIRY command will be sent down to the
device when the disk becomes nonresponsive.
( SR: 1653300970 DTS: JAGab11365 )
( SR: 1653290395 DTS: JAGaa47016 )
If a faulty disk sends NOT_READY sense key to SCSI. The
current SCSI policy is to retry the request until the disk
is ready. This results in a hang IO situation and prevents
the LVM mirroring from working.
Resolution:
LVM-related NOT_READY requests will be treated as
nonresponse from the disk and will therefore be failed back
for LVM to handle.
PHKL_16927:
( SR: 5003434118 DTS: JAGaa23967 )
There is a race condition between scsi_lun_open and
scsi_start_bus_locked. This can be fixed by incrementing
the in_use counter before releasing the lun lock therefore
insuring the lun stay open.
( SR: 5003429654 DTS: JAGaa40369 )
In c720_invalid_req_done, we directly dereference scb->busp
without assuring that this scb is a bus scb. The busp
pointer is NULL if the scb is a lun scb. Thus, the fix is
to add a check to see whether lsp->scb->busp is NULL, if so,
obtain the busp from lsp->scb->lp->bus instead.
( SR: 4701407890 DTS: JAGaa23080 )
When using the pass through driver with the "inhibit Inquiry
on open" option (see scsi_ctl(7)) and a device on a SCSI bus
with no other devices and repeatedly opening and closing the
device to send but a single SCSI command, the bus is
sometimes in the wrong state when the target device begins
to transfer data.
PHKL_17468:
In a hardware configuration, mirrored disks can be accessed
through primary/alternate Fiber Channel (FC) links. If the
primary link and the alternate link of a disk of the
mirrored pairs are down, the other disk should continue to
sending or receiving data. The problem is it fails to do
so and causes an I/O hang.
This patch provides fix for this hang problem. The SCSI
layer will retry the FC requests as long as the PFTIMEOUT
period has not expired and the request is recoverable.
PHKL_16862:
In a hardware configuration, mirrored disks can be accessed
through primary/alternate Fiber Channel (FC) links. If the
primary link and the alternate link of a disk of the
mirrored pairs are down, the other disk should continue to
sending or receiving data. The problem is it fails to do
so and causes an I/O hang.
This patch will provide a temporary fix for this problem.
In this fix, the SCSI layer will retry the FC request as
long as the FC sets a flag to ask for retrying the
request.
SR:
1653281824 1653290395 1653300004 1653300970 1653306654
4701407668 4701407890 4701414136 5003425298 5003429654
5003434118 5003462986 5003464297 8606100450 8606101027
8606103392 8606103998 8606105212 8606105826 8606114227
8606127843 8606130943 8606166545 8606166632 8606166635
8606166643 8606166656 8606166696 8606166733 8606166737
8606168866 8606132417 8606136160 8606142756 8606146079
8606164094
Patch Files:
/usr/conf/lib/libhp-ux.a(disc3.o)
/usr/conf/lib/libhp-ux.a(scsi3.o)
/usr/conf/lib/libhp-ux.a(scsi_c720.o)
/usr/conf/lib/libhp-ux.a(scsi_ctl.o)
/usr/conf/lib/libhp-ux.a(scsi_disk.o)
/usr/conf/master.d/scsi-disk
/usr/conf/space.h.d/scsi-disk.h
/usr/include/sys/scsi_ctl.h
what(1) Output:
/usr/conf/lib/libhp-ux.a(disc3.o):
disc3.c $Date: 2001/01/31 18:09:03 $ $Revision: 1.18
.98.23 $ PATCH_10.20 (PHKL_23259)
/usr/conf/lib/libhp-ux.a(scsi3.o):
scsi3.c $Date: 2001/01/31 18:17:47 $ $Revision: 1.10
.98.46 $ PATCH_10.20 (PHKL_23259)
/usr/conf/lib/libhp-ux.a(scsi_c720.o):
scsi_c720.c $Date: 2001/01/31 18:18:55 $ $Revision
: 1.5.98.53 $ PATCH_10.20 (PHKL_23259)
scsi_c720.c $Date: 2001/01/31 18:18:55 $ $Revision:
1.5.98.53 $
/usr/conf/lib/libhp-ux.a(scsi_ctl.o):
scsi_ctl.c $Date: 2001/01/31 18:19:55 $ $Revision:
1.9.98.49 $ PATCH_10.20 (PHKL_23259)
/usr/conf/lib/libhp-ux.a(scsi_disk.o):
scsi_disk.c $Date: 2001/01/31 18:20:29 $ $Revision
: 1.7.98.43 $ PATCH_10.20 (PHKL_23259)
/usr/conf/master.d/scsi-disk:
scsi-disk $Date: 2001/01/31 18:22:49 $ $Revision: 1.
1.98.3 $ PATCH_10.20 (PHKL_23259)
/usr/conf/space.h.d/scsi-disk.h:
scsi-disk.h $Date: 2001/01/31 18:22:13 $ $Revision:
1.1.98.3 $ PATCH_10.20 (PHKL_23259)
/usr/include/sys/scsi_ctl.h:
scsi_ctl.h $Date: 2001/01/31 18:21:30 $ $Revision: 1
.8.98.15 $ PATCH_10.20 (PHKL_23259)
cksum(1) Output:
3942978859 25812 /usr/conf/lib/libhp-ux.a(disc3.o)
4169487164 79584 /usr/conf/lib/libhp-ux.a(scsi3.o)
3967119990 99080 /usr/conf/lib/libhp-ux.a(scsi_c720.o)
482082418 70776 /usr/conf/lib/libhp-ux.a(scsi_ctl.o)
388393171 21780 /usr/conf/lib/libhp-ux.a(scsi_disk.o)
3847202969 673 /usr/conf/master.d/scsi-disk
73497796 1178 /usr/conf/space.h.d/scsi-disk.h
1170670221 52788 /usr/include/sys/scsi_ctl.h
Patch Conflicts: None
Patch Dependencies:
s800: 10.20: PHKL_16751
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHKL_16862 PHKL_16927 PHKL_17468 PHKL_18191 PHKL_18391 PHKL_18959
PHKL_19098 PHKL_19131 PHKL_19615 PHKL_20687 PHKL_21085 PHKL_21863
PHKL_22224 PHKL_22690
Equivalent Patches:
PHKL_23258:
s700: 10.20
Patch Package Size: 420 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_23259
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHKL_23259.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHKL_23259. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHKL_23259.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHKL_23259.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions:
This patch depends on base patch PHKL_16751.
For successful installation, please ensure that PHKL_16751
is in the same depot with this patch, or PHKL_16751 is
already installed.
-----End of Document ID: PHKL_23259------------------------------------------
Document ID: PHCO_23353
Date Loaded: 20010213
Title: s700_800 10.24 (VVOS) ex(1),vi(1),expreserve(1) patch
Patch Name: PHCO_23353
Patch Description: s700_800 10.24 (VVOS) ex(1),vi(1),expreserve(1) patch
Creation Date: 01/02/09
Post Date: 01/02/13
Hardware Platforms - OS Releases:
s700: 10.24
s800: 10.24
Products: N/A
Filesets:
TextEditors.EDITORS
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHCO_23353
Symptoms:
PHCO_23353:
Ported HP-UX patch PHCO_22228 to VVOS. The notes for HP-UX
patch PHCO_8654 states that the permissions on expreserve
should be 0555. The permissions are different on a VVOS
system.
Based on HP-UX patch PHCO_22228:
1. exrecover(1) functionality corrected.
2. vi(1) cannot handle tags longer than 30 characters.
3. vi(1) is not matching the patterns correctly in case
of multi-byte locales.
4. vi(1) does not handle window size change signal
(SIGWINCH) in case of piped commands.
5. Line number information was not being reset whenever
a fresh file was being opened after alternation
between files for e# command.
Based on HP-UX patch PHCO_13667:
1. Incomplete fix in PHCO_12335. Word anchoring in
global substitution not handled correctly. vi fails
for the specific case - g/\<global\>/s//globals/g
2. vi command reports incorrect number of characters
for multibyte locales.
Based on HP-UX patch PHCO_12335:
1. End of Word anchoring (\>) in substitution
causes a loss of punctuation and white space.
Based on HP-UX patch PHCO_11678:
1. %s/\<ow_\([0-9]\)\>/xx_\1/g does not work.
Based on HP-UX patch PHCO_9490:
1. Begin of Word anchoring (\<) under a global
substitution causes an unexpected truncation of
the string.
2. End of Word anchoring (\>) in substitution
causes a loss of punctuation and white space.
Based on HP-UX patch PHCO_8654:
Permission of /usr/lib/expreserve should be 0555.
PHCO_12305:
A non privileged user does not receive local mail
notifications when the user's vi session is killed or
terminated unexpectedly.
Defect Description:
PHCO_23353:
Ported HP-UX patch PHCO_22228 to VVOS. The notes for HP-UX
patch PHCO_8654 states that the permissions on expreserve
should be 0555. The permissions are different on a VVOS
system.
Based on HP-UX patch PHCO_22228:
1. exrecover(1) functionality corrected.
Resolution:
Code has been modified to take care of this issue.
2. vi(1) cannot handle tags longer than 30 characters.
Resolution:
Now the code is modified to handle the tags longer
than 30 characters.
3. vi(1) is not matching the patterns correctly in case
of multi-byte locales, because vi(1) is not
substituting the newline in a multi-byte locale.
Resolution:
The code has been modified to take care of the
newline substitution in case of multi-byte locales.
4. The signal handler for "SIGWINCH" was not activated
for piped commands to vi(1).
Resolution:
Now the code is modified to take care of signal handler
for SIGWINCH while piping.
5. The vi(1) behaves differently between 9.X and 10.X
because line number information was not being reset
whenever a fresh file was being opened after alternation
between files .
Resolution:
Now the code has been modified to reset the line number
information properly when a fresh file was being opened
after alternation between files.
Based on HP-UX patch PHCO_13667:
1. Incomplete fix in PHCO_12335. Word anchoring in
global substitution causes a loss of punctuation
and white space. vi fails for the specific case
- g/\<global\>/s//globals/g
2. vi command reports incorrect number of characters
for multibyte locales. vi used to report the number of
bytes instead of the number of characters in the file.
Based on HP-UX patch PHCO_12335:
vi does not recognize that ";" does not belong to a word.
Based on HP-UX patch PHCO_11678:
The PHCO_9490 version of ex(1) translates incorrectly.
Based on HP-UX patch PHCO_9490:
Since 10.01, vi(1)/ex(1) fails to correctly
interpret/process \< and \> in substitute
commands. This worked OK in 9.04.
Based on HP-UX patch PHCO_8654:
Permission of /usr/lib/expreserve should be 0555.
PHCO_12305:
When a non privileged user's vi session is terminated
unexpectedly, the user does not receive mail notifying
the user that a copy of the editor session was saved and
can be retrieved by using the 'recover' command of vi.
SR:
8606156264 8606100309 4701385112 1653249524 1653280651
1653251314 1653240234 4701379339 5003398289 1653213132
1653201574 1653181115 4701329391 4701365619
Patch Files:
/usr/bin/e
/usr/bin/edit
/usr/bin/ex
/usr/bin/vedit
/usr/bin/vi
/usr/bin/view
/usr/lib/nls/msg/C/exrecover.cat
/usr/lbin/exrecover
/usr/lbin/expreserve
/etc/auth/system/files.fcdb/05.patches/PHCO12305.fcdb
what(1) Output:
/usr/bin/e:
$Revision: 78.2.1.21 $ 32-bit NLS $
PATCH_10_20: hpux_rel.o ex.o ex_addr.o ex_cmds.o ex_
cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex
_get.o ex_io.o ex_put.o ex_re.o ex_rldata.o
ex_set.o ex_subr.o ex_temp.o ex_tty.o ex_uni
x.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex
_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_
vput.o ex_vwind.o printf.o bcopy.o ex_crypt.
o 01/01/24
/usr/bin/edit:
$Revision: 78.2.1.21 $ 32-bit NLS $
PATCH_10_20: hpux_rel.o ex.o ex_addr.o ex_cmds.o ex_
cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex
_get.o ex_io.o ex_put.o ex_re.o ex_rldata.o
ex_set.o ex_subr.o ex_temp.o ex_tty.o ex_uni
x.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex
_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_
vput.o ex_vwind.o printf.o bcopy.o ex_crypt.
o 01/01/24
/usr/bin/ex:
$Revision: 78.2.1.21 $ 32-bit NLS $
PATCH_10_20: hpux_rel.o ex.o ex_addr.o ex_cmds.o ex_
cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex
_get.o ex_io.o ex_put.o ex_re.o ex_rldata.o
ex_set.o ex_subr.o ex_temp.o ex_tty.o ex_uni
x.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex
_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_
vput.o ex_vwind.o printf.o bcopy.o ex_crypt.
o 01/01/24
/usr/bin/vedit:
$Revision: 78.2.1.21 $ 32-bit NLS $
PATCH_10_20: hpux_rel.o ex.o ex_addr.o ex_cmds.o ex_
cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex
_get.o ex_io.o ex_put.o ex_re.o ex_rldata.o
ex_set.o ex_subr.o ex_temp.o ex_tty.o ex_uni
x.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex
_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_
vput.o ex_vwind.o printf.o bcopy.o ex_crypt.
o 01/01/24
/usr/bin/vi:
$Revision: 78.2.1.21 $ 32-bit NLS $
PATCH_10_20: hpux_rel.o ex.o ex_addr.o ex_cmds.o ex_
cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex
_get.o ex_io.o ex_put.o ex_re.o ex_rldata.o
ex_set.o ex_subr.o ex_temp.o ex_tty.o ex_uni
x.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex
_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_
vput.o ex_vwind.o printf.o bcopy.o ex_crypt.
o 01/01/24
/usr/bin/view:
$Revision: 78.2.1.21 $ 32-bit NLS $
PATCH_10_20: hpux_rel.o ex.o ex_addr.o ex_cmds.o ex_
cmds2.o ex_cmdsub.o ex_data.o ex_extern.o ex
_get.o ex_io.o ex_put.o ex_re.o ex_rldata.o
ex_set.o ex_subr.o ex_temp.o ex_tty.o ex_uni
x.o ex_v.o ex_vadj.o ex_vget.o ex_vmain.o ex
_voper.o ex_vops.o ex_vops2.o ex_vops3.o ex_
vput.o ex_vwind.o printf.o bcopy.o ex_crypt.
o 01/01/24
/usr/lib/nls/msg/C/exrecover.cat:
None
/usr/lbin/exrecover:
$Revision: 78.2.1.21 $ 32-bit NLS $
$Revision: 76.2.2.1 $
PATCH_10_20: hpux_rel.o exrecover.o ex_extern.o 01/0
1/24
/usr/lbin/expreserve:
$Revision: Hewlett-Packard ISSL Level vvos_davis40 $
$Header: Hewlett-Packard ISSL Release vvos_
davis $ $Date: Fri Feb 9 20:43:46 EST 2001
$
$Revision: 78.2.1.21 $ 32-bit NLS $
cmd/ex/expreserve.c, hpuxcmdfs, vvos_davis, davis176
$Date: 01/02/09 21:00:01 $ $Revision: 1.12
PATCH_10.24 (PHCO_23353) $
$Revision: 76.2 $
/etc/auth/system/files.fcdb/05.patches/PHCO12305.fcdb:
$Revision: Hewlett-Packard ISSL 1.1 etc/auth/system/
files.fcdb/05.patches/PHCO12305.fcdb, hpuxcm
dfs, vvos_davis, davis175 $ $Date: 97/09/08
16:24:05 $
etc/auth/system/files.fcdb/05.patches/PHCO12305.fcdb
, hpuxcmdfs, vvos_davis, davis175 $Date: 01/
02/09 16:21:41 $ $Revision: 1.1 PATCH_10.24
(PHCO_12305) $
cksum(1) Output:
408415990 237568 /usr/bin/e
408415990 237568 /usr/bin/edit
408415990 237568 /usr/bin/ex
408415990 237568 /usr/bin/vedit
408415990 237568 /usr/bin/vi
408415990 237568 /usr/bin/view
3071133312 558 /usr/lib/nls/msg/C/exrecover.cat
1038296614 20480 /usr/lbin/exrecover
2213825864 20480 /usr/lbin/expreserve
1764124143 737 /etc/auth/system/files.fcdb/05.patches/
PHCO12305.fcdb
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHCO_12305
Equivalent Patches:
PHCO_22229:
s700: 11.00
s800: 11.00
PHCO_23354:
s700: 11.04
s800: 11.04
PHCO_22228:
s700: 10.20
s800: 10.20
PHCO_22848:
s700: 10.10
s800: 10.10
PHCO_22849:
s700: 10.01
s800: 10.01
Patch Package Size: 340 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_23353
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHCO_23353.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHCO_23353. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHCO_23353.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHCO_23353.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHCO_23353------------------------------------------
Document ID: PHNE_20748
Date Loaded: 20010212
Title: s700_800 10.20 remote network commands cumulative patch
Patch Name: PHNE_20748
Patch Description: s700_800 10.20 remote network commands cumulative patch
Creation Date: 01/01/23
Post Date: 01/02/12
Hardware Platforms - OS Releases:
s700: 10.20
s800: 10.20
Products: N/A
Filesets:
InternetSrvcs.INETSVCS-RUN
Automatic Reboot?: No
Status: General Release
Critical: No
Path Name: /hp-ux_patches/s700_800/10.X/PHNE_20748
Symptoms:
PHNE_20748:
1. JAGab73645/SR 8606105517:
Both remsh and remshd are hanging when a remote process
is started through remsh.
2. JAGab21137/SR 5003458414:
ER - remshd and rexecd are not updating the
"/var/adm/wtmp" and "/var/adm/btmp" files.
3. JAGab31733/SR 5003467134:
When "-pr" option is set, rcp fails to copy some of the
files present in the source directory under some
conditions.
4. JAGaa42962/SR 8606140969:
When rcp is used with wild card characters it fails to
create the first subdirectory when it is not existing at
the target machine.
5. JAGab83643/SR 8606110892:
rdist fails to handle the hard links properly.
6. JAGad15036/SR 8606145700:
remshd/rexecd is sometimes failing to display the error
message while executing a bad command when the user is in
ksh.
7. JAGad06606/SR 8606137488:
ruptime was showing ??:?? for the number of days when
the host was up or down for more than 365 days.
8. JAGad28199/SR 8606158870:
rlogind is intermittently failing to log syslog messages
for passwd entry timeouts and for failure in login
attempt.
9. JAGad28443/SR 8606159114:
rdist is not creating regular files properly.
10.JAGad36477/SR 8606167191:
rdist is not always handling source and destination path
properly.
PHNE_13619:
rlogin
* rlogin does not handle LANG environment variable
properly.
rlogind
* rlogind does not handle long hostname.
remsh
* ER - remsh with stderr closed returns "fd = 2".
* remsh does not handle LANG environment variable
properly.
remshd
* remshd does not update login counters properly.
* PHNE_12161: remshd and rexecd patch does
not work with large UID/GIDs.
* rexecd does not update trusted systems DB on
good logins.
rcp
* rcp does not clear old errno value.
* SR: RCP may show file as being there even if it ran
out of disk space.
* rcp does not check for proper parameters.
* rcp does not handle LANG environment variable properly.
rdist
* rdist does not check for temporary files before
creating them.
* rdist does not set process resources properly.
* rdist does not process distfile properly.
* rdist fails if subdirectory exists that matches
remote hostname.
PHNE_12161:
* The lockout feature of trusted systems does not work
with rexec.
PHNE_11728:
* Certain signals cause rlogin to dump core.
* Change in rlogind logging. Timeout login events
no longer logged.
PHNE_10638:
* rlogin dies intermittently due to signal "SIGUSR1".
PHNE_9787:
* RCP on a NFS system displays the error message
rcp : can't truncate....Permission denied with NFS.
PHNE_9219:
* RDIST allows copy of certain files without
the required permission.
PHNE_8889:
* remsh/rexec do not force user to change expired
password if it is null.
PHNE_8807:
* Environment variable TERM overflow in rlogin.
* Time stamp of rlogind's log message for login failure
is set to EST/EDT.
* Connection closes when any child process of rlogind
receives a SIGSTOP.
PHNE_7920:
* RDIST cannot transfer files greater than 2 Giga
bytes. An enhancement request exists for RDIST to
be able to handle files greater than 2 Giga bytes
in size.
* A bug was found in RDIST which can allow an
unprivileged local user to gain unauthorized access.
This patch fixes the bug.
PHNE_7918:
* RCP cannot transfer files greater than 2 Giga bytes. An
enhancement request exists for RCP to be able to handle
files greater than 2 Giga bytes in size.
PHNE_6815:
* Changed the default pathname to include /usr/local/bin
and /usr/contrib/bin as per HP-UX 9.x.
Defect Description:
PHNE_20748:
1. JAGab73645/SR 8606105517:
In remshd, the SIGCHLD signal is not handled properly. It
is currently relying on the EOF from the pipe which is
used to send error messages from the child to the parent
process in remshd. Because of this, remshd is hanging in
some cases and as a result remsh is also hanging.
Resolution:
A new signal handler for SIGCHLD has been added which,
for remshd, does a shutdown on the socket.
2. JAGab21137/SR 5003458414:
For each login and logout, remshd and rexecd must log the
necessary information in "/var/adm/wtmp" and
"/var/adm/btmp" files as the case may be.
Resolution:
Modified the source code to add a new function. It has
a parameter from which it decides to which of the two
files it should update.
3. JAGab31733/SR 5003467134:
If the target system has a directory owned by a user
other the one who is owning the source directory, rcp
fails to copy the files following the directory present
in the target machine. This is due to an error message
sent by the remote machine when utimes() system call
fails for that target directory, which makes the client
to exit without copying the rest of the files.
Resolution:
The server code has been modified to send the final
response to the client after the utimes() system call
so that the client will continue the process till it
copies all the files.
4. JAGaa42962/SR 8606140969:
When rcp is invoked with "-r" option to copy more than
one files the target directory is not getting created.
Resolution:
As soon as the server function receives the first
file, it checks whether the target directory is
existing or not. If the target directory is not
existing, then it creates the target directory. Then it
copies the first sub-directory to the target directory.
5. JAGab83643/SR 8606110892 :
When rdist is used to distribute files, and two of the
distributed files are hardlinked, rdist is failing to
create the proper path in some cases.
Resolution:
rdist code has been modified to creat the hard linked
files properly.
6. JAGad15036/SR 8606145700:
In remshd the child process writes the error message into
a pipe and dies. Sometimes the child process dies before
the parent process has read that error message. Then the
parent receives a SIGCHLD signal and exits without
reading the error message. Thus the error message is not
getting displayed.
Resolution:
The parent process after receiving the SIGCHLD signal
tries to read from the pipe before doing an exit.
Also, the SIGCHLD signal is now blocked during the read
operation from the pipe.
7. JAGad06606/SR 8606137488:
ruptime checks to see if the machine is up or down
for more than 365 days. If it is more than 365 days it
will print ??:??.
Resolution:
The check has been removed so that ruptime can always
print the number of days even it is more than 365 days.
8. JAGad28199/SR 8606158870:
rlogind was ignoring SIGCLD signal while ending rlogin
session. If it gets SIGCLD signal before exiting it was
not calling SIGCLD handler, where it was checking for
child status and logging syslog message.
Resolution:
The code has been modified not to ignore the SIGCLD
signal and to log the proper message.
9. JAGad28443/SR 8606159114:
When 'install' in the 'distfile' is used without '-w'
option, rdist is not creating the regular files properly.
Resolution:
rdist code has been modified to create the regular files
properly.
10.JAGad36477/SR 8606167191:
rdist is not always handling source and destination path
properly.
Resolution:
Now rdist code has been modified to handle
source and destination path properly.
PHNE_13619:
rlogin
* rlogin does not handle LANG environment variable
properly.
rlogind
* rlogind does not handle long hostname.
remsh
* ER - remsh with stderr closed returns "fd = 2".
* remsh does not handle LANG environment variable properly.
remshd
* remshd does not update login counters properly.
* With PHNE_12161 installed, remsh displays the
error message "invalid id".
* rexecd does not update trusted systems DB on
good logins.
rcp
* rcp does not clear old errno value.
* SR: RCP may show file as being there even if it ran
out of disk space.
* rcp does not check for proper parameters.
* rcp does not handle LANG environment variable properly.
rdist
* rdist does not check for temporary files before creating
them.
* rdist does not set process resources properly.
* rdist does not process distfile properly.
* rdist fails if subdirectory exists that matches
remote hostname.
PHNE_12161:
* On trusted systems, the bad login counter is not
updated by rexecd on a login failure. As a result,
the lockout feature of trusted systems does not work
with rexec.
PHNE_11728:
* Certain signals are not trapped by rlogin and
these cause rlogin to dump core. Now, rlogin
exits gracefully on receiving these signals.
* Change in rlogind logging. Timeout login events
no longer logged.
PHNE_10638:
* rlogin dies intermittently because of SIGUSR1. This
occurs because of some timing problems.
PHNE_9787:
* RCP on a NFS system fails with an error message. This
is because a truncate is done before the permissions
of the file is changed.
PHNE_9219:
* RDIST does not set the userid before
certain file operations.
PHNE_8889:
* remshd/rexecd did not check for aging in the case of
null passwords.
PHNE_8807:
* Environment variable TERM overflow in rlogin.
* Time stamp of rlogind's log message for login failure
is set to EST/EDT.
* rlogind terminates when a SIGSTOP is issued to any
of it's child processes. The daemon receives a
SIGCHLD which causes rlogind to terminate.
PHNE_7920:
* The operating system did not support files greater than
2 Giga bytes. The 10.20 release has large file support
built in. RDIST has been enhanced to provide large file
support. In order for RDIST to interoperate correctly
with existing versions of RDIST, patches will be
released for 10.X to handle some interoperability issues.
* RDIST creates an error message based on a user provided
string without checking bounds on the buffer used. This
buffer is on the stack, and can therefore be used to
execute arbitrary instructions.
PHNE_7918:
* The operating system did not support files greater than
2 Giga bytes. The 10.20 release has large file support
built in. RCP has been enhanced to provide large file
support. In order for RCP to interoperate correctly with
existing versions of RCP, patches will be released for
9.X and 10.X to handle some interoperability issues.
PHNE_6815:
* Pathname accidentally got changed.
SR:
8606105517 5003458414 5003467134 8606140969 8606110892
8606145700 8606137488 8606158870 8606159114 8606167191
4701381525 1653188235 5003422279 5003403527 5003392761
1653257212 5003394536 1653234070 5003360909 5003314096
5003301994 5003371351 1653210096 1653206573 4701350389
4701320101 1653173971 5003352864 4701329367 4701340471
Patch Files:
/usr/lbin/remshd
/usr/lbin/rexecd
/usr/lbin/rlogind
/usr/bin/rlogin
/usr/bin/remsh
/usr/bin/rcp
/usr/bin/rexec
/usr/bin/rdist
/usr/bin/ruptime
what(1) Output:
/usr/lbin/remshd:
Copyright (c) 1983, 1988 The Regents of the Universi
ty of California.
rshd.c 5.17.1.2 (Berkeley) 2/7/89
remshd.c $Revision: 1.34.212.15 $
/usr/lbin/rexecd:
Copyright (c) 1983, 1988 The Regents of the Universi
ty of California.
rexecd.c 5.7 (Berkeley) 1/4/89
rexecd.c $Revision: 1.34.212.15 $
/usr/lbin/rlogind:
Copyright (c) 1983, 1988 The Regents of the Universi
ty of California.
rlogind.c $Header: rlogind.c,v 1.17.212.25 2000/09/0
7 06:33:29 gpatgar Exp $
rlogind.c 5.22.1.6 (Berkeley) 2/7/89
/usr/bin/rlogin:
Copyright (c) 1983 The Regents of the University of
California.
rlogin.c $Revision: 1.35.212.10 $ $Date: 98/07/15 23
:33:25 $
/usr/bin/remsh:
Copyright (c) 1983 The Regents of the University of
California.
remsh.c $Revision: 1.28.212.10 $ $Date: 98/07/15 22:
31:58 $
rsh.c 5.7 (Berkeley) 9/20/88
/usr/bin/rcp:
Copyright (c) 1983 The Regents of the University of
California.
rcp.c $Revision: 1.16.212.25 $ $Date: 2000/05/02 03:
03:07 $
rcp.c 5.20 (Berkeley) 5/23/89
/usr/bin/rexec:
Copyright (c) 1983 The Regents of the University of
California.
remsh.c $Revision: 1.28.212.10 $ $Date: 98/07/15 22:
31:58 $
rsh.c 5.7 (Berkeley) 9/20/88
/usr/bin/rdist:
$Revision: 1.1.212.4 Sat Jan 27 10:22:18 GMT 2001$
/usr/bin/ruptime:
Copyright (c) 1983 The Regents of the University of
California.
ruptime.c $Revision: 1.3.212.4 $ $Date: 2000/07/11 0
2:00:51 $
ruptime.c 5.5 (Berkeley) 8/25/88
cksum(1) Output:
2385750223 24576 /usr/lbin/remshd
3928880565 24576 /usr/lbin/rexecd
1023136489 28672 /usr/lbin/rlogind
1909433317 24576 /usr/bin/rlogin
1712561782 16384 /usr/bin/remsh
3219178008 32768 /usr/bin/rcp
1712561782 16384 /usr/bin/rexec
3899010559 73728 /usr/bin/rdist
669273757 20480 /usr/bin/ruptime
Patch Conflicts: None
Patch Dependencies: None
Hardware Dependencies: None
Other Dependencies: None
Supersedes:
PHNE_6815 PHNE_7918 PHNE_7920 PHNE_8807 PHNE_8889 PHNE_9219
PHNE_9787 PHNE_10638 PHNE_11728 PHNE_12161 PHNE_13619
Equivalent Patches: None
Patch Package Size: 320 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 PHNE_20748
5a. For a standalone system, run swinstall to install the
patch:
swinstall -x autoreboot=true -x match_target=true \
-s /tmp/PHNE_20748.depot
By default swinstall will archive the original software in
/var/adm/sw/patch/PHNE_20748. If you do not wish to retain a
copy of the original software, you can create an empty file
named /var/adm/sw/patch/PATCH_NOSAVE.
WARNING: If this file exists when a patch is installed, the
patch cannot be deinstalled. Please be careful
when using this feature.
It is recommended that you move the PHNE_20748.text file to
/var/adm/sw/patch for future reference.
To put this patch on a magnetic tape and install from the
tape drive, use the command:
dd if=/tmp/PHNE_20748.depot of=/dev/rmt/0m bs=2k
Special Installation Instructions: None
-----End of Document ID: PHNE_20748------------------------------------------
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]