Patch-ID# 101284-13 Keywords: leo zx xgl window DGA xlib Sliders Synopsis: Solaris 2.3: Leo (ZX) Jumbo patch Date: Feb/09/95 Solaris Release: 2.3 SunOS Release: 5.3 Unbundled Product: Unbundled Release: Relevant Architectures: sun4c sun4d sun4m BugId's fixed with this patch: 1142155 1143340 1144277 1143257 1136429 1145261 1142745 1141818 1143142 1140344 1142676 1153015 1150680 1145660 1148175 1151688 1155259 1155260 1150871 1151663 1154637 1151996 1150680 1145184 1148048 1157248 1158601 1158930 1159785 1163574 1152778 1139988 1161915 1160231 1158503 1154556 1163940 1160459 1159450 1143588 1138915 1157673 1161166 1151690 1163796 1161212 1167192 1166087 1167341 1167363 1164769 1169502 1155414 1157191 1155553 1170684 1171795 1169541 1151450 1170580 1171552 1173967 1173968 1174916 1175360 1176030 1176189 1177283 1178825 1165947 1180130 1180859 1182300 1182325 1182909 1182993 1185871 1186160 1165947 1188580 Changes incorporated in this version: 1165947 1188580 Patches accumulated and obsoleted by this patch: Patches which conflict with this patch: Patches required with this patch: Obsoleted by: Solaris 2.4 Files included with this patch: /kernel/drv/leo /etc/opt/SUNWleo/bin/leoconfig /usr/openwin/server/modules/ddxSUNWleo.so.1 /opt/SUNWits/Graphics-sw/xgl-3.0/lib/pipelines/xglSUNWleo.so.3 /opt/SUNWits/Graphics-sw/xgl-3.0/lib/locale/en/LC_MESSAGES/xglSUNWleo.mo Problem Description: From (101284-13): 1165947 XGL NURBS resembles sieve (leaks memory) 1188580 leodiag hangs indefinitely upon exit with 'x' option From (101284-12): 1185871 NTSC is not supported by ZX or TZX with new ICS clock chip. 1186160 2.3 ZX driver may try to add interrupt handler twice with ddi_add_intr(9f) From (101284-11): 1182993 ZX driver initializes mutexes/cvs with invalid iblk cookie From (101284-10): 1165947 Memory leaks in XGL NURBS 1180130 Motif 1.2.2 ScrolledList widget doesn't handle long strings correctly 1180859 Xlib rendering invisible when window is grabbed 1182300 ZX driver does not properly handle DMA on large memory (>1G) sun4d 1182325 XGL apps can hang on MP/ZX platforms while waiting for DMA to complete 1182909 need way to disable ZX NURB rendering From (101284-09): 1177283 System panics starting openwindows on ZX with DXlib 1178825 edge offset on ZX not acceptable From (101284-08): 1151450 leoconfig sends unnecessary messages when ZX hardware isn't installed 1170580 /etc/init.d/leconfig should not print message upon exiting 1171552 Multiple ZX on the same machine causes Hang in one of ZX's 1173967 SS20/ZX platform has bad performance when running more than 1 XGL app 1173968 ZX failed sundiag picking test after 8+ hours on SS5/SS20 1174916 ZX driver hard-codes number of enabled LFs 1175360 ZX SS10 system hangs when open audio device 1176030 xgl_multi_simple_polygon decomposed wrong on ZX 1176189 Memory leak in li1Polygon for complex polygons From (101284-07): 1155414 ShowMe Whiteboard has problems snapping images from DGA/XGL windows 1155553 Cursor color incorect after exiting openwindows 1157191 XDrawString broken on ZX under Solaris 2.3 1169502 8bit XFillRectangle draws nothing 1169541 S5/ZX: Assertion failed in module 'LeoPicking.cc' at line 227 1170684 ZX hangs on SS5 1171795 SS20/MP panics running yoyo_demos on ZX From (101284-06): 1151690 ZX driver doesn't use DMA mode for SS5 1163796 XGL support for DMA on SS5 1161212 Direct user DMA should only be used for non-volatile data 1167192 Data Curruption of GC Structure within ZX DDX module 1166087 24-bit pixmaps are not copied correctly into X-window on ZX 1167341 poor performance using WordPerfect under WABI on ZX 1167363 X Cursor often leaves dots behind 1164769 Colour corruption with XCopyArea/XFillRectangle From (101284-05): 1163574: XglDpDevLeo::copyBuffer punts to nowhere (including z-buffer reads) 1152778: hollow polygons not antialiased 1139988: get/set pixel not implemented for Zbuffer 1161915: cursor jumps when reaching the left hand side of the top edge of the screen 1160231: Improvements to overall OS reliability 1158503 FB_GETGAMMA ioctl can cause kernel panic on leo 1154556: Picking hangs Leo (ZX) on Aurora systems 1163940: XCopyArea() for lines, arcs, from pixmap to window failed on ZX 1160459: Inverse Video when Openwindows is exited on the latest ZX boards 1159450: leo doesn't render partial characters along left edge of screen 1143588: cmdtool scrollbar cable breaks up after running leotest on aurora 1138915: Server does NOT call ValidateGC() when changing fonts. 1157673: motif widgets don't show up insensitive on leo (ZX) framebuffer 1161166: core dump running PDGS (not a fix but will prevent core dump) From (101284-04): 1159785: Sending user polyline data with per-vertex flags directly to leo 1158930: hang in Pro/ENGINEER regression tests 1158601: FPE on screen clear because uninitialized variable 1157248: ddx on SPARCstation20/ZX drops pixels 1148048: blt_lock bug: MP (was Kodiac) systems with leo panics From (101284-03): 1155259: ZX does not use hardware Fast Clear for 8-bit windows 1155260: ZX does not use hardware to draw 2D multisimple polygons 1150871: Renderer clip_list attribute does not work on ZX 1151663: xview app does not get backing store on ZX. 1154637: allocating 2 (> 1?) window ids fails and crashes server 1151996: color map double buffering does not work on ZX in 8-bit visual. 1150680: Xsun dumps core when xv is run in 24 bit mode on the ZX 1145184: /usr/openwin/demo/maze problems when run on a leo FB in 24-bit Also, a workaround for 1150676 Openwindows is broken in 24 bit mode on leo From (101284-02): 1153015: sending user data with flag info directly to leo is incorrect 1150680: Xsun dumps core when xv is run in 24 bit mode on the Z 1145660: Visible bell in OW3.3 on Leo is many times slower than OW3. 1148175: Frequent system panics when running Leo in stereo mode 1151688: sun4m leo driver causes aurora to hang running leotool From (101284-01): 1142155: Patterned lines are too slow on Leo 1143340: BAD TRAP M-Bus Timeout Error sched Data Fault 1144277: picking does not work on ss2 1143257: Leo performance problems when using linewidth greater 1.0 1136429: Frequent window system hangs for 3 seconds 1145261: Depth cued patterned lines are not displayed 1142745: Minimum exposure doesn't work for DGA windows 1141818: Single-buffered 8-bit DGA windows not moved to proper plane group 1143142: Multiple Leo support on the same server 1140344: Vertical Sliders leave pixel tears 1142676: xlib crosshair cursor erases xgl image 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: ----------------------------- After installing this patch, reboot the system to load the newly installed driver. 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. Installpatch will backout the patch
to leave the system in its pre-patched state. See the log file
for the reason for failure. Correct the problem and
re-apply the patch.
Error message:
Pkgadd of package failed with error code .
Will not backout patch...patch re-installation.
Warning: The system may be in an unstable state!
See /tmp/log. for reason for failure.
Explanation and recommended action: The installation of one of
the patch packages failed. Installpatch will NOT backout the
patch. You may manually backout the patch using backoutpatch,
then re-apply the entire patch. Look in the log file for the
reason pkgadd failed. 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.
Message:
Re-installing Patch.
Explanation: The patch has already been applied, but there is
at least one package in the patch that could be added. For
example, if you applied a patch that had both Openwindows and
Answerbook components, but your system did not have Answerbook
installed, the Answerbook parts of the patch would not have
been applied. If, at a later time, you pkgadd Answerbook, you
could re-apply the patch, and the Answerbook components of the
patch would be applied to the system.
Message:
Installpatch Interrupted.
Installpatch is terminating.
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files and exit.
Message:
Installpatch Interrupted.
Backing out Patch...
Explanation: Installpatch was interrupted during execution
(usually through pressing ^C). Installpatch will clean up
its working files, backout the patch, and exit.
Patch Backout Errors:
---------------------
Error message:
prebackout patch exited with return code .
Backoutpatch exiting.
Explanation and corrective action: the prebackout script
supplied with the patch exited with a return code other
than 0. Generate a script trace of backoutpatch to determine
why the prebackout script failed. Correct the reason for
failure, and re-execute backoutpatch.
Error message:
postbackout patch exited with return code .
Backoutpatch exiting."
Explanation and corrective action: the postbackout script
supplied with the patch exited with a return code other than
0. Look at the postbackout script to determine why it failed.
Correct the failure and, if necessary, RE-EXECUTE THE
POSTBACKOUT SCRIPT ONLY.
Error message:
Only one service may be defined.
Explanation and corrective action: You have attempted to specify
more than one service from which to backout a patch. Different
services must have their patches backed out with different
invocations of backoutpatch.
Error message:
The -S and -R arguments are mutually exclusive.
Explanation and recommended action: You have specified both a
non-native service to backout, and a package installation root.
These two arguments are mutually exclusive. If backing out a
patch from a non-native usr partition, the -S option should be
used. If backing out a patch from a client's root
partition (either native or non-native), the -R option
should be used.
Error message:
The service cannot be found on this system.
Explanation and recommended action: You have specified a non-
native service from which to backout a patch, but the
specified service is not installed on your system. Correctly
specify the service when backing out the patch.
Error message:
Only one rootdir may be defined.
Explanation and recommended action: You have specified more than
one package install root using the -R option. The -R option
may be used only once per invocation of backoutpatch.
Error message:
The directory cannot be found on this system.
Explanation and recommended action: You have specified a
directory using the -R option which is either not mounted,
or does not exist on your system. Verify the directory name
and re-backout the patch.
Error message:
Patch has not been successfully applied to this system.
Explanation and recommended action: You have attempted to backout
a patch that is not applied to this system. If you must
restore previous versions of patched files, you may have to
restore the original files from the initial installation CD.
Error message:
Patch has not been successfully applied to this system.
Will remove directory
Explanation and recommended action: You have attempted to back
out a patch that is not applied to this system. While the
patch has not been applied, a residual
/var/sadm/patch/ (perhaps from an unsuccessful
installpatch) directory still exists. The patch cannot be
backed out. If you must restore old versions of the patched
files, you may have to restore them from the initial
installation CD.
Error message:
This patch was obsoleted by patch .
Patches must be backed out in the order in
which they were installed. Patch backout aborted.
Explanation and recommended action: You are attempting to backout
patches out of order. Patches should never be backed-out out
of sequence. This could undermine the integrity of the more
current patch.
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, cpio