OBSOLETE Patch-ID# 101130-12 Keywords: panic, CD changes, sunpu 2.1 gateway Synopsis: HSI/S 2.0: patch Date: May/09/97 Solaris Release: 2.x SunOS Release: 5.x Unbundled Product: HSI/S Unbundled Release: 2.0 Relevant Architectures: sun4c sun4m sun4d sun4u BugId's fixed with this patch: 1129547 1135164 1138104 1150034 1184586 1187336 1167007 1181246 1205222 1205222 1211770 1227975 1237882 1240458 1229653 1117118 1247901 1242586 1258694 1258695 1247170 1245893 4010040 4016764 4028654 Changes incorporated in this version: 4044596 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: 106477 on Jun/22/98 Files included with this patch: /usr/kernel/drv/HSI /usr/sbin/hsi_trace Problem Description: 4044596 sunpu2.1 process will crash the system 9 out of 10 times Problem Description: (from rev-11) 4016764 sna3274 gateway terminates frequently under heavy load 4028654 HSI/S 2.0: crc errors with internal loopback Problem Description: (from rev-10) 4010040 hsi_stat shows 1 abort for every in put packet Problem Description: (from rev-09) 1247170 hsi causes sdlc_frmr to be sent under heavy load 1245893 The HSI/S card hard hang the system upon running hsi_init on ss20 Problem Description: (from rev-08) 1242586 HSI driver crashes the system. X25 running 1258694 Add better trace facilities to the hsi driver 1258695 Enable ABORT interrupt in ibm mode of HSI driver 1247901 SNA3270 8.0 send FRMR as a reply to valid frames (from rev-07) 1211770 The hsi driver with patch 101130-05 generates thousands of interrupts 1227975 503535 - Interrupted X25 connection over HSI consummed 20% of CPU time 1237882 Esc: 504491 SS10 crashes with 'BAD TRAP: type=9' in routine hih_mtob: Data fault 1240458 high interrupts from HSI port 1229653 HSI in sun 1000 panics system if the HSI link is heavly loaded 1117118 find root cause of continuous ABORTS with modem-eliminators in fdx (from rev -06) The driver read side is now MP safe. 1237458 multiple VCs on X.25 cause crash Related Escalation #: ESC501334: ss-10 panic when modem switched off with SNA GW 9.0 on HSI/S (from rev -05) Putback the abort interrupts enable. (from rev -04) Fixed postinstall script in -03 to install HSI from the patch package (from rev -03) Now allows support of up to 8 HSI cards in an SC2000 Cures intermittent "hihX: reset" problems. (from rev -02) 1138104 kernel/HSI synchronization, overrun problems, 1150034 excess xmit hung messages. (from rev -01) 1129547; 1135164: xmit hung on Port hih1 when running hih0 to hih1 Patch Installation Instructions: -------------------------------- Generic 'installpatch' and 'backoutpatch' scripts are provided within each patch package with instructions appended to this section. Other specific or unique installation instructions may also be necessary and should be described below. Special Install Instructions: ----------------------------- if you have HSI/S patch 101130-07 installed on the sytem, please do the following to back it out, csh# backoutpatch 101130-07 Instructions to install patch using "installpatch" -------------------------------------------------- 1. Become super-user. 2. Apply the patch by typing:
.
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
patch packages failed. Any previously installed packages
in the patch should have been removed. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Patch Installation Messages:
---------------------------
Note: the messages listed below are not necessarily considered errors
as indicated in the explanations given. These messages are, however,
recorded in the patch installation log for diagnostic reference.
Message:
Package not patched:
PKG=SUNxxxx
Original package not installed
Explanation: One of the components of the patch would have patched a
package that is not installed on your system. This is not
necessarily an error. A Patch may fix a related bug for several
packages. Example: suppose a patch fixes a bug in both the
online-backup and fddi packages. If you had online-backup installed
but didn't have fddi installed, you would get the message
Package not patched:
PKG=SUNWbf
Original package not installed
This message only indicates an error if you thought the package
was installed on your system. If this is the case, take the
necessary action to install the package, backout the patch (if
it installed other packages) and re-install the patch.
Message:
Package not patched:
PKG=SUNxxx
ARCH=xxxxxxx
VERSION=xxxxxxx
Architecture mismatch
Explanation: One of the components of the patch would have patched a
package for an architecture different from your system. This is not
necessarily an error. Any patch to one of the architecture specific
packages may contain one element for each of the possible
architectures. For example, Assume you are running on a sun4m. If
you were to install a patch to package SUNWcar, you would see the
following (or similar) messages:
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4c
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4d
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4e
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
Package not patched:
PKG=SUNWcar
ARCH=sparc.sun4
VERSION=11.5.0,REV=2.0.18
Architecture mismatch
The only time these messages indicate an error condition
is if installpatch does not correctly recognize your architecture.
Message:
Package not patched:
PKG=SUNxxxx
ARCH=xxxx
VERSION=xxxxxxx
Version mismatch
Explanation: The version of software to which the patch is applied is
not installed on your system. For example, if you were running Solaris
5.3, and you tried to install a patch against Solaris 5.2, you would
see the following (or similar) message:
Package not patched:
PKG=SUNWcsu
ARCH=sparc
VERSION=10.0.2
Version mismatch
This message does not necessarily indicate an error. If
the version mismatch was for a package you needed patched, either
get the correct patch version or install the correct package version.
Then backout the patch (if necessary) and re-apply.
Patch Backout Errors:
---------------------
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: The user has attempted to back
out a patch that was never applied to this system. It is
possible that the patch was applied, but that the patch
directory /var/sadm/patch/ was deleted somehow.
If this is the case, the patch cannot be backed out. The
user may have to restore the original files from the
initial installation CD.
Error message:
This patch was obsoleted by patch $1.
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: The obsoleted contents of an
older patch rev that apparently still exists under /var/sadm/patch
should never be restored out of sequence. This could undermine
the integrity of the more current patch rev installed and the
restoration of the files it has saved.
Error message:
Patch was installed without backing up the original
files. It cannot be backed out.
Explanation and recommended action: Either the -d option of
installpatch was set when the patch was applied, or the save
area of the patch was deleted to regain space. As a result, the
original files are not saved and backoutpatch cannot be used. The
original files can only be recovered from the original
installation CD.
Error message:
pkgrm of package failed return code .
See /var/sadm/patch//log for reason for failure.
Explanation and recommended action: The removal of one of
patch packages failed. See the log file for the reason for
failure. Correct the problem and run the backout script again.
Error message:
Restore of old files failed.
Explanation and recommended action: The backout script uses the
cpio command to restore the previous versions of the files
that were patched. The output of the cpio command should
have preceded this message. The user should take the
appropriate action to correct the cpio failure.
KNOWN PROBLEMS:
On client server machines the patch package is NOT applied
to existing clients or to the client root template space.
Therefore, when appropriate, ALL CLIENT MACHINES WILL NEED
THE PATCH APPLIED DIRECTLY USING THIS SAME INSTALLPATCH
METHOD ON THE CLIENT. See instructions above for
applying patches to a client.
A bug affecting a package utility (eg. pkgadd, pkgrm, pkgchk)
could affect the reliability of installpatch or backoutpatch
which uses package utilities to install and backout the patch
package. It is recommended that any patch that fixes package
utility problems be reviewed and, if necessary, applied before
other patches are applied. Such existing patches are:
100901 Solaris 2.1
101122 Solaris 2.2
101331 Solaris 2.3
SEE ALSO
pkgadd, pkgchk, pkgrm, pkginfo, showrev