Patch-ID# 101594-02
Keywords: spam sx sxow sxlib sxxgl sxxil
Synopsis: SunOS 5.3 (SPARCstation 10SX) sxlib/sxow/sxxgl/sxxil jumbo patch
Date: Mar/21/94
Solaris Release: 2.3
SunOS Release: 5.3
Unbundled Product:
Unbundled Release:
Relevant Architectures: sparc.sun4m
BugId's fixed with this patch: 1151283 1154350 1154354 1154358 1148227 1149845 1154332 1154343 1154344 1154002 1155861 1155862 1154376 1154338 1154339 1154341 1154338 1154355 1154357 1154359 1154360 1157480 1154346 1157428 1157430 1157766 1157096 1155932 1155782 1155098 1154363 1154361 1154352 1154329 1154279 1154071 1154835 1155290 1155658 1141254 1142930 1148240 1157413 1157414 1157411 1157473 1143031 1154156 1154159 1154353 1155630 1156321 1156324 1156617 1156202 1156193 1156195 1154531 1142933 1159618 1159624 1159685 1158709 1158946 1158789
Changes incorporated in this version: 1154156 1154159 1154353 1155630 1156321 1156324 1156617 1156202 1156193 1156195 1154531 1142933 1159618 1159624 1159685 1158709 1158946 1158789
Patches accumulated and obsoleted by this patch:
Patches which conflict with this patch:
Patches required with this patch:
Obsoleted by:
Files included with this patch:
/usr/lib/libsx.so.1
/usr/openwin/server/modules/ddxSUNWcg14.so.1
/opt/SUNWits/Graphics-sw/xgl-3.0/lib/pipelines/xglSUNWsx.so.3
/opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcomputeJpeg_SUNWcg14.so.1
/opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcomputeSUNWcg14.so.1
/opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcomputesx.so.1
/opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilcsx.so.1
/opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilioSUNWcg14.so.1
/opt/SUNWits/Graphics-sw/xil/lib/pipelines/xilsx.so.1
Problem Description:
1154531: XCopyArea not X11 compliant
1142933: Xsun core dumps while zoom-out of postscript doc using imagetool
1159618: fp precision bug in pgon clipper
1159624: screen-door transparency uses blend attr
1159685: fix for core dumps and incorrect clipping
1158709: xil crashes in zoom with certain src & dst origin combinations
1158946: xil crashes in zoom with negative image origins
1158789: newframe ignores DC viewport
1154156: Bilinear interpolation returns wrong result destination data by
1154159: Bicubic interpolation does not compute correct pixel value over 9
1154353: ROI's handled incorrectly in Scale16bicubic
1155630: On SX, xil_scale (NN, sf>2) to a display with an attached roi
1156321: Any part of 2 scale facotr "nearest" destination XilImage appear
1156324: Scale factor never work correctly on xil_scale as compared with
1156617: xil_scale doesn't make proper image which ROI is set without
1156202: sx-xil scale with bilinear interpolation causes ugly artifacts
1156193: sx-xil does not interpolate pixels around boundaries during
1156195: sx-xil does not interpolate pixels around boundaries during
from (101594-01):
1151283: xil_scale with bilinear, .1., .1 never returns
1154350: bad error chekcing in OrConst16
1154354: performance problem in Scale16nearest
1154358: linebytes problem in Threshold16
1148227: xil_scale of a byte image with an integral scale factor
1149845: xil_set_pixel() doesn't work (or maybe rescale)
1154332: memory leak in Convolve8
1154343: dangerous spamification in Lookup8_8
1154344: performance problem copy'ing LUT in Lookup8_8
1154002: JPEG decompression color brightness off by 1.164
1155861: spamification problem in XilDeviceStorageTypeSX.cc
1155862: Affine8nearest is broken
1154376: Memory leak in CG14 driver
1154338: memory leak in DivideConst8
1154339: memory leak in Extrema16
1154341: memory leak in Extrema8
1154338: memory leak in DivideConst8
1154355: memory leak in SubtractConst8
1154357: memory leak in SubtractFromConst8
1154359: memory leak in Translate16nearest
1154360: memory leak in Translate8nearest
1157480: memory leak in TranslateBL8SX.cc
1154346: memory leak in MultiplyConst8.cc
1157428: Transpose on SX core dumps and does not match memory code
1157430: Transpose on CG14 core dumps and does not match memory code
1157766: lookup16_16 outofbounds reg access under xilch if called after
1157096: SetValue8 cg14 molecule for 1 band does not replicate all four
1155932: performance problem in Rescale16
1155782: performance problem in rgblinear to other color spaces; uncaced
1155098: roi and roi_list not destroyed in Convolve16SX.cc for unsupported
1154363: performance problem in xils_rgb7092rgblinear_8
1154361: performance problem in xils_photoycc2rgb709_8
1154352: planemasks handled incorrectly in Rotate8nearest
1154329: wrong planemask used on 3 band child images in Affine8nearest
1154279: 9x9 separable convolution needs to be integrated in sx/xil
1154071: UniGraphics shows artifacts on SX
1154835: SX driver crashes when rendering clipped triangle
1155290: Pro/Engineer application crashes running short_test diagnostic
1155658: Face distinguishing for msp incorrect if projection is parallel
1141254: XGL/SX driver generates FPEs
1142930: z-buffered lines have dropouts if no cmem
1148240: AVS bounding box not erased through hardware renderer
1157413: 2d line renderer does not punt if no contig-mem
1157414: No win-lock is performed if double buffers are switched manually
1157411: Transparency attrs used when transparency value = 0.0
1157473: AA lines still drawn when rop != copy
1143031: Colormap double buffering broken on Sx
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:
-----------------------------
None.
Instructions to install patch using "installpatch"
--------------------------------------------------
1. Become super-user.
2. Apply the patch by typing:
//installpatch /
where is the directory containing the patch and
is the patch number. must be a full path name.
Example:
# /tmp/123456-01/installpatch /tmp/123456-01
3. If any errors are reported, see "Patch Installation Errors" in
the Command Descriptions section below.
Rebooting the system or restarting the application after a successful
patch installation is usually necessary to utilize patch.
NOTE: 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 the next section for instructions
for installing a patch on a client.
Instructions for installing a patch on a diskless or dataless client
--------------------------------------------------------------------
1. Before applying the patch, the following command must be executed
on the server to give the client read-only, root access to the
exported /usr file system so that the client can execute the
pkgadd command:
share -F nfs -o ro,anon=0 /export/exec/Solaris_2.1_sparc.all/usr
The command:
share -F nfs -o ro,root= \
/export/exec/Solaris_2.1_sparc.all/usr
accomplishes the same goal, but only gives root access to the
client specified in the command.
2. Login to the client system and become super-user.
3. Continue with step 2 in the "Instructions to install patch using
installpatch" section above.
Instructions for backing out patch using "backoutpatch"
-------------------------------------------------------
1. Become super-user.
2. Change directory to /var/sadm/patch:
cd /var/sadm/patch
3. Backout patch by typing:
/backoutpatch
where is the patch number.
Example:
# 123456-01/backoutpatch 123456-01
4. If any errors are reported, see "Patch Backout Errors" in
the Command Descriptions section below.
Instructions for identifying patches installed on system:
----------------------------------------------------------
Type:
installpatch -p
This command produces a list of the patch IDs of the patches that
are currently applied to the system. When executed with the -p
option, the installpatch command does not modify the system in
any way.
Command Descriptions
--------------------
NAME
installpatch - apply patch package to Solaris 2.x system
backoutpatch - remove patch package from Solaris 2.x system
SYNOPSIS
installpatch [-u] [-d]
backoutpatch
DESCRIPTION
These installation and backout utilities apply only to
Solaris 2.x associated patches. They do not apply to Solaris
1.x associated patches. These utilities are currently only
provided with each patch package and are not included with
the standard Solaris 2.x release software.
OPTIONS
installpatch
-u unconditional install, do not verify file attributes
-d do not save original files being replaced
-p print a list of the patches currently applied on the system
DIAGNOSTICS
Patch Installation Errors:
--------------------------
Error message: Patch has already been applied.
Explanation and recommended action: This patch has already been
applied to the system. If the patch has to be reapplied
for some reason, backout the patch and then reapply it.
Error message: This patch is obsoleted by a patch which has
already been applied to this system. Application of this
patch would leave the system in an inconsistent state.
Patch installation is aborted.
Explanation and recommended action: Occasionally, a patch
is replaced by a new patch which incorporates the bug fixes
in the old patch and supplies additional fixes also. At
this time, the earlier patch is no longer made available
to users. The second patch is said to "obsolete" the
first patch. However, it is possible that some users
may still have the earlier patch and try to apply it to
a system on which the later patch is already applied.
If the obsoleted patch were allowed to be applied, the
additional fixes supplied by the later patch would no
longer be available, and the system would be left in an
inconsistent state. This error message indicates that
the user attempted to install an obsoleted patch. There
is no need to apply this patch because the later patch
has already supplied the fix.
Error message: The packages to be patched are not installed on
this system.
Explanation and recommended action: None of the packages
to be updated by this patch are installed on the system.
Therefore, this patch cannot be applied to the system.
Error message: This patch is not applicable to client systems.
Explanation and recommended action: The patch is only
applicable to servers and stand-alone machines. Attempting
to apply this patch to a client system will have no effect on
the system.
Error message: The /usr/sbin/pkgadd command is not executable.
Explanation and recommended action: The /usr/sbin/pkgadd
command cannot be executed. The most likely cause of this
is that installpatch is being run on a diskless or dataless
client and the /usr file system was not exported with
root access to the client. See the section above on
"Instructions for installing a patch on a diskless or
dataless client".
Error message: Patch directory is not of expected format.
Explanation and recommended action: The patch directory
supplied as an argument to installpatch did not contain
any patch packages. Verify that the argument supplied
to installpatch is correct.
Error message: The following validation errors were found:
Explanation and recommended action: Before applying the patch,
the patch application script verifies that the current
versions of the files to be patched have the expected
fcs checksums and attributes. If a file to be patched has
been modified by the user, the user is notified of this
fact. The user then has the opportunity to save the
file and make a similar change to the patched version.
For example, if the user has modified /etc/inet/inetd.conf
and /etc/inet/inetd.conf is to be replaced by the patch,
the user can save the locally modified /etc/inet/inetd.conf
file and make the same modification to the new file
after the patch is applied. After the user has noted all
validation errors and taken the appropriate action for
each one, the user should re-run installpatch using
the "-u" (for "unconditional") option. This time, the
patch installation will ignore validation errors and
install the patch anyway.
Error message: Insufficient space in /var/sadm to save old files.
Explanation and recommended action: There is insufficient
space in the /var/sadm directory to save old files.
The user has two options for handling this problem:
(1) generate additional disk space by deleting unneeded
files, or (2) override the saving of the old files by
using the "-d" (do not save) option when running installpatch.
However if the user elects not to save the old versions of
the files to be patched, backoutpatch CANNOT be used.
One way to regain space on a system is to remove the
save area for previously applied patches. Once the user
has decided that it is unlikely that a patch will be
backed out, the user can remove the files that were saved
by installpatch. The following commands should be executed
to remove the saved files for patch xxxxxx-yy:
cd /var/sadm/patch/xxxxxx-yy
rm -r save/*
rm .oldfilessaved
After these commands have been executed, patch xxxxxx-yy can
no longer be backed out.
Error message: Save of old files failed.
Explanation and recommended action: Before applying the patch,
the patch installation script uses cpio to save the old
versions of the files to be patched. This error message
means that the cpio failed. The output of the cpio
would have been preceded this message. The user should
take the appropriate action to correct the cpio failure.
A common reason for failure will be insufficient disk
space to save the old versions of the files. The user
has two options for handling insufficient disk space:
(1) generate additional disk space by deleting unneeded
files, or (2) override the saving of the old files by
using the "-d" option when running installpatch. However
if the user elects not to save the old versions of the
files to be patched, the patch CANNOT be backed out.
Error message: Pkgadd of package failed. 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.
Error message: error while adding patch to root template
Explanation and recommended action: The install script
determined this system to be a client server. The attempt
to apply the patch package to the appropriate root
template space located under /export/root/templates
failed unexpectedly. Check the log file for any failure
messages. Correct the problem and re-apply the patch.
Patch Backout Errors:
---------------------
Error message: Patch has not been 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: 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. 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.
After a patch package has been installed pkginfo(1) will
not recognize the SUNW_PATCHID macro in the patch package
pkginfo file. Instead, to identify patches installed on
the system use the grep command method described in the
patch README.
The pkgadd command shipped with Solaris 2.1 fails (drops core
without any error message) when there are more than 100
entries in the /etc/mnttab file. This means that installpatch
can fail, because it uses pkgadd. Since this is very likely on
any big system with lots of automounts, ANY patch could fail.
Applying patch 100901-01 fixes this problem (the README for
patch 100901 mentions shutting down the automounter while
applying it).
SEE ALSO
pkgadd(1), pkgchk(1), pkgrm(1), pkginfo(1)